When an error status VM was deleted which a port belong to, The port can not be assigned to other VM again
Bug #1550201 reported by
JianGang Weng
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Compute (nova) |
Expired
|
Medium
|
Unassigned |
Bug Description
In version liberty:
1. When you create an VM with a given logic port, for some problem(such as all of the neutron agents is offline), the instance fall to the error status.
2. Resolve the problems, and delete the error VM Instance.
3. Create an new VM with the old port, then you will find the port can't be assigned
Detail Operation process:
Changed in nova: | |
assignee: | nobody → bailin.zhang (bailin-zhang) |
Changed in nova: | |
assignee: | bailin.zhang (bailin-zhang) → nobody |
Changed in nova: | |
status: | In Progress → Confirmed |
description: | updated |
Changed in nova: | |
assignee: | nobody → bailin.zhang (bailin-zhang) |
Changed in nova: | |
status: | Confirmed → In Progress |
To post a comment you must log in.
@JianGang Weng:
Looks like an actual bug. I would expect that the port can be reused
after I delete the error'ed VM. Could you please attach a log to
show where in the code this happens?
I'm adding the Neutron tag as the root cause could be in the
nova<->neutron interaction.