RemoteFS: image volume cache unusable

Bug #1685277 reported by Lucian Petrut
14
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Cinder
Fix Released
Undecided
Lucian Petrut

Bug Description

At the moment, the RemoteFS based drivers cannot leverage the generic image volume cache feature.

The reason is that this involves cloning a newly created volume while still being in 'downloading' state, which is an unacceptable state from the driver's point of view.

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

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

Changed in cinder:
assignee: nobody → Lucian Petrut (petrutlucian94)
status: New → In Progress
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to cinder (master)

Reviewed: https://review.openstack.org/458885
Committed: https://git.openstack.org/cgit/openstack/cinder/commit/?id=63b9f0fb8e831c29fab00670c19056e436d5f5f0
Submitter: Jenkins
Branch: master

commit 63b9f0fb8e831c29fab00670c19056e436d5f5f0
Author: Lucian Petrut <email address hidden>
Date: Fri Apr 21 17:29:43 2017 +0300

    RemoteFS: enable image volume cache

    At the moment, the RemoteFS based drivers cannot leverage the generic
    image volume cache feature.

    The reason is that this involves cloning a newly created volume while
    still being in 'downloading' state, which is an unacceptable state
    from the driver's point of view.

    This change adds 'downloading' as an acceptable state for the volume
    clone operation as well as for creating/deleting snapshots used
    internally by the volume clone operation.

    Note that 'regular' volume clones will be rejected before reaching
    the driver when having a source volume in 'downloading' state.

    Change-Id: I84bb3f062637031f7f46b414d6cbbff0bb0292ea
    Closes-Bug: #1685277

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

This issue was fixed in the openstack/cinder 11.0.0.0b3 development milestone.

Revision history for this message
Silvan Kaiser (2-silvan) wrote :

I created a stable/ocata diff patch for this from the master fix, do we want to add this as a back port? I could easily set up a gerrit patch for that branch.

Revision history for this message
Lucian Petrut (petrutlucian94) wrote :

A backport would be helpful.

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to cinder (stable/ocata)

Fix proposed to branch: stable/ocata
Review: https://review.openstack.org/489591

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Change abandoned on cinder (stable/ocata)

Change abandoned by Silvan Kaiser (<email address hidden>) on branch: stable/ocata
Review: https://review.openstack.org/489591

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

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.