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
6
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:

http://paste.openstack.org/show/488310/

Changed in nova:
assignee: nobody → bailin.zhang (bailin-zhang)
Revision history for this message
Markus Zoeller (markus_z) (mzoeller) wrote :

@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.

Changed in nova:
status: New → Confirmed
importance: Undecided → Medium
tags: added: network neutron
Revision history for this message
Markus Zoeller (markus_z) (mzoeller) wrote :

@JianGang Weng:
Since you set yourself as assignee of the bug it is commonly expected
that you provide a patch for this bug within the next 2 weeks. I also
switch it to "In Progress" to signal to other contributors that you
are already working on the patch.

Changed in nova:
status: Confirmed → In Progress
Revision history for this message
bailin.zhang (bailin-zhang) wrote :

sorry, the log of #3 is a new bug.

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
Revision history for this message
Anusha Unnam (anusha-unnam) wrote :

There is no patch submitted for this bug for more than 6 months, removing the assignee and setting the bug status back to confirmed.

Changed in nova:
assignee: bailin.zhang (bailin-zhang) → nobody
status: In Progress → Confirmed
Revision history for this message
Anusha Unnam (anusha-unnam) wrote :

This is not reproducible. I followed the same steps you mentioned and I didn't get port already in-use error. I was able to reuse the port. SO i think now this bug is invalid.

Revision history for this message
Anusha Unnam (anusha-unnam) wrote :

@JianGang Weng:
Sorry I didn't notice this is in liberty. I tried in current master and it worked well.
Is this bug still valid in liberty?

Revision history for this message
Anusha Unnam (anusha-unnam) wrote :

Since the reporter of this bug hasn't replied back, marking this bug as incomplete.
If you think this bug is still valid in liberty, please provide the logs for this bug from liberty and change the status.

Changed in nova:
status: Confirmed → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for OpenStack Compute (nova) because there has been no activity for 60 days.]

Changed in nova:
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.