Missing primary key and unable to be fully resolved

[jorge-sevilla]

Hi, when i run the sincronization i get errors like this:

but it doesn't make sense to me, because the primary key that says it doesn't appear is in the information that's being synchronized.

Then, when the syncronize ends, appers this error:

NetBox: 4.0.2
Python: 3.10.12

[bb-Ricardo]

Hi, did you upgrade from an earlier NetBox version? Please try to delete the cache and run the sync again.

[jorge-sevilla]

Hi,
No, i installed this version since start and already tried deleting the cache but still getting same errors.

I tried editting the skip_object_if_mandatory_attr_is_missing variable to True to skip the primary key errors but still have the other ones.

[bb-Ricardo]

Hi,

It seems that the NetBox response somehow can't be parsed properly, resulting in additional errors at the end of the synchronization.

In general it would be great to post the actual text output as text and not as picture. It is hard to see what's happening on small screens.

Can you run with the cli option -l DEBUG2 please to get some more details?

[jorge-sevilla]

Sure!

I cant post the entire output baecause is too long, but here an example of the "primary key missing" error:

2024-07-31 07:43:44,357 - INFO: Creating new NetBox 'tag' object 'NetBox-synced: Orphaned' with data: {'name': 'NetBox-synced: Orphaned', 'slug': 'netbox-synced-orphaned', 'description': 'A source which has previously provided this object no longer states it exists. Objects would be automatically removed after 30 days but pruning is currently disabled.', 'color': '607d8a'}
2024-07-31 07:43:44,358 - DEBUG2: Sending POST to 'http://192.168.10.89/api/extras/tags/' with data 'b'{"name": "NetBox-synced: Orphaned", "slug": "netbox-synced-orphaned", "description": "A source which has previously provided this object no longer states it exists. Objects would be automatically removed after 30 days but pruning is currently disabled.", "color": "607d8a"}''.
2024-07-31 07:43:44,378 - DEBUG2: Received HTTP Status 200.
2024-07-31 07:43:44,378 - ERROR: This 'tag' data structure does not contain the primary key 'name' got: {'count': 2, 'next': None, 'previous': None, 'results': [{'id': 3, 'url': 'https://192.168.10.89/api/extras/tags/3/', 'display': 'NetBox-synced', 'name': 'NetBox-synced', 'slug': 'netbox-synced', 'color': 'ff5722', 'description': '', 'object_types': [], 'tagged_items': 0, 'created': '2024-07-22T10:17:26.261237Z', 'last_updated': '2024-07-31T07:43:44.322328Z'}, {'id': 4, 'url': 'https://192.168.10.89/api/extras/tags/4/', 'display': 'Source: vcenter', 'name': 'Source: vcenter', 'slug': 'source-vcenter', 'color': '9e9e9e', 'description': '', 'object_types': [], 'tagged_items': 0, 'created': '2024-07-22T14:38:50.753261Z', 'last_updated': '2024-07-31T07:43:44.350556Z'}]}

And then the "could not be fully resolved errors" looks like this:

2024-07-31 07:17:15,368 - ERROR: Unfortunately updated item cluster for object VM5 (GÉMINIS) could not be fully resolved: <NBCluster instance '192.168.11.5' at 140403217631120>
2024-07-31 07:17:15,368 - ERROR: Unfortunately updated item cluster for object ARES could not be fully resolved: <NBCluster instance '192.168.11.3' at 140403217678688>
2024-07-31 07:17:15,368 - ERROR: Unfortunately updated item platform for object VM2 could not be fully resolved: <NBPlatform instance 'VMware ESXi 6.7.0' at 140403211854528>
2024-07-31 07:17:15,369 - ERROR: Unfortunately updated item cluster for object VM2 could not be fully resolved: <NBCluster instance '192.168.11.20' at 140403217640720>
2024-07-31 07:17:15,369 - ERROR: Unfortunately updated item platform for object VM3 could not be fully resolved: <NBPlatform instance 'VMware ESXi 6.5.0' at 140403214287440>
2024-07-31 07:17:15,369 - ERROR: Unfortunately updated item cluster for object VM3 could not be fully resolved: <NBCluster instance '192.168.11.2' at 140403217639568>
2024-07-31 07:17:15,369 - ERROR: Unfortunately updated item cluster for object 192.168.11.9 could not be fully resolved: <NBCluster instance '192.168.11.9' at 140403217637552>
2024-07-31 07:17:15,369 - ERROR: Unfortunately updated item platform for object 192.168.11.9 could not be fully resolved: <NBPlatform instance 'VMware ESXi 6.5.0' at 140403214287440>
2024-07-31 07:17:15,369 - ERROR: Unfortunately updated item device_type for object 192.168.11.4 could not be fully resolved: <NBDeviceType instance 'System x3250 M3 -[4252EAG]-' at 140403211373008>
2024-07-31 07:17:15,369 - ERROR: Unfortunately updated item cluster for object 192.168.11.4 could not be fully resolved: <NBCluster instance '192.168.11.4' at 140403217633376>
2024-07-31 07:17:15,369 - ERROR: Unfortunately updated item platform for object 192.168.11.4 could not be fully resolved: <NBPlatform instance 'VMware ESXi 6.5.0' at 140403214287440>
2024-07-31 07:17:15,369 - ERROR: Unfortunately updated item cluster for object TEST-2K16-MOM-DEMO could not be fully resolved: <NBCluster instance '192.168.11.3' at 140403217678688>
2024-07-31 07:17:15,369 - ERROR: Unfortunately updated item platform for object TEST-2K16-MOM-DEMO could not be fully resolved: <NBPlatform instance 'Microsoft Windows Server 2016 or later (64-bit)' at 140403214818736>
2024-07-31 07:17:15,369 - ERROR: Unfortunately updated item cluster for object VM-CORE_OLD could not be fully resolved: <NBCluster instance '192.168.11.3' at 140403217678688>
2024-07-31 07:17:15,369 - ERROR: Unfortunately updated item platform for object VM-CORE_OLD could not be fully resolved: <NBPlatform instance 'Red Hat Enterprise Linux 9 (64-bit)' at 140403211727296>
2024-07-31 07:17:15,369 - ERROR: Unfortunately updated item cluster for object PROD-NOZOMI-AUDITORIAS could not be fully resolved: <NBCluster instance '192.168.11.3' at 140403217678688>
2024-07-31 07:17:15,369 - ERROR: Unfortunately updated item platform for object PROD-NOZOMI-AUDITORIAS could not be fully resolved: <NBPlatform instance 'FreeBSD 13 or later versions (64-bit)' at 140403214564608>
2024-07-31 07:17:15,369 - ERROR: Unfortunately updated item cluster for object VM-BD-1 could not be fully resolved: <NBCluster instance '192.168.11.3' at 140403217678688>
2024-07-31 07:17:15,369 - ERROR: Unfortunately updated item platform for object VM-BD-1 could not be fully resolved: <NBPlatform instance 'Red Hat Enterprise Linux 9 (64-bit)' at 140403211727296>
2024-07-31 07:17:15,369 - ERROR: Unfortunately updated item cluster for object VDI-1 could not be fully resolved: <NBCluster instance '192.168.11.3' at 140403217678688>

[bb-Ricardo]

Hi, not sure what's going on. But it seems that your HTTP request is altered. When doing a POST request, NetBox answesrs with the object created. In your case NetBox returns a list of all objects of the type the POST request was issued for. In this case, the script send a POST request to create a to /api/extras/tags and receives a list of existing tags which is incorrect.

Please check your Webserver configuration. Do you have any special modules or configuration activaeted?

[jorge-sevilla]

Hello, after looking for a solution for a week without success, I decided to reinstall this github from scratch and I have finally managed to make it work perfectly, no idea what was wrong. Thank you very much for your time and sorry for the inconvenience!

[bb-Ricardo]

Great that you get it working.