@DustinB Guest tools simply don't support the system I'm running.

Hello,

Virtual machines that have no xen-tools package installed have no way to tell XO which IP addresses they use, which Xen Orchestra apparently interprets as them having no addresses at all and removes all addresses in Netbox which were manually assigned to their virtual interfaces. Would be possible to make XO avoid managing addresses in Netbox for virtual machines with no xen-tools installed?

Perhaps the following patch would be enough to solve the issue?

diff --git a/packages/xo-server-netbox/src/index.js b/packages/xo-server-netbox/src/index.js
index 7b3361180..01c7847fd 100644
--- a/packages/xo-server-netbox/src/index.js
+++ b/packages/xo-server-netbox/src/index.js
@@ -783,6 +783,8 @@ class Netbox {
         log.warn('Synchronizing IPs: cannot find VM from UUID custom field', { vm: nbVm.custom_fields.uuid })
         continue
       }
+      if (!xoVm.managementAgentDetected)
+        continue
 
       // Find the Netbox interface associated with the vif
       const nbVmIfs = filter(nbIfs, { virtual_machine: { id: nbVm.id } })

Unfortunately I couldn't test this patch myself.

Netbox version: 4.2.7
XO commit: 70d59eb

Thanks

I see your point. Thank you!

Hello,

I believe there is an issue with Netbox synchronization plugin. In short, Xen Orchestra does not appear to check if an address of a newly-created VM is already in Netbox and blindly tries to create it. This makes the whole IP address creation step fail for all other VMs even during subsequent synchronizations.

Steps to reproduce the issue:

1. Create an address in Netbox
2. Create a VM in XO with the address from the previous step
3. Run synchronization
4. You will see a "400 Bad Request" error with a message stating that "Duplicate IP address found in global table"
   Xen Orchestra creates your VM with an interface in Netbox, but fails to create and assign the IP address.

I think there are two ways to fix the issue: You could either make XO "adopt" the address when it has to be assigned to a VM, or you could delete the address and create it again. I Think the latter makes more sense as that would strip away all attributes (i.e. tags) which could no longer be correct after the address is assigned to a virtual machine.

I am using a source-built version of XO.

Netbox version: 4.2.7
Xen Orchestra commit: 3c54363

Thanks