2017-10-04 18:57:42 |
Trinh Lee |
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. |
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. |
|