AWS instances created by juju don't have an IPv6 assigned, even if "auto-assign IPv6 addresses" is enabled for the subnet
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Canonical Juju |
Fix Committed
|
Medium
|
Thomas Miller |
Bug Description
Hi,
When creating AWS instances with juju, even if I have enabled auto-assignment of IPv6 addresses in all my subnets, the instances don't have an IPv6 assigned to them.
To reproduce :
- make sure that your VPC (default or not, if it's not the default, you'll have to bootstrap with "--config vpc-id=$vpc) has an IPv6 CIDR
- make sure that all the subnets of the VPC have an IPv6 CIDR
- make sure that all the subnets have "auto-assign IPv6" enabled
Then, bootstrap.
Result : the instance doesn't have an IPv6 assigned, and I need to assign one from the console (or using the API/CLI), and only then will dhclient -6 do the right thing.
Expected result : the instance is at least assigned an IPv6 in the management console. For the instance to do dhcp itself, I think we'll need cloud-init / UserData to be told so.
Also, the secgroups created by juju only have IPv4 rules. And, finally, the default routing table created by Amazon doesn't have a default gateway for IPv6 (you'll want to add one for ::/0, using the same igw as IPv4).
This is with juju 2.2-beta4. I couldn't find anything related to this in the debug output of "juju bootstrap".
Thanks
summary: |
- AWS instances created by juju don't have an associated IPv6, even if + AWS instances created by juju don't have an IPv6 assigned, even if "auto-assign IPv6 addresses" is enabled for the subnet |
tags: | added: canonical-is |
affects: | juju-core → juju |
tags: | added: ipv6 |
Changed in juju: | |
assignee: | nobody → Thomas Miller (tlmiller) |
This has affected us deploying dualstack services so it would be good if it received more priority.