This bug was originally filed in Launchpad as LP: #1818641
Launchpad details
affected_projects = []
assignee = None
assignee_name = None
date_closed = 2019-11-17T04:17:30.909347+00:00
date_created = 2019-03-05T11:15:06.650720+00:00
date_fix_committed = None
date_fix_released = None
id = 1818641
importance = medium
is_complete = True
lp_url = https://bugs.launchpad.net/cloud-init/+bug/1818641
milestone = None
owner = jcn50
owner_name = Chris NIVARD
private = False
status = expired
submitter = jcn50
submitter_name = Chris NIVARD
tags = ['aws', 'ec2', 'ipv6']
duplicates = []
Launchpad user Chris NIVARD(jcn50) wrote on 2019-03-05T11:15:06.650720+00:00
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:
coreos/bugs#1828
A solution provided there for Ubuntu cannot be applied on CentOS.
This bug was originally filed in Launchpad as LP: #1818641
Launchpad details
Launchpad user Chris NIVARD(jcn50) wrote on 2019-03-05T11:15:06.650720+00:00
How to reproduce:
On AWS EC2:
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:
coreos/bugs#1828
A solution provided there for Ubuntu cannot be applied on CentOS.