yahoo-eng-team team mailing list archive

["Chung Chih, Hung" <lyan.h@xxxxxxxxxxxxxx>]

Public bug reported:

When I try to using heat to boot server which flavor is m1.small (this is just a sample)
And I had created one neutron port which will assign to the server
Also my compute host's memory is not big enough to supply such flavor
Therefore my heat stack will boot a server with existed neutron port and it will failed on "No valid host was found"

Heat had retry mechanism, it will delete failed server and then boot new one
But nova wouldn't detach neutron port
It will raise exception which is "Port a67b3bf1-3b3c-4441-a614-2c16240c376c is still in use" at next boot step for heat

You can using nova boot command to reproduce such bug
1. create neutron port in any subnet
2. boot one server with neutron port which was created at step1 (You can chose large flavor cause it will failed at scheduler)
3. delete error server
4. using neutron command to show port which was created at step 1
Finally you can find the neutron port was still attached to error server. Even it was been destroy.
In normal case, if me delete succeed servers, nova will delete or detach neutron port.

** Affects: nova
     Importance: Undecided
     Assignee: Chung Chih, Hung (lyanchih)
         Status: New

** Changed in: nova
     Assignee: (unassigned) => Chung Chih, Hung (lyanchih)

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1512559

Title:
  remove failed server wouldn't detach/delete neutron port

Status in OpenStack Compute (nova):
  New

Bug description:
  When I try to using heat to boot server which flavor is m1.small (this is just a sample)
  And I had created one neutron port which will assign to the server
  Also my compute host's memory is not big enough to supply such flavor
  Therefore my heat stack will boot a server with existed neutron port and it will failed on "No valid host was found"

  Heat had retry mechanism, it will delete failed server and then boot new one
  But nova wouldn't detach neutron port
  It will raise exception which is "Port a67b3bf1-3b3c-4441-a614-2c16240c376c is still in use" at next boot step for heat

  You can using nova boot command to reproduce such bug
  1. create neutron port in any subnet
  2. boot one server with neutron port which was created at step1 (You can chose large flavor cause it will failed at scheduler)
  3. delete error server
  4. using neutron command to show port which was created at step 1
  Finally you can find the neutron port was still attached to error server. Even it was been destroy.
  In normal case, if me delete succeed servers, nova will delete or detach neutron port.

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