View Issue Details
|ID||Project||Category||View Status||Date Submitted||Last Update|
|0000436||AlmaLinux-9||cloud-init||public||2023-10-27 00:36||2023-10-27 20:05|
|Summary||0000436: AWS EC2 images don't work on an IPv6 only Subnet|
|Description||AlmaLinux 9 won't properly initialize on an IPv6 only Subnet in EC2|
|Steps To Reproduce||Create an IPv6 only Subnet in your VPC (choose "No IPv4 CIDR".|
Launch an instance (I used ami-0cee948d95563ce2c, us-east-2 AARCH64). Use the IPv6 only subnet as its subnet.
Watch the boot using the Serial Console. It kind of hangs at the end of the kernel init, and finally will show a login prompt. It doesn't appear that cloud-init works.
(I mounted the image in another instance and saw there was no key in ~ec2-user/.ssh/authorized-keys.)
I can't connect to the instance with SSH.
|Additional Information||This is likely due to:|
However...if you launch AWS Linux 2023 or Debian 12 (I tested 2023-10-13), they work. They both use cloud-init. Which means, this is possible. (Note: Fedora 38 also has the problem...which means AWS Linux fixed the issue, but somehow it didn't make its way to Fedora. Thanks guys.)
I don't know if this is the kind of thing that Alma might be willing to deviate from upstream for. Also, who knows how long it will take upstream to fix.
|Tags||No tags attached.|
Thanks a lot for your contribution.
This is fixed[^1] on 22.2 version of Cloud-init.
Since, the Cloud-init packages on AlmaLinux OS 8.9 and 9.3 are rebased from the 23.1.1 upstream, the patch already included[^2].
We are closely monitoring the upstream patch[^3] which is currently work in progress with implementation of unit tests. Once it's merged we will backport it.