[Expired for neutron because there has been no activity for 60 days.]
** Changed in: neutron
Status: Incomplete => Expired
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
IPv4 subnets added when VM is already up on an IPv6 subnet on the same
network, does not enable VM ports to get IPv4 address
Status in neutron:
On both stable/pike and stable/ocata, we performed the following
1. Create a network
2. Create an IPv6 subnet in SLAAC Mode (both RA mode and Address mode)
3. Create a router
4. Attach the IPv6 subnet to the router
5. Now boot VMs with the network-id.
6. Make sure VMs are up and able to communicate via their Global and
Link-Local IPv6 addresses.
7. Create an IPv4 subnet on the same network.
After step 5, you will notice that the booted VM neutron ports fixed-
ips are not updated with IPv4 subnets automatically.
The user has to manually update the VM Neutron ports via port-update
command with the IPv4 subnet-id and then go back to the VM and recycle
eth0 after which only the VMs will get the IPv4 address.
The DHCP Neutron port alone got updated automatically with the IPv4
address in addition to IPv6 address with the above steps.
Any new VMs spawned after both IPv4 and IPv6 subnets are available on
the network, is able to get both the addresses and its Neutron Ports
in the control plane also reflect the same.
BTW, if the above set of steps are followed just by swapping the order
where we create IPv4 subnets first, then boot VMs, create an IPv6
subnet on the same network, the VM Neutron Ports fixed-ips get updated
automatically with the new assigned IPv6 Global addresses on the IPv6
To manage notifications about this bug go to:
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : email@example.com
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp