@pdonias Yes, I was running a newer version than that but just to make sure I upgraded to 8068b83ffe58e6caed0cac5816ac2690479a9c41. Still the same problem, unfortunately.

I'm not too sure if it matters, but there are VMs running in the pool that does not have an IP in a "smaller" /24 prefix. So if the prefixes 192.168.0.0/16 and 192.168.100.0/24 are in Netbox, there might be VMs using IPs other than the ones in the 192.168.100.0/24 prefix.

Let's say I have the prefix 192.168.0.0/16 added in Netbox, and a sub-prefix 192.168.100.0/24. Now, if I have a VM running using IP 192.168.100.69, the Netbox plugin will create this IP as 192.168.100.69/16 instead of 192.168.100.69/24.

Is this intended behavior and if not, should I open an issue about it on GitHub? Thanks!

@pdonias Thanks a lot, this solved the problem!

@olivierlambert Alright, I upgraded to Xen Orchestra commit 82452 but I am still experiencing the same issue.

Sorry for bringing up such an old topic, but I have ran into the same issue (when syncing a certain pool to Netbox). I've used xo-cli --list-objects --addresses type=VM \$pool=<uuid of pool with problems> to get an idea of the data it's trying to import. There are no instances where there are two IP-addresses seperated by a space (like x.x.x.x y.y.y.ythe ) but there is one instance with an empty value.

  {
    "addresses": {
      "0/ipv4/0": "x.x.x.x",
      "1/ipv4/0": "y.y.y.y",
      "2/ipv4/0": ""
    }
  },

I'm running Xen Orchestra commit 667d0 (xo-server 5.96.0 and xo-web 5.97.2).