** Description changed:

  [Impact]
  
   * Instances in error state cannot be evacuated.
  
  [Test Case]
  
   * nova evacuate <error_state_instance> <another_compute_host>
   * nova refuses to evacuate the instance because of its state
  
  [Regression Potential]
  
   * None
-  * Passed tempest smoke tests locally.
+  * Passed tempest smoke tests locally.
+ 
+ Note: one simple way to put an instance into error state is to directly
+ change its database record, for example update instances set
+ vm_state='error' where uuid='XXXXXXXX'
  
  We currently allow reboot/rebuild/rescue for an instance in the Error
  state if the instance has successfully booted at least once.
  
  We should allow "evacuate" as well, since it is essentially a "rebuild"
  on a different compute node.
  
  This would be useful in a number of cases, in particular if an initial
  evacuation attempt fails (putting the instance into the Error state).

** Description changed:

  [Impact]
  
   * Instances in error state cannot be evacuated.
  
  [Test Case]
  
   * nova evacuate <error_state_instance> <another_compute_host>
   * nova refuses to evacuate the instance because of its state
  
  [Regression Potential]
  
   * None
   * Passed tempest smoke tests locally.
  
  Note: one simple way to put an instance into error state is to directly
- change its database record, for example update instances set
- vm_state='error' where uuid='XXXXXXXX'
+ change its database record, for example "update instances set
+ vm_state='error' where uuid='XXXXXXXX'"
  
  We currently allow reboot/rebuild/rescue for an instance in the Error
  state if the instance has successfully booted at least once.
  
  We should allow "evacuate" as well, since it is essentially a "rebuild"
  on a different compute node.
  
  This would be useful in a number of cases, in particular if an initial
  evacuation attempt fails (putting the instance into the Error state).

** Description changed:

  [Impact]
  
   * Instances in error state cannot be evacuated.
  
  [Test Case]
  
   * nova evacuate <error_state_instance> <another_compute_host>
   * nova refuses to evacuate the instance because of its state
  
  [Regression Potential]
  
   * None
   * Passed tempest smoke tests locally.
  
  Note: one simple way to put an instance into error state is to directly
  change its database record, for example "update instances set
  vm_state='error' where uuid='XXXXXXXX'"
  
+ 
  We currently allow reboot/rebuild/rescue for an instance in the Error
  state if the instance has successfully booted at least once.
  
  We should allow "evacuate" as well, since it is essentially a "rebuild"
  on a different compute node.
  
  This would be useful in a number of cases, in particular if an initial
  evacuation attempt fails (putting the instance into the Error state).

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1298061

Title:
  nova should allow evacuate for an instance in the Error state

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to