Cannot redeploy from pg_dump when custom objects refers to netbox native objects

[cbout22]

Plugin Version

0.4.4

NetBox Version

4.4.9

Python Version

3.12.3

Steps to Reproduce

1. Create a COT named Bar
2. Create a COT named Foo with: COTF : Object-> Tenancy -> tenants and COTF : Object -> Custom Object -> Bar
3. Create a Foo custom object that is bind to a tenant and a Bar CO
4. Dump db
5. Re-Deploy a netbox with this dump
6. Try to access to any tenants and custom objects

Expected Behavior

We can access to tenants, Foo custom objects and Bar custom objects

Observed Behavior

1. Impossible to access to any tenants (whenever they were never linked to any custom object)

2. Impossible to access to custom objects

[arthanson]

@cbout22 I'm not seeing this behavior following your steps, can you please check if there is something else needed to reproduce. I create the COT with the field referencing tenants and created an object of that type with the tenant set. I then did a pgdump then restored it to a new database and accessed that database - all worked fine and I could access the tenant and the custom objects fine.

[cbout22]

I tried to find another protocol, but i didn't find any other way to reproduce it.

It arrives that we do not reproduce the bug if our COTF only point to Netbox's Natif Objects

But when we add a COTF that link to another COT, the bug always happened.

Maybe it's our configuration that is problematic :

Custom Object Hub :

available_slots(Available slots): int 
name: Text, Primary name field, Required, Must be unique
type: choice, Required
tenant: Object > tenancy > tenant, required
vrf: Object > ipam > vrf, required

Custom Object Attachment :

hub: Object > Custom Objects > Hub, required
vrf: Object > ipam > vrf, required

Then I create a Custom Objects > Hubs and create and delete multiples Custom Objects > Attachments attached to this hub and to multiple vrf. Before dumping I've 1 hub and 1 attachment