-
Notifications
You must be signed in to change notification settings - Fork 75
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
vm_tenant_relation #206
Comments
Hi, It would be helpful to get some more information. How does the config look like? can you run the tool with The tenant exists in NetBox? How does it look like? |
Here is existing Tenant
Logs from DEBUG2:
Tenant after sync:
Config string:
|
Ok, looks good. Any reason why you changed the tenant slug in NetBox? Otherwise the update seemed to work fine. |
thats the main issue - slug was changed by sync update.
|
Can you explain why this causes an issue? |
If question is about why I've created Tenant by hands: I've got ansible playbook that creates all the tenants, and in our env we have different names and slug, including cyrillic names. If talk more globally about our case: |
Alright. I have to come up with a general solution to solve this. Currently the slug is created on demand from the name. Will look into it next week. |
Example: Tenant Name: Simple_IS after sync slug will be 'simple-is' Example2: after sync slug will be '-' |
True, it is pretty ignorant to assume objects are named using roman letters. |
So expected behaviour for me look like additional idea: OR use slug in config insted of name? |
Agree, but Managers wants to see 'TRUE NAMES' in RU. Nevertheless the case is not about Cyrilic symbols :) |
Hi, Sorry it took quite a while. I just pushed a new commit to the Thank you |
issue with assigning vm with Tenant if vm_tenant_relation is exist
INFO: Tenant 'NAME' attribute 'slug' changed from 'u0002-slug' to '-'
So if tenant already exists - its rewrite slug to '-'
The text was updated successfully, but these errors were encountered: