yahoo-eng-team team mailing list archive

[Launchpad Bug Tracker <1818641@xxxxxxxxxxxxxxxxxx>]

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

** Changed in: cloud-init
       Status: Incomplete => Expired

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to cloud-init.
https://bugs.launchpad.net/bugs/1818641

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

Status in cloud-init:
  Expired

Bug description:
  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.

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1818641/+subscriptions