VMware: size not extended for volume created from in-use source volume

Bug #1763529 reported by Vipin Balachandran
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Cinder
Fix Released
Medium
Vipin Balachandran

Bug Description

Volume created from a in-use source volume will have the same size as the source volume.

Tags: drivers vmware
Changed in cinder:
importance: Undecided → Medium
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/561068

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

Reviewed: https://review.openstack.org/561068
Committed: https://git.openstack.org/cgit/openstack/cinder/commit/?id=cce7307ec1281745c718ddbed2d15ba1b07acde5
Submitter: Zuul
Branch: master

commit cce7307ec1281745c718ddbed2d15ba1b07acde5
Author: Vipin Balachandran <email address hidden>
Date: Thu Apr 12 15:44:22 2018 -0700

    VMware: Extend volume after clone

    Volumes created from in-use source volumes will have the
    same size as the source volume. Fixing this by calling
    extend if the cloned volume's size is smaller than the
    requested volume size.

    Change-Id: Ia1da23fc17092ce6656ed85c91bdab72d2e7cc70
    Closes-bug: 1763529

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

This issue was fixed in the openstack/cinder 13.0.0.0b2 development milestone.

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

Other bug subscribers

Remote bug watches

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