You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Two same named VMs in different vCenter clusters, one being online and the other is offline.
Each run the online VM gets an IP assigned, and site changed to the one where the VM is running.
Next run the VM is set as "offline", getting their site id changed again and gets the primary_ipv4 removed. The same applies with attached disks and vNICS. They get removed from the offline variant of the VM and get created again when the online variant VM from the other cluster is being used.
This repeats each run, obviously. Tags are interestingly not being changed (as I would suspect having the other vCenter name as an tag added, and using for filter the next run).
I would expect to have two VMs in netbox, assigned to different sites/clusters instead of having one VM where each run the cluster information gets overwritten by the other VM. Tried running with v1.6.0 and latest development branch.
The text was updated successfully, but these errors were encountered:
Two same named VMs in different vCenter clusters, one being online and the other is offline.
Each run the online VM gets an IP assigned, and site changed to the one where the VM is running.
Next run the VM is set as "offline", getting their site id changed again and gets the primary_ipv4 removed. The same applies with attached disks and vNICS. They get removed from the offline variant of the VM and get created again when the online variant VM from the other cluster is being used.
This repeats each run, obviously. Tags are interestingly not being changed (as I would suspect having the other vCenter name as an tag added, and using for filter the next run).
I would expect to have two VMs in netbox, assigned to different sites/clusters instead of having one VM where each run the cluster information gets overwritten by the other VM. Tried running with v1.6.0 and latest development branch.
The text was updated successfully, but these errors were encountered: