Instance delete should fail in neutron.delete_port() fails
Bug #1233104 reported by
Phil Day
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Compute (nova) |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
Currently neutronv2 deallocate_
It would be cleaner if Nova only continued with the delete if a PortNotFound is raised, but otherwise fails, which would result in the Instance remaining in a Error state with an entry in the instance_fault table so that the user can address the issue or at least re-try the delete.
tags: | added: network |
Changed in nova: | |
milestone: | none → icehouse-3 |
Changed in nova: | |
status: | Fix Committed → Fix Released |
Changed in nova: | |
milestone: | icehouse-3 → 2014.1 |
To post a comment you must log in.
Hi, /github. com/openstack/ nova/blob/ master/ nova/network/ neutronv2/ api.py# L403. /github. com/openstack/ nova/commit/ b12da559b6a40fb a4e4431d74372b5 e350047525
From the code it looks like this isssue is already dealt with - please see - https:/
This was resolved in https:/
Thanks
Gary