LVM revert is not synchronous

Bug #1707943 reported by Ben Swartzlander on 2017-08-01
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack Shared File Systems Service (Manila)
Ben Swartzlander

Bug Description

The initial implementation of revert-to-snapshot in the Manila LVM driver does the revert in the background, which causes problems because later operations can fail if they occur too soon after a revert is initiated.

The revert operation should be synchronous to avoid these issues.

Changed in manila:
milestone: none → pike-rc1
importance: Undecided → Medium
assignee: nobody → Ben Swartzlander (bswartz)
status: New → In Progress
Revision history for this message
Ben Swartzlander (bswartz) wrote :
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to manila (master)

Submitter: Jenkins
Branch: master

commit 5cb87d5dc3cc6ac11de07ed9971f5eff747c6e44
Author: Ben Swartzlander <email address hidden>
Date: Fri Jul 28 14:50:45 2017 -0400

    Fix multiple issues with revert to snapshot in LVM

    Reverts with the LVM driver were happening asynchronously
    which resulted in unreliable behavior. This change makes
    the reverts synchronous.

    Also, the driver now unexports and unmounts both the share and
    the snapshot during the revert (required to make the operation
    synchronous) which requires changing the driver interface to
    include the snapshot access rules in addition to the share access

    Closes-bug: #1707943

    Change-Id: Ifea1799e1d2e3963fec7e90ce3f9cb47b9f02f4f

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  Edit
Everyone can see this information.

Other bug subscribers