Failure in interface-attach may leave port around
Bug #1338551 reported by
Drew Thorstensen
This bug affects 5 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Compute (nova) |
Fix Released
|
Low
|
Eli Qiao |
Bug Description
When the interface-attach action is run, it may be passed in a network (but no port identifier). Therefore, the action allocates a port on that network. However, if the attach method fails for some reason, the port is not cleaned up.
This behavior would be appropriate if the invoker had passed in a port identifier. However if nova created the port for the action and that action failed, the port should be cleaned up as part of the failure.
The allocation of the port occurs in nova/compute/
Changed in nova: | |
assignee: | nobody → Drew Thorstensen (thorst) |
tags: | added: network neutron |
Changed in nova: | |
assignee: | Drew Thorstensen (thorst) → Paul Ward (wpward) |
Changed in nova: | |
assignee: | Paul Ward (wpward) → Eli Qiao (taget-9) |
Changed in nova: | |
status: | In Progress → Confirmed |
Changed in nova: | |
status: | Confirmed → In Progress |
tags: | added: juno-backport-potential |
Changed in nova: | |
assignee: | Eli Qiao (taget-9) → Davanum Srinivas (DIMS) (dims-v) |
Changed in nova: | |
assignee: | Davanum Srinivas (DIMS) (dims-v) → Eli Qiao (taget-9) |
Changed in nova: | |
importance: | Undecided → Low |
Changed in nova: | |
milestone: | none → kilo-3 |
status: | Fix Committed → Fix Released |
Changed in nova: | |
milestone: | kilo-3 → 2015.1.0 |
To post a comment you must log in.
Fix proposed to branch: master /review. openstack. org/105238
Review: https:/