In ipv6 enabled networks, xen orchestra fails to use happy eyeballs

[braiam]

Are you using XOA or XO from the sources?

XOA

Which release channel?

stable

Provide your commit number

No response

Describe the bug

If there's a interface with global ipv6 address, xen orchestra will fail to connect to the internet and therefore registering

https://en.wikipedia.org/wiki/Happy_Eyeballs

Error message

✔  1/16 - Node version
✔  2/16 - Memory
✔  3/16 - xo-server config syntax
✖  4/16 - Appliance registration: not registered
✔  5/16 - Disk space for /
✔  6/16 - Disk space for /var
✔  7/16 - Native SMB support
✔  8/16 - Fetching VM UUID
✔  9/16 - XOA version
✔ 10/16 - /var is writable
✔ 11/16 - NTP synchronization
✔ 12/16 - xoa-support user
✔ 13/16 - local SSH server
✖ 14/16 - Internet connectivity: Error: connect ENETUNREACH 2a01:240:ab08::4:80
    at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1555:16) {
  errno: -101,
  code: 'ENETUNREACH',
  syscall: 'connect',
  address: '2a01:240:ab08::4',
  port: 80,
  url: 'http://xen-orchestra.com/'
}
✔ 15/16 - npm version
✖ 16/16 - XOA status: not up-to-date, please run xoa-updater

To reproduce

Install xoa in a ipv6 enabled network

Expected behavior

XOA should try to connect using both ipv4 and ipv6

Screenshots

No response

Node

18.20.2

Hypervisor

8.2.1

Additional context

No response

[julien-f]

Likely related to the issue nodejs/node#48145

You can work around this by increasing the default autoSelectFamilyAttemptTimeout of 250 (miliseconds) in /etc/xoa-updater/config.autoSelectFamilyAttemptTimeout.json:

{
  "autoSelectFamilyAttemptTimeout": 1000
}

[julien-f]

Also, you need to upgrade before being able to do that.

If you need help, please open a proper support ticket and a support tunnel.

[braiam]

you need to upgrade before being able to do that.

Upgrade to what? This is a fresh deployment of XOA. Should I move away from stable into latest? I can't do that if I can't register. So what I did was keeping a tight loop removing the ipv6 address and hoped it will hit the correct timing. It successfully did that, but it's still sticky trying to connect with ipv6, even with the file created:

• node: 20.18.0
• npm: 10.8.3
• xen-orchestra-upload-ova: 0.1.6
• xen-orchestra-web: 0.6.0
• xo-server: 5.168.1
• xo-server-telemetry: 0.7.0
• xo-server-xoa: 0.29.3
• xo-web-free: 5.167.0
• xoa-cli: 0.40.0
• xoa-updater: 0.50.6

I'm capable of following instructions, but it doesn't seem that nodejs is behaving as expected.