SolidFire retype fails due to volume status as retyping and not available

Bug #1942090 reported by Fábio Oliveira
8
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)
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to cinder (master)

Fix proposed to branch: master
Review: https://review.opendev.org/c/openstack/cinder/+/806616

Changed in cinder:
status: New → In Progress
tags: added: retype solidfire
Changed in cinder:
importance: Undecided → Medium
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to cinder (master)

Reviewed: https://review.opendev.org/c/openstack/cinder/+/806616
Committed: https://opendev.org/openstack/cinder/commit/853f082884a06e318e7d07249c708c56fd5cf0e3
Submitter: "Zuul (22348)"
Branch: master

commit 853f082884a06e318e7d07249c708c56fd5cf0e3
Author: Fabio Oliveira <email address hidden>
Date: Mon Aug 30 11:52:41 2021 -0300

    NetApp Solidfire: Fix retype and name exception on migration

    While performing retype or migrate on a volume the name exception
    occurs due to the check on all backends including the origin.
    The retype status exception occurs because the only accepted state
    is available, but retype changes the status to retyping.

    This change just assures to check the name on the target backend
    and also adds retyping as a valid status for migrate condition.

    Change-Id: Ic09d65a0a6ecbb529dc0e4b041650ead449e1273
    Closes-Bug: 1942090
    Closes-Bug: 1932964

Changed in cinder:
status: In Progress → Fix Released
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/cinder 20.0.0.0rc1

This issue was fixed in the openstack/cinder 20.0.0.0rc1 release candidate.

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to cinder (stable/xena)

Fix proposed to branch: stable/xena
Review: https://review.opendev.org/c/openstack/cinder/+/882059

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Change abandoned on cinder (stable/xena)

Change abandoned by "Elod Illes <email address hidden>" on branch: stable/xena
Review: https://review.opendev.org/c/openstack/cinder/+/882059
Reason: stable/xena branch of openstack/cinder is about to be deleted. To be able to do that, all open patches need to be abandoned. Please cherry pick the patch to unmaintained/xena if you want to further work on this patch.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.