3par drivers don't report stats when limitMiB is set on a CPG

Bug #1178418 reported by Walt Boring on 2013-05-09
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Walt Boring

Bug Description

When a CPG is created on the 3PAR and the limitMiB is set (maximum size allowed for the CPG), the 3PAR driver's don't report the volume stats, due to a bug in refactored code.

Changed in cinder:
assignee: nobody → Walt Boring (walter-boring)

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

Changed in cinder:
status: New → In Progress

Reviewed: https://review.openstack.org/28722
Committed: http://github.com/openstack/cinder/commit/20c2be3e7912e9c58392e11934c8114b63e73670
Submitter: Jenkins
Branch: master

commit 20c2be3e7912e9c58392e11934c8114b63e73670
Author: Walter A. Boring IV <email address hidden>
Date: Thu May 9 14:15:13 2013 -0700

    Fixes an get_volume_stats reporting issue

    This patch fixes a bug introduced in the last get_volume_stats
    patch that caused the method to fail. I Also added another set
    of unit tests to catch any future issues related to get_volume_stats.

    Fixes Bug: #1178418

    Change-Id: I0dd2e0113ff822d3e717ab3d6da6b9d1b914a995

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

Other bug subscribers