yahoo-eng-team team mailing list archive

["Markus Zoeller \(markus_z\)" <mzoeller@xxxxxxxxxxxxxxxxxx>]

This is an automated cleanup. This bug report has been closed because it
is older than 18 months and there is no open code change to fix this.
After this time it is unlikely that the circumstances which lead to
the observed issue can be reproduced.

If you can reproduce the bug, please:
* reopen the bug report (set to status "New")
* AND add the detailed steps to reproduce the issue (if applicable)
* AND leave a comment "CONFIRMED FOR: <RELEASE_NAME>"
  Only still supported release names are valid (LIBERTY, MITAKA, OCATA, NEWTON).
  Valid example: CONFIRMED FOR: LIBERTY


** Changed in: nova
   Importance: Low => Undecided

** Changed in: nova
       Status: Confirmed => Expired

-- 
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/1310835

Title:
  VMWARE: Instance becomes unmanageable once in in ERROR/Deleting mode

Status in OpenStack Compute (nova):
  Expired

Bug description:
  Steps to reproduce:
  1. Startup n-cpu node pointing to a cluster say "c1".
  2. Spawn few instances
  3. Kill/Stop n-cpu node and change the configuration i.e. from cluster "c1" to "c2"
  4. Start n-cpu node
  5. Terminate instances spawned in step 2

  Actual result:
  Instances are stuck in ERROR/Deleting state and become unmanageable even after reconfiguring cpu node back to "c1" and these instances now can only be managed via vsphere client.

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