The selected cluster is not assigned to this site

[jancovic]

I am trying to fill data to netbox, but I got this error
`ERROR: NetBox returned body: {'cluster': [''The selected cluster (PLN-N2-MMI-VC2-Cluster) is not assigned to this site (PLN-N2-MMI-VC2-Cluster).']}

settings.ini
[source/PLN-N2-MMI-VC2-Cluster]
cluster_site_relation = PLN-N2-MMI-VC2-Cluster = PLN-N2-MMI-VC2-Cluster

error log

2022-12-18 05:40:13,904 - INFO: Creating new NetBox 'virtual machine' object 'vm_test' with data: {'tags': [{'name': 'NetBox-synced'}, {'name': 'Source: PLN-N2-MMI-VC2-Cluster'}], 'name': 'vm_test', 'cluster': 27, 'status': 'active', 'memory': 4096, 'vcpus': 2, 'disk': 200, 'site': 13, 'platform': 18, 'role': 32}
2022-12-18 05:40:14,086 - ERROR: NetBox returned: POST /api/virtualization/virtual-machines/ Bad Request
2022-12-18 05:40:14,086 - ERROR: NetBox returned body: {'cluster': ['The selected cluster (PLN-N2-MMI-VC2-Cluster) is not assigned to this site (PLN-N2-MMI-VC2-Cluster).']}
2022-12-18 05:40:14,086 - ERROR: Request Failed for virtual machine. Used data: {'tags': [{'name': 'NetBox-synced'}, {'name': 'Source: PLN-N2-MMI-VC2-Cluster'}], 'name': vm_test', 'cluster': 27, 'status': 'active', 'memory': 4096, 'vcpus': 2, 'disk': 200, 'site': 13, 'platform': 18, 'role': 32}

[jancovic]

Hello , Any idea where I need to assign it ?
When I included my cluster in cluster_include_filter ... not helped me.

[bb-Ricardo]

You have to define the cluster_site_relation option as described in the config file.

[jancovic]

yes I tried this also before, but I get another error :IndexError: list index out of range

[jancovic]

Hi Ricardo
I tried several changes in cluster_site_relation but I am lost here.
Any idea what I am doing wrong ?

[jancovic]

Hi Ricardo, I updated my github description request with cluster_site_relation = PLN-N2-MMI-VC2-Cluster = PLN-N2-MMI-VC2-Cluster
but i got still same results : 'The selected cluster (PLN-N2-MMI-VC2-Cluster) is not assigned to this site (PLN-N2-MMI-VC2-Cluster).']}
any idea what is wrong ?

[jancovic]

issue fixed by workaround : removing all old VMs inventories and run new scan.