unmanage volume/snapshot reduce quota incorrectly
Bug #1504007 reported by
wanghao
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Cinder |
Fix Released
|
Medium
|
wanghao |
Bug Description
When managing volume/snapshot get error, the quota usage will roll back and set the new volume/snapshot status to error, but then delete/unmanage this resource, quota usage will be reduced again, it's incorrect.
Test steps:
1.Check the quota usage of current tenant.
2.Manage a volume which is not exist, and the new volume will be error.
3.Check the quota usage of current tenant, it will be not changed.
4.Delete/Unmanage this volume successfully, and check the quota usage again, it will be -1 again.
Changed in cinder: | |
assignee: | nobody → wanghao (wanghao749) |
description: | updated |
description: | updated |
Changed in cinder: | |
importance: | Undecided → Medium |
tags: | added: liberty-backport-potential |
Changed in cinder: | |
milestone: | none → mitaka-rc1 |
Changed in cinder: | |
milestone: | mitaka-rc1 → newton-1 |
Changed in cinder: | |
milestone: | newton-1 → newton-2 |
Changed in cinder: | |
milestone: | newton-2 → ocata-1 |
To post a comment you must log in.
Fix proposed to branch: master /review. openstack. org/232436
Review: https:/