Netbox Plugin: Error: ipaddr: the address has neither IPv6 nor IPv4 format

[pdonias]

Thanks @theaeon. Could you check if some of your VMs on that pool have invalid IP addresses? You can do that from the home page by filtering only the VMs on that pool (Pools selector at the top of the page) and expanding the details for all the VMs to show the IP addresses (hamburger button at the top right hand corner). Each IP address must be in its own blue rectangle and with the correct format for either IPv4 or IPv6. Let me know if this is too hard to check, we'll find another way.

[theAeon]

pdonias One of my VMs isn't reporting an IP address. Do you think that could do it?

[pdonias]

theAeon No, that's a normal case and it's handled properly. The issue would be if one of the IPs has 2 IPs in the same field separated by a white space like: "x.x.x.x y.y.y.y", or if the field is just empty or anything else that doesn't look like a proper IP address.

If you want to check the addresses more thoroughly, you can install xo-cli with npm i -g xo-cli, log into your XO with xo-cli --register <XO-Server URL> <username> <password> and then run xo-cli --list-objects --addresses type=VM \$pool=<pool ID>.

[vilhelm]

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).

[olivierlambert]

Hi!

Thanks for the report Please update to the latest commit available, and confirm you still have the issue. I'm adding pdonias in the loop

[vilhelm]

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

[pdonias]

Hi vilhelm, could you try on the branch empty-ip and let us know if you still have the issue please?

[vilhelm]

pdonias Thanks a lot, this solved the problem!

[pdonias]

vilhelm Thanks for testing, we'll fix it in master

[pdonias]

vilhelm That's fixed: https://github.com/vatesfr/xen-orchestra/pull/6328. Thanks again for the report

pdonias opened this pull request in vatesfr/xen-orchestra

closed fix(xo-server/xapi-object-to-xo): handle guest metrics reporting empty IP field #6328