CoraidDriver: create_volume_from_snapshot of a different size

Bug #1158959 reported by Jean-Baptiste RANSY on 2013-03-22
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Cinder
Medium
Jean-Baptiste RANSY

Bug Description

When you create a Volume from a Snapshot, the 'size' argument for the new volume isn't used at all
So, the new volume created will be created (successfully but) with the same size as the snapshot size.

Cinder think the volume has been created with the right size.

We just need to call Coraid ESM LV Resize with the REST API after the volume has been created.

Changed in cinder:
status: New → In Progress
assignee: nobody → Jean-Baptiste RANSY (jean-baptiste-ransy)
tags: added: grizzly-rc-potential
Thierry Carrez (ttx) on 2013-03-27
Changed in cinder:
importance: Undecided → Medium
Thierry Carrez (ttx) on 2013-04-02
tags: added: grizzly-backport-potential
removed: grizzly-rc-potential

Reviewed: https://review.openstack.org/25281
Committed: http://github.com/openstack/cinder/commit/1410af4214379da13b10baec3ddb37cbce7e5eb6
Submitter: Jenkins
Branch: master

commit 1410af4214379da13b10baec3ddb37cbce7e5eb6
Author: Jean-Baptiste Ransy <email address hidden>
Date: Thu Jun 20 17:39:45 2013 +0200

    CoraidDriver: Create_volume_from_snapshot of a different size

    When you create a Volume from a Snapshot, the 'size' argument for the
    new volume isn't used at all.
    So, the new volume created will be created (successfully but) with the
    same size as the snapshot size.

    Cinder think the volume has been created with the right size.

    We just need to call Coraid ESM LV Resize with the REST API after
    the volume has been created.

    Fixes bug 1158959

    Change-Id: I760fe1ba4052bb2d5b1a1a5c55c9a976522af107

Changed in cinder:
status: In Progress → Fix Committed
Thierry Carrez (ttx) on 2013-07-17
Changed in cinder:
milestone: none → havana-2
status: Fix Committed → Fix Released
Thierry Carrez (ttx) on 2013-10-17
Changed in cinder:
milestone: havana-2 → 2013.2
Alan Pevec (apevec) on 2014-03-31
tags: removed: grizzly-backport-potential
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers