Need help for cluster multisite config

[steve-hbt]

Hello everyone,

Some elements are synced correctly, however, I still have multiple site-related errors in the console.
So I'm wondering if some elements are not synced because of this.

My infrastructure looks like this:

• Host ESXI-1 is in SITE-1 in RACK-1-1
• Host ESXI-2 is in SITE-2 in RACK-2-1
• Each host is in the maincluster which is not on any site ()

Thanks for help !

2025-06-23 15:11:38,784 - INFO: Query data from vCenter: 'vcenter.my.domain'
2025-06-23 15:11:38,815 - ERROR: This 'site' data structure does not contain the primary key 'name' got: {'name': None}
2025-06-23 15:11:38,815 - INFO: Created new site object: None
2025-06-23 15:11:38,815 - INFO: Cluster 'maincluster' attribute 'scope_type' changed from 'None' to 'dcim.site'
2025-06-23 15:11:38,831 - ERROR: This 'site' data structure does not contain the primary key 'name' got: {'name': None}
2025-06-23 15:11:42,409 - WARNING: Possibly wrongly assigned VRF for IP '192.168.210.3/24'. Current VRF 'DATACENTER' and possible VRF 'None'
2025-06-23 15:11:54,815 - INFO: Parsing objects which were marked to be reevaluated
2025-06-23 15:11:54,816 - INFO: Site 'None' attribute 'tags' changed from '[]' to '['NetBox-synced', 'Source: maincluster-vcenter']'
2025-06-23 15:11:54,867 - INFO: Updating changed data in NetBox
2025-06-23 15:11:54,870 - INFO: Creating new NetBox 'site' object 'None' with data: {'tags': [{'name': 'NetBox-synced'}, {'name': 'Source: maincluster-vcenter'}]}
2025-06-23 15:11:54,890 - ERROR: NetBox returned: POST /api/dcim/sites/ Bad Request
2025-06-23 15:11:54,890 - ERROR: NetBox returned body: {'name': ['This field is required.'], 'slug': ['This field is required.']}
2025-06-23 15:11:54,890 - ERROR: Request Failed for site. Used data: {'tags': [{'name': 'NetBox-synced'}, {'name': 'Source: maincluster-vcenter'}]}
2025-06-23 15:11:54,900 - INFO: Updating NetBox 'cluster' object 'maincluster' with data: {'scope_type': 'dcim.site'}
2025-06-23 15:11:54,958 - ERROR: NetBox returned: PATCH /api/virtualization/clusters/3/ Bad Request
2025-06-23 15:11:54,959 - ERROR: NetBox returned body: {'scope': ['Please select a site.']}
2025-06-23 15:11:54,959 - ERROR: Request Failed for cluster. Used data: {'scope_type': 'dcim.site'}
2025-06-23 15:11:55,287 - INFO: Creating new NetBox 'site' object 'None' with data: {'tags': [{'name': 'NetBox-synced'}, {'name': 'Source: maincluster-vcenter'}]}
2025-06-23 15:11:55,304 - ERROR: NetBox returned: POST /api/dcim/sites/ Bad Request
2025-06-23 15:11:55,304 - ERROR: NetBox returned body: {'name': ['This field is required.'], 'slug': ['This field is required.']}
2025-06-23 15:11:55,305 - ERROR: Request Failed for site. Used data: {'tags': [{'name': 'NetBox-synced'}, {'name': 'Source: maincluster-vcenter'}]}
2025-06-23 15:11:55,314 - INFO: Updating NetBox 'cluster' object 'maincluster' with data: {'scope_type': 'dcim.site'}
2025-06-23 15:11:55,371 - ERROR: NetBox returned: PATCH /api/virtualization/clusters/3/ Bad Request
2025-06-23 15:11:55,371 - ERROR: NetBox returned body: {'scope': ['Please select a site.']}
2025-06-23 15:11:55,371 - ERROR: Request Failed for cluster. Used data: {'scope_type': 'dcim.site'}
2025-06-23 15:11:55,644 - INFO: Completed NetBox Sync in 26 seconds

with this configuration :

; relations options

; This option defines which vCenter cluster is part of a NetBox site.
; This is done with a comma separated key = value list.
;   key: defines the cluster name as regex
;   value: defines the NetBox site name (use quotes if name contains commas)
; This is a quite important config setting as IP addresses, prefixes, VLANs
; and VRFs are site dependent. In order to assign the correct prefix to an IP
; address it is important to pick the correct site.
; A VM always depends on the cluster site relation
; a cluster can be specified as "Cluster-name" or
; "Datacenter-name/Cluster-name" if multiple clusters have the same name.
; When a vCenter cluster consists of hosts from multiple NetBox sites,
; it is possible to leave the site for a NetBox cluster empty. All VMs from
; this cluster will then also have no site reference.
; The keyword "<NONE>" can be used as a value for this.
;cluster_site_relation = Cluster_NYC = New York, Cluster_FFM.* = Frankfurt, Datacenter_TOKIO/.* = Tokio, Cluster_MultiSite = <NONE>
cluster_site_relation = maincluster = <NONE>

; Same as cluster site but on host level. If unset it will fall back to
; cluster_site_relation
;host_site_relation = nyc02.* = New York, ffm01.* = Frankfurt
host_site_relation = esxi-1.* = SITE-1, esxi-2.* = SITE-2

[bb-Ricardo]

Hi, it seems the sites have not been created in NetBox properly before the first sync. You need to create SITE-1 and SITE-2 before the first sync.

[steve-hbt]

My sites was already created before first sync but on first sync dosnt have host_site_relation option

i have to do something for « remake » a first sync ?

[bb-Ricardo]

this line is strange:

2025-06-23 15:11:38,815 - ERROR: This 'site' data structure does not contain the primary key 'name' got: {'name': None}

When the site is read from NetBox, it should have a name defined.

[steve-hbt]

I will request site information with API tomorrow to see the result of name.
Thanks

[steve-hbt]

The API request correctly returns a result with "name" defined.

GET /api/dcim/sites/1/
HTTP 200 OK
Allow: GET, PUT, PATCH, DELETE, HEAD, OPTIONS
Content-Type: application/json
Vary: Accept

{
    "id": 1,
    "url": "https://netbox/api/dcim/sites/1/",
    "display_url": "https://netbox/dcim/sites/1/",
    "display": "SITE-1",
    "name": "SITE-1",
    "slug": "site-1",
    "status": {
        "value": "active",
        "label": "Active"
    },

[steve-hbt]

Hello,
Despite a lot of searching, I haven't found any solutions.
-l DEBUG2 displays this result.
Could the problem be caused by the use of <NONE> in my configuration?

2025-07-03 11:21:39,004 - INFO: Query data from vCenter: 'vcenter.my.domain'
2025-07-03 11:21:39,015 - DEBUG: vCenter returned '1' datacenter
2025-07-03 11:21:39,018 - DEBUG: Parsing vCenter datacenter: DC1
2025-07-03 11:21:39,018 - DEBUG2: Parsing 'cluster group' data structure: DC1
2025-07-03 11:21:39,028 - DEBUG: vCenter returned '1' cluster
2025-07-03 11:21:39,035 - DEBUG: Parsing vCenter cluster: DC1/maincluster
2025-07-03 11:21:39,035 - DEBUG2: Trying to find site name for cluster 'DC1/maincluster'
2025-07-03 11:21:39,035 - DEBUG2: Found a matching cluster_site_relation '<NONE>' (maincluster) for maincluster
2025-07-03 11:21:39,035 - DEBUG2: Site relation for 'DC1/maincluster' set to None
2025-07-03 11:21:39,035 - DEBUG2: Trying to find a matching existing cluster
2025-07-03 11:21:39,035 - DEBUG2: Found an existing cluster where 'name' and 'site' are matching
2025-07-03 11:21:39,035 - DEBUG2: Parsing 'cluster' data structure: maincluster
2025-07-03 11:21:39,035 - DEBUG2: Parsing 'cluster type' data structure: VMware ESXi
2025-07-03 11:21:39,036 - ERROR: This 'site' data structure does not contain the primary key 'name' got: {'name': None}
2025-07-03 11:21:39,036 - INFO: Created new site object: None
2025-07-03 11:21:39,036 - INFO: Cluster 'maincluster' attribute 'scope_type' changed from 'None' to 'dcim.site'
2025-07-03 11:21:39,036 - DEBUG: Updated cluster object: maincluster
2025-07-03 11:21:39,045 - DEBUG: vCenter returned '1' single host cluster
2025-07-03 11:21:39,051 - DEBUG: Parsing vCenter cluster: DC1/maincluster
2025-07-03 11:21:39,052 - DEBUG2: Trying to find site name for cluster 'DC1/maincluster'
2025-07-03 11:21:39,052 - DEBUG2: Found a matching cluster_site_relation '<NONE>' (maincluster) for maincluster
2025-07-03 11:21:39,052 - DEBUG2: Site relation for 'DC1/maincluster' set to None
2025-07-03 11:21:39,052 - DEBUG2: Trying to find a matching existing cluster
2025-07-03 11:21:39,052 - DEBUG2: Found an existing cluster where 'name' and 'site' are matching
2025-07-03 11:21:39,052 - DEBUG2: Parsing 'cluster' data structure: maincluster
2025-07-03 11:21:39,052 - DEBUG2: Parsing 'cluster type' data structure: VMware ESXi
2025-07-03 11:21:39,052 - ERROR: This 'site' data structure does not contain the primary key 'name' got: {'name': None}

[steve-hbt]

Issue created on the same subject #468
And PR related #469

Thanks to @joachimBurket

[bb-Ricardo]

great, thank you. I'll have a look at it.