yahoo-eng-team team mailing list archive

[曾永明 <1714195@xxxxxxxxxxxxxxxxxx>]

Public bug reported:

1.hypervisor is vCenter or kvm
2.the instance status is start in vCenter or kvm
3.the instance status is stop in nova database

   this is High-risk operation，beause when instance is started by
vCenter ,it is is running business, but nova task shutdown instance or
delete instance .so we should synchronized vCenter status to nova
database

** Affects: nova
     Importance: Undecided
     Assignee: 曾永明 (zengyongming)
         Status: New

** Changed in: nova
     Assignee: (unassigned) => 曾永明 (zengyongming)

** Description changed:

  1.hypervisor is vCenter or kvm
  2.the instance status is start in vCenter or kvm
  3.the instance status is stop in nova database
  
-    this is High-risk operation，beause when instance is started by
+    this is High-risk operation，beause when instance is started by
  vCenter ,it is is running business, but nova task shutdown instance or
- .so we should synchronized vCenter status to nova database
+ delete instance .so we should synchronized vCenter status to nova
+ database

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

Title:
  nova task shutdown or deleted instance when instance status in  the
  databse differs from  hypervisor

Status in OpenStack Compute (nova):
  New

Bug description:
  1.hypervisor is vCenter or kvm
  2.the instance status is start in vCenter or kvm
  3.the instance status is stop in nova database

     this is High-risk operation，beause when instance is started by
  vCenter ,it is is running business, but nova task shutdown instance or
  delete instance .so we should synchronized vCenter status to nova
  database

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