yahoo-eng-team team mailing list archive

[Launchpad Bug Tracker <1682487@xxxxxxxxxxxxxxxxxx>]

[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.
https://bugs.launchpad.net/bugs/1682487

Title:
  Instance cannot get IPv6 address after port is detached and re-
  attached to a new instance

Status in neutron:
  Expired

Bug description:
  OpenStack Version: seen in Newton, Mitaka, Liberty, and Kilo.

  Steps to reproduce:

  1. Create a port from a V6 subnet:
  $ neutron port-create --name test-port2 esc-net-v6

  2. Use this port to create an instance:
  $ nova boot --nic port-id=c2a3f6a8-3dbc-486d-baa1-9f2a0e58cde1 --flavor m1.large --image 69e81c12-5d94-4fa3-8805-4b5824cf83c0 instance-ipv6

  3. Check instance using "ip addr" and the V6 IP address is correctly
  assigned to the instance.

  4. Delete the instance. The port will be detached from the instance.
  $ nova delete 523ad0bd-495b-4b2a-8571-5dd9265326dd

  5. Use the same port to create a new instance again:
  $ nova boot --nic port-id=c2a3f6a8-3dbc-486d-baa1-9f2a0e58cde1 --flavor m1.large --image 69e81c12-5d94-4fa3-8805-4b5824cf83c0 instance2-ipv6

  6. Check instance using "ip addr" (I am using a CentOS7 image) and the V6 IP address is NOT correctly assigned to the instance.
  At this point, the instance DOES NOT have an IP address. From now on, the port cannot be re-attached as expected anymore.

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1682487/+subscriptions