← Back to team overview

yahoo-eng-team team mailing list archive

[Bug 1550171] [NEW] When an error status VM was deleted which a port belong to, The port can not be assigned to other VM again

 

Public bug reported:

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/

** Affects: neutron
     Importance: Undecided
     Assignee: JianGang Weng (weng-jiangang)
         Status: In Progress

** Changed in: neutron
     Assignee: (unassigned) => JianGang Weng (weng-jiangang)

** Changed in: neutron
       Status: New => In Progress

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1550171

Title:
  When an error status VM was deleted which a port belong to,  The port
  can not be assigned to other VM again

Status in neutron:
  In Progress

Bug description:
  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/

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1550171/+subscriptions


Follow ups