Extending volume is in GB yet 3PAR is expecting MB

[Michael Denny]

Extending volume diff is in GB yet 3PAR is expecting MB

Extending Volume osv-iGH8frZFSDuht.TTE90Erw from 3 to 7, by 4 GB. from (pid=60905) extend_volume /opt/stack/cinder/cinder/volume/drivers/san/hp/hp_3par_common.py:246

Cinder is correct
cinder extend 7f688411-9618-460e-a0f6-eb5dc333bc1a 7

Results in incorrect virtual volume size for thin provisioned and extended volume

[OpenStack Infra (hudson-openstack)]

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

[OpenStack Infra (hudson-openstack)]

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

commit e088c73b185073943d9b18b7ede0375c096ee8b3
Author: Kurt Martin <email address hidden>
Date: Tue Feb 25 08:30:01 2014 -0800

    3PAR: Fix extend volume GiB to MiB

    Extend volume was sending GiB instead of MiB to the 3PAR
    array. This patch is now sending the growth size in MiBs
    instead of GiBs.

    Change-Id: Ib4903315a32e090e760883cc80c50f3698fe015f
    Closes-Bug: #1284368