OpenStack Shared File Systems Service (Manila)

  1. Bug #1499347
  2. Comment #2

Comment 2 for bug 1499347

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to manila (master)

Reviewed: https://review.openstack.org/228772
Committed: https://git.openstack.org/cgit/openstack/manila/commit/?id=4e4c8759a25fa18384b45f4150000aacfaed035a
Submitter: Jenkins
Branch: master

commit 4e4c8759a25fa18384b45f4150000aacfaed035a
Author: Csaba Henk <email address hidden>
Date: Tue Sep 29 09:49:19 2015 +0200

    glusterfs vol layout: start volume cloned from snapshot

    When handling create_share_from_snapshot with glusterfs
    volume layout, we do a snapshot clone gluster operation
    that gives us a new volume (which will be used to back
    the new share). 'snapshot clone' does not start the
    resultant volume, we have explicitly start it from Manila.
    So far the volume layout code did not bother about it,
    rather the 'vol start' was called from glusterfs-native
    driver. That however broke all other volume layout based
    configs (ie. glusterfs driver with vol layout).

    Fix this now by doing the 'vol start' call in the vol
    layout code.

    Change-Id: I63c13ce468a3227f09e381814f55e8c914fbef95
    Closes-Bug: #1499347