Volume Retype of attached volume with active VM does not work

[Trinh Lee]

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.

[Sylvain Bauza (sylvain-bauza)]

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.

[Sean McGinnis (sean-mcginnis)]

Please attach the cinder logs.

[Trinh Lee (trinhlee)]

Are you able to reproduce the issue?
I didn't see much error from the logs...the attached volume instance just got stuck at "retyping" status forever....
Will attach the logs later in this ticket but it is good if you can try to reproduce. Thanks.

[Sean McGinnis (sean-mcginnis)]

Attached logs don't appear to capture what was going on at the time.

Make sure you have the [nova] section configured. When a volume is attached Cinder needs to call out to Nova to handle the volume moving.