LVM revert is not synchronous

[Ben Swartzlander]

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.

[Ben Swartzlander (bswartz)]

https://review.openstack.org/#/c/488569/

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/488569
Committed: https://git.openstack.org/cgit/openstack/manila/commit/?id=5cb87d5dc3cc6ac11de07ed9971f5eff747c6e44
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
    rules.

    Closes-bug: #1707943

    Change-Id: Ifea1799e1d2e3963fec7e90ce3f9cb47b9f02f4f

[OpenStack Infra (hudson-openstack)]

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