yahoo-eng-team team mailing list archive

[Cyril Roelandt <cyril.roelandt@xxxxxxxxxxxx>]

Public bug reported:

In the following commands, 'vmtest' is a freshly created virtual
machine.


$ nova show vmtest | grep -E "(status|task_state)"
| OS-EXT-STS:task_state                | -
| status                               | ACTIVE

$ nova rescue vmtest
+-----------+--------------+
| Property  | Value
+-----------+--------------+
| adminPass | 2ZxvzZULT4sr
+-----------+--------------+

$ nova show vmtest | grep -E "(status|task_state)"
| OS-EXT-STS:task_state                | -
| status                               | RESCUE

$ nova pause vmtest

$ nova show vmtest | grep -E "(status|task_state)"
| OS-EXT-STS:task_state                | -
| status                               | PAUSED

$ nova unpause vmtest

$ nova show vmtest | grep -E "(status|task_state)"
| OS-EXT-STS:task_state                | -
| status                               | ACTIVE

Here, we would want the vm to be in the 'RESCUE' state, as it was before
being paused.

$ nova unrescue vmtest
ERROR (Conflict): Cannot 'unrescue' while instance is in vm_state active (HTTP 409) (Request-ID: req-34b8004d-b072-4328-bbf9-29152bd4c34f)

The 'unrescue' command fails, which seems to confirm that the VM was no
longer being rescued.


So, two possibilities:
1) When unpausing, the vm should go back to 'rescued' state
2) Rescued vms should not be allowed to be paused, as is indicated by this graph: http://docs.openstack.org/developer/nova/devref/vmstates.html


Note that the same issue can be observed with suspend/resume instead of pause/unpause, and probably other commands as well.

WDYT ?

** Affects: nova
     Importance: Undecided
         Status: New

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

Title:
  Pausing a rescued instance should be impossible

Status in OpenStack Compute (Nova):
  New

Bug description:
  In the following commands, 'vmtest' is a freshly created virtual
  machine.

  
  $ nova show vmtest | grep -E "(status|task_state)"
  | OS-EXT-STS:task_state                | -
  | status                               | ACTIVE

  $ nova rescue vmtest
  +-----------+--------------+
  | Property  | Value
  +-----------+--------------+
  | adminPass | 2ZxvzZULT4sr
  +-----------+--------------+

  $ nova show vmtest | grep -E "(status|task_state)"
  | OS-EXT-STS:task_state                | -
  | status                               | RESCUE

  $ nova pause vmtest

  $ nova show vmtest | grep -E "(status|task_state)"
  | OS-EXT-STS:task_state                | -
  | status                               | PAUSED

  $ nova unpause vmtest

  $ nova show vmtest | grep -E "(status|task_state)"
  | OS-EXT-STS:task_state                | -
  | status                               | ACTIVE

  Here, we would want the vm to be in the 'RESCUE' state, as it was
  before being paused.

  $ nova unrescue vmtest
  ERROR (Conflict): Cannot 'unrescue' while instance is in vm_state active (HTTP 409) (Request-ID: req-34b8004d-b072-4328-bbf9-29152bd4c34f)

  The 'unrescue' command fails, which seems to confirm that the VM was
  no longer being rescued.

  
  So, two possibilities:
  1) When unpausing, the vm should go back to 'rescued' state
  2) Rescued vms should not be allowed to be paused, as is indicated by this graph: http://docs.openstack.org/developer/nova/devref/vmstates.html

  
  Note that the same issue can be observed with suspend/resume instead of pause/unpause, and probably other commands as well.

  WDYT ?

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