On 2024-08-15 10:33:14 -0400 (-0400), Noah Meyerhans wrote: > On Thu, Aug 15, 2024 at 04:27:01PM +0200, Thomas Goirand wrote: > > There's 2 issues that I'm aware of with our current generic image. > > > > First, the genericcloud image kernel has the SATA AHCI driver stripped-out, > > so then the config drive doesn't work anymore. I reported this here: > > > > https://bugs.debian.org/1078702 > > > > Bastian, do you think, with your kernel team hat, that you can take care of > > this one? > > This is by design. Use the generic image if you need more drivers. > > > The 2nd issue is that booting with IPv6 only connectivity leads to systemd > > waiting forever on the systemd-networkd-wait-online.service unit. When I can > > log in, then: > > > > dhclient -6 enp3s0 > > > > does its job, and I'm getting the IPv6 address. Note that such ipv6-only > > config works with an Ubuntu image. > > > > I have no clue how to fix this in our image. Any idea? > > This isn't an image issue. Pass appropriate cloud-config at launch to > tell cloud-init to configure the network the way you want it, and it > will work. Did you miss Bastian's response to your previous message > about this? https://lists.debian.org/debian-cloud/2024/08/msg00028.html
These issues are interrelated. In OpenStack public clouds, configdrive is a way (and in some cases the only way) to pass userdata to cloud-init. Without a kernel that can automount the configdrive, cloud-init's default behaviors can't be overridden in some cloud environments. I think the main takeaway here is that we should go back to having OpenStack cloud images, because the "generic" cloud images are really only intended for use in the proprietary hyperscalars, not in free/libre open source public cloud providers. It's unfortunate, but understandable as the cloud team seems to focus their efforts on supporting proprietary systems and there's only so many hours in their day. -- Jeremy Stanley
signature.asc
Description: PGP signature
