yahoo-eng-team team mailing list archive

[Sylvain Bauza <sbauza@xxxxxxx>]

Sicne the command is issued from the Cinder CLI, I'm not seeing at first
glance that as a nova problem. Triaging the bug to Cinder, but feel free
to put the status to New for Nova if something is required from its
side.

** Also affects: cinder
   Importance: Undecided
       Status: New

** Changed in: nova
       Status: New => Invalid

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

Title:
  Volume Retype of attached volume with active VM does not work

Status in Cinder:
  New
Status in OpenStack Compute (nova):
  Invalid

Bug description:
  Steps to reproduce:

  1. Boot a Nova VM instance and make sure it is ACTIVE and running fine.
  2. Create a new Cinder volume.
  3. Attach the above Cinder volume to the above active (running) VM.
  3. Try to migrate this ATTACHED volume between different storages of the same type (cinder retype with --migration-policy on-demand )
  4. The retyped volume gets stuck at "Retyping" state forever.

  Expected result:
  The attached volume should be retyped to another storage.

  Notes: no specific errors observed from the cinder-volumes.log or cinder-api.log.
  The attached volume is simply stuck at "Retyping" state. A new (temporary) volume was created but stuck at "Migrating" state forever as well.

  This issue was observed on the latest Liberty branch. But I believe
  the same issue might happen with Ocata as well.

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