Public bug reported:
Nova sends a request for port unbind with binding host "" and this can
sometimes lead to a problem when nova's cache is different than
Neutron's view of instance-port mappings.
Steps
1. Create a neutron port
2. Create a VM and launch instance with this port
3. Shutdown nova compute and neutron agents on compute node where this VM was
spawned
4. Unbind port from VM and delete the VM(Notice offline delete is a DB
operation as request cant be completed on compute node as it is down)
5. Now create a new VM with same port on a different compute node
6. Bring up nova compute on the first node
After 30 minutes the running deleted instance reap runs and detects a VM
in libvirt which is not present in nova database. It cleans up the VM
but in the process it unbinds the pre-existing port which is now
attached to a completely different VM on a different compute node
Root cause: nova unbind request does not check if port is bound to
current instance from Neutron standpoint
** Affects: nova
Importance: Undecided
Assignee: AJAY KALAMBUR (akalambu)
Status: New
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1634269
Title:
Incorrect port unbind request on instance delete
Status in OpenStack Compute (nova):
New
Bug description:
Nova sends a request for port unbind with binding host "" and this can
sometimes lead to a problem when nova's cache is different than
Neutron's view of instance-port mappings.
Steps
1. Create a neutron port
2. Create a VM and launch instance with this port
3. Shutdown nova compute and neutron agents on compute node where this VM was
spawned
4. Unbind port from VM and delete the VM(Notice offline delete is a DB
operation as request cant be completed on compute node as it is down)
5. Now create a new VM with same port on a different compute node
6. Bring up nova compute on the first node
After 30 minutes the running deleted instance reap runs and detects a
VM in libvirt which is not present in nova database. It cleans up the
VM but in the process it unbinds the pre-existing port which is now
attached to a completely different VM on a different compute node
Root cause: nova unbind request does not check if port is bound to
current instance from Neutron standpoint
To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1634269/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
