Efficient image cloning feature does not recognize volume-type and incompatible with SSC.

Bug #1226752 reported by Jeff Applewhite on 2013-09-17
This bug affects 1 person
Affects Status Importance Assigned to Milestone

Bug Description

When performing efficient image cloning, if volume-type is supplied with image-id in the create command, sometimes the cloning is done in the shares which do not match the volume-type criteria. While cloning it should be verified if the cache is in share which can host volume for specified volume-type, if not then usual copy-image-to-volume route should be followed.

Navneet (singn) on 2013-09-18
tags: added: netapp
Changed in cinder:
assignee: nobody → Navneet (singn)
Mike Perez (thingee) on 2013-09-18
tags: added: drivers
Changed in cinder:
status: New → In Progress

Reviewed: https://review.openstack.org/47365
Committed: http://github.com/openstack/cinder/commit/f47581de091cac8f32151d2faf72df2fe84fcf62
Submitter: Jenkins
Branch: master

commit f47581de091cac8f32151d2faf72df2fe84fcf62
Author: Navneet Singh <email address hidden>
Date: Thu Aug 1 06:47:48 2013 +0530

    NetApp fix clone image compatibility issue with ssc

    It makes clone image functionality compatible
    with the ssc feature. Hence it makes clone
    image sensitive to volume type and provision
    on the right share matching volume type
    extra specs.

    Change-Id: If980239fedf784a1cca7abd6ee3d00f8625b9b11

Changed in cinder:
status: In Progress → Fix Committed
Thierry Carrez (ttx) on 2013-10-04
Changed in cinder:
milestone: none → havana-rc1
status: Fix Committed → Fix Released
Thierry Carrez (ttx) on 2013-10-17
Changed in cinder:
milestone: havana-rc1 → 2013.2
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers