Justin

Oh man, that's a lot of spam. Yes, the logs now show that it's matching on the MAC address. However, it's matching to a VM in a completely different cluster...

Can the search for an existing VM be isolated the current cluster it's working on?

The two versions that I'm working with on my test network are 4.20.11.1M and 4.22.6M. Both have the same issue.

It looks like this syntax is the same at least up through 4.27.

I went back to my production (3.7.4) and discovered it does the same in the Preferences menu, but also found the menu item for light/dark mode switch which takes effect...

The largest issue seems to be the change from ContentType to ObjectType. We were able to get it working by replacing all instances of content_types in the files in module/...

Still need to change line 1192 as noted above: ``` for content_type in data.get("object_types", []): ```

``` Traceback (most recent call last): File "/opt/netbox-sync/./netbox-sync.py", line 146, in main() File "/opt/netbox-sync/./netbox-sync.py", line 98, in main nb_handler.query_current_data(source.dependent_netbox_objects) File "/opt/netbox-sync/module/netbox/connection.py", line 521, in query_current_data self.inventory.add_object(nb_object_class, data=object_data, read_from_netbox=True) File "/opt/netbox-sync/module/netbox/inventory.py",...

> Still need to change line 1192 as noted above: > > ``` > for content_type in data.get("object_types", []): > ``` Apparently I was wrong. Whatever happened the first run...

This was happening to me, but only when the cluster being imported didn't exist in Netbox.