share migration does not detect share-group-snapshots

Bug #1660336 reported by Rodrigo Barbieri
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack Shared File Systems Service (Manila)
Fix Released
Rodrigo Barbieri

Bug Description

Share migration has 2 behaviors when it comes to snapshots:

1) host-assisted migration cannot migrate snapshots, so it should error-out.
2) driver-assisted migration, when driver supports it, can migrate snapshots.

Currently, if share is member of a group, and has a group snapshot, share migration is allowing the migration to start. In case of a host-assisted migration, it is not detecting the presence of any snapshots, and is proceeding with the migration.

Steps to reproduce:

1) create share group X in host W
2) create share Y in group X
3) create a group snapshot Z of group X
4) attempt to migrate share Y to host U
5) migration will succeed. If using the generic driver, it will fail to delete the source instance, as it has snapshots, but will delete anyway, leaving the group-snapshot inconsistent.

Changed in manila:
importance: Undecided → High
milestone: none → ocata-rc1
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to manila (master)

Fix proposed to branch: master

Changed in manila:
assignee: nobody → Rodrigo Barbieri (rodrigo-barbieri2010)
status: New → In Progress
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to manila (master)

Submitter: Jenkins
Branch: master

commit 26c803ea95b7e9b00822a867fc4b9bc04a4f10d4
Author: Rodrigo Barbieri <email address hidden>
Date: Wed Feb 1 15:41:03 2017 -0200

    Blocked migration of shares within share groups

    In Ocata, coordination between share migration and share groups
    features was not implemented. So, restrict its usage for now.


    Change-Id: Id15453590685aa9c7788e79a33ca98b4dcc8a3ea
    Closes-bug: #1660336
    Closes-bug: #1660319

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

This issue was fixed in the openstack/manila release candidate.

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

Other bug subscribers