instance won't reboot after scaleway bumped initrd to v3.12.6-0-g94f40b6

[stuffo]

you will end up with an unconfigured network in initrd. this will prevent any further work of scaleways initrd as the metadata server is unreachable.

workaround

if you didn't reboot till now, and wan't to avoid this bug, its enough to do this once:
sudo rm /boot/.archkernel-version
sudo reboot
if you already rebooted and ended up with a stuck initrd:
use Scaleway's Resuce bootscript to mount your nbd and enter the commands above.

background

I was too lazy to add code for detecting a initrd change. When the Arch kernel doesn't change, you end up with a previous version of the scaleway initrd which in this case uses an old approach to configure the network. simulating a kernel change forces initrd rebuild using the current version.

[streaps]

What about scaleway-ubuntukernel? Same problem?

[stuffo]

yes. use the same workaround if you run into this.
if you just started using this package, you won't run into this, as it is only related to instances created before the last initrd change (i think about 16th of june).