-
Notifications
You must be signed in to change notification settings - Fork 29
Netbox virtual interfaces do not support tag filter #33
Comments
Thanks for the report @inetman28! I suspect the issue is related to the way the tags are being created. Either the tag has a name or slug value that not conforming to NetBox. When searching objects by tag NetBox is returning all items instead of the items that would otherwise contain the tag. Would you mind sharing the tag name and slug for me? The output of the following URL would be very helpful in troubleshooting as well. Thank you! |
hi
|
Thank you! You've presented quite an interesting situation. Reviewing the NetBox API docs I see we can assign tags to I will take a bit of time to review this and see what alternative methods we have of comparing and syncing virtual machine interfaces. Great find! |
I've submitted a patch for this issue. It works around the current limitation by collecting all interfaces and then filtering by tag post collection. I will check with the upstream NetBox community project to determine if it's the desired ability to tag and object without being able to query those tags as well. |
Fix for #33 by filtering prunable virtual interfaces post collection from NetBox
I've applied the patch in |
Environment
Steps to Reproduce
Expected Behavior
I expected that all vcenter objects will sync with netbox
Observed Behavior
I have two vcenter servers: vcsmgmt and vcsres-1. When object from vcsres-1 have been synced with netbox, second vcenter should be synced too but during sync second vcenter server remove virtual interfaces and ip address that was synced from first vcenter. See below log for example:
as you can see we get objects from netbox with 'vcsmgmt' tag
but vcenter-netbox-sync will remove another objects without tag 'vcsmgmt' ('vcsres-1' for example)
The text was updated successfully, but these errors were encountered: