Volumes created from snapshots on Windows are unaccessible

[Lucian Petrut]

When creating a volume from a snapshot on Windows, a shadow copy volume is exported as an iSCSI disk. The issue is that this export is readonly and cannot be mounted to instances. As this export cannot be modified, to make the new volume usable, the solution would be to copy the image to a new path and import it as the desired volume.

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: master
Review: https://review.openstack.org/86642

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/86642
Committed: https://git.openstack.org/cgit/openstack/cinder/commit/?id=9026db874634a78b8cdd3abb45a75a37f6ededfe
Submitter: Jenkins
Branch: master

commit 9026db874634a78b8cdd3abb45a75a37f6ededfe
Author: Lucian Petrut <email address hidden>
Date: Thu Apr 10 04:16:07 2014 +0300

    Fixes cinder volume from snapshot on Windows

    When creating a volume from a snapshot on Windows, a shadow copy
    volume is exported as an iSCSI disk. The issue is that this export
    is readonly and cannot be mounted to instances.

    As this export cannot be modified, to make the new volume usable,
    the according image must be moved to a new path and imported .

    Closes-Bug: #1306032

    Change-Id: I3a936d30fdd7875059dc56c2681f453757c2605f