> Since it sounds like you're experiencing this in an OpenStack cloud, > one workaround would be to boot your server instance with > configdrive enabled; cloud-init knows how to get its metadata that > way as well.
Dear Jeremy, Thank you for your response and the suggestion to enable configdrive. OpenStack-OVS Unfortunately, this approach is not applicable in our case. We are using the official `debian-12-genericcloud-amd64` image, which is specifically designed for cloud environments and intentionally excludes certain hardware-related drivers. Based on available information, the `genericcloud` images lack the necessary drivers for accessing CD-ROM devices. This limitation has been confirmed by Debian developers. Notably, you yourself mentioned in a previous post to the debian-cloud mailing list that these images are targeted for environments such as AWS and Azure, and as a result, CD-ROM drivers were deliberately excluded: > “These images are tailored for environments like AWS and Azure, which do not require CD-ROM access, and therefore CD-ROM drivers are not included.” Reference: https://lists.debian.org/debian-cloud/2024/11/msg00010.html More importantly, our concern here is not merely finding a workaround, but addressing a **functional bug** in cloud-init when running in an IPv6-only environment. While alternative methods might exist under specific conditions, this bug prevents the system from initializing properly when metadata is only available via IPv6. This effectively renders the image unusable in any IPv6-only deployment scenario, making the issue **extremely high priority**, as it blocks access to core cloud functionality. Thank you again for your time and support. Best regards
