SolidFire retype fails due to volume status as retyping and not available
Bug #1942090 reported by
Fábio Oliveira
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Cinder |
Fix Released
|
Medium
|
Fábio Oliveira |
Bug Description
Env:
Two enabled solidfire backends
Steps to reproduce:
1. Create a volume type for each solidfire backend with extra_specs as volume_backend_name "backend name <n>"
2. Create a volume with the volume type for the first backend
3. Run the retype with the other volume type: cinder retype --migration-policy on-demand <volume-name> <other-volume-type>
Expected result:
Successful retype
Actual result:
Invalid volume: Volume status must be 'available' to execute storage assisted migration.
Changed in cinder: | |
assignee: | nobody → Fábio Oliveira (fabiooliveira1) |
tags: | added: retype solidfire |
Changed in cinder: | |
importance: | Undecided → Medium |
To post a comment you must log in.
Fix proposed to branch: master /review. opendev. org/c/openstack /cinder/ +/806616
Review: https:/