[Storwize] Fix issue while extending a volume with replication enabled

Bug #1920870 reported by Venkata krishna Thumu
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Cinder
Fix Released
Medium
Venkata krishna Thumu

Bug Description

Current IBM SVF Storwize driver extending a volume with replication enabled by deleting and recreating the Remote-copy relationship which leads to some critical problems such as data-sync between primary and secondary volumes and relationship recreation issues might be making the volume unavailable to the user.

Through this patch, we are fixing the former issues by stopping and starting the relationship instead of breaking the relationship and handling the exceptions for the negative scenarios such as extending a thick provisioned mirror volume and extending a mirror volume that is a part of a group.

Changed in cinder:
assignee: nobody → Venkata krishna Thumu (venkatakt)
Changed in cinder:
importance: Undecided → Medium
tags: added: extend ibm replication svf volume
Changed in cinder:
status: New → In Progress
description: updated
description: updated
description: updated
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to cinder (master)

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

commit bdcee852321ee414d79da8a0ed9bd95f3369bd9d
Author: venkatakrishnathumu <email address hidden>
Date: Wed Mar 31 17:13:44 2021 +0000

    [SVF] Fix extend issue for mirroring volumes

    [Spectrum Virtualize Family] Fixed volume extend issue for volumes
    with replication enabled by avoiding both delete RC relationship
    and create RC relationship of that volume.

    Closes-Bug: #1920870

    Change-Id: Id8dfa3d756142a17a50edf969d2ec84cfe524f4f

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

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

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.