Hetnzer: Channel 24.05 not working

[theduke]

I just tried to set up a new Hetzner Cloud server with the just released 24.05.

The installation works, but after the reboot the network isn't reachable anymore.

I connected with the console, it looks like the interfaces are configured correctly, but no default gateway is set up. (ip route is empty).

[CherryKitten]

can confirm, had the same problem a few days ago

[Zaunei]

I tried it with an Ubuntu 22.04 CX22 instance today and had no problems with the network after the reboot. I just used the normal command right after login into the new VM via SSH:

curl https://raw.githubusercontent.com/elitak/nixos-infect/master/nixos-infect | PROVIDER=hetznercloud NIX_CHANNEL=nixos-24.05 bash 2>&1 | tee /tmp/infect.log

[gbytedev]

Possibly related: networking doesn't work after the update to 24.05.

This box has been working well until today since it was originally provisioned with nixos-infect box to nixos 22.11.

I suspect the default network configuration added by nixos-infect is now erroneous.

[tcurdt]

What worked for me is to use PROVIDER=hetznercloud NIX_CHANNEL=nixos-23.11 and then switch to 24.05 once the system is up. Really not ideal. But since flakes are not supported by nixos-infect not much of a difference.

[ahirner]

I tried it with an Ubuntu 22.04 CX22 instance today and had no problems with the network after the reboot. I just used the normal command right after login into the new VM via SSH:

curl https://raw.githubusercontent.com/elitak/nixos-infect/master/nixos-infect | PROVIDER=hetznercloud NIX_CHANNEL=nixos-24.05 bash 2>&1 | tee /tmp/infect.log

The issue does not reproduce if rebooting a new system, or switching then rebooting a non-flake system.
After including one in our flakes config, networking fails:

Removing this link-local ipv6 address from the interfaces.ipv6.addresses produced by nixos-infect allows error free rebooting and the system stays reachable: