Cinder

Incorrect capacity exists when extending volume

Bug #1706888 reported by TommyLike
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Cinder
Fix Released
Undecided
TommyLike

Bug Description

Cinder does not update the backend status (allocated_capacity_gb/provisioned_capacity_gb/free_capacity_gb) in time when extending volume. So the next capacity consuming operation might pass the scheduler but fail in the backend.

TommyLike (hu-husheng)
Changed in cinder:
assignee: nobody → TommyLike (hu-husheng)
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/487783

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/487783
Committed: https://git.openstack.org/cgit/openstack/cinder/commit/?id=a8776a726ea6320e2985b6c12f580ea8b17d21d2
Submitter: Jenkins
Branch: master

commit a8776a726ea6320e2985b6c12f580ea8b17d21d2
Author: TommyLike <email address hidden>
Date: Thu Jul 27 17:09:20 2017 +0800

    Update backend state when extending volume

    Rather than update the backend state in the next
    period task, update it directly in scheduler when
    extending.

    Change-Id: Idc59abcd574a7eef354d6590f7b748c6b54df8b4
    Closes-Bug: #1706888

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

This issue was fixed in the openstack/cinder 11.0.0.0b3 development milestone.

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

Other bug subscribers

Remote bug watches

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