IPv6 not enabling on EC2 when done afterwards (CentOS 7.6)

[Chris NIVARD]

How to reproduce:
=================
On AWS EC2:
- launch a CentOS 7.6 instance with IPv4 only
- once running: assign an IPv6 from AWS EC2, and reboot the instance
- while the instance data is properly populated: the network configuration does not assign the IPv6 to the instance (no connection).

Unsuccessful turnaround attempts:
=================================
A) /etc/cloud/cloud.cfg.d/99-ipv6-networking.cfg
network:
        version: 1
        config:
        - type: physical
                name: eth0
                subnets:
                - type: dhcp6

B) There has been a debate in the CentOS github as to whether AWS was IPv6 RFC compliant, read the entire thread here:
https://github.com/coreos/bugs/issues/1828
A solution provided there for Ubuntu cannot be applied on CentOS.

[Ryan Harper (raharper)]

Hi,

Thanks for filing a bug. Would you be able to confirm which version of cloud-init is installed in the image? And can you attach your /var/log/cloud-init.log as well as /etc/sysconfig/network-scripts/ifcfg-* config files?

Note, cloud-init has support for configuring ipv6 in ec2 since 18.3 I believe so this should be fixed in master. You could also try using the cloud-init daily build:

https://copr.fedorainfracloud.org/coprs/g/cloud-init/cloud-init-dev/

[Launchpad Janitor (janitor)]

[Expired for cloud-init because there has been no activity for 60 days.]

[Chris NIVARD (jcn50)]

Do I have to do anything or has the bug been verified/fixed?

[Dan Watkins (oddbloke)]

Hey Chris,

We're waiting for the debug information that Ryan requested in comment #1 to be able to move this forward. I'm setting this back to Incomplete, please move it to New once you have attached that information.

Thanks!

Dan

[Launchpad Janitor (janitor)]

[Expired for cloud-init because there has been no activity for 60 days.]

[James Falcon (falcojr)]

Tracked in Github Issues as https://github.com/canonical/cloud-init/issues/3346