It is possible to clone a volume with a size greater than
the source volume. When using the SolidFire driver, the volume size
was not passed in the call made to the SolidFire API when
cloning a volume.
It resulted in a cloned volume having the same size as the source
volume but the correct size in the Cinder database.
This changes makes sure the cloned volume has the correct size
by explicitly passing the requested size when calling
the SolidFire API and cloning the volume.
Fixes: bug #1219105
Change-Id: I5628c7fa922780d6b0601e2daa79310a61085edc
(cherry picked from commit 0a87ff988cd21586daeb6ed886e44aedaa49c320)
Reviewed: https:/ /review. openstack. org/45143 github. com/openstack/ cinder/ commit/ 19e92af7eff54fd 75e2a91b772812d a46c60b3cc
Committed: http://
Submitter: Jenkins
Branch: stable/grizzly
commit 19e92af7eff54fd 75e2a91b772812d a46c60b3cc
Author: Mathieu Gagné <email address hidden>
Date: Fri Aug 30 21:59:59 2013 -0400
Clone volume with right size with SolidFire
It is possible to clone a volume with a size greater than
the source volume. When using the SolidFire driver, the volume size
was not passed in the call made to the SolidFire API when
cloning a volume.
It resulted in a cloned volume having the same size as the source
volume but the correct size in the Cinder database.
This changes makes sure the cloned volume has the correct size
by explicitly passing the requested size when calling
the SolidFire API and cloning the volume.
Fixes: bug #1219105 d6b0601e2daa793 10a61085edc 6daeb6ed886e44a edaa49c320)
Change-Id: I5628c7fa922780
(cherry picked from commit 0a87ff988cd2158