| 2015-10-08 08:21:48 |
wanghao |
bug |
|
|
added bug |
| 2015-10-08 08:22:07 |
wanghao |
cinder: assignee |
|
wanghao (wanghao749) |
|
| 2015-10-08 09:18:53 |
wanghao |
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 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 this volume successfully, and check the quota usage again, it will be -1 again. |
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 this volume successfully, and check the quota usage again, it will be -1 again. |
|
| 2015-10-08 09:20:06 |
wanghao |
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 this volume successfully, and check the quota usage again, it will be -1 again. |
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. |
|
| 2015-10-08 09:26:59 |
OpenStack Infra |
cinder: status |
New |
In Progress |
|
| 2015-11-10 07:20:23 |
wanghao |
cinder: importance |
Undecided |
Medium |
|
| 2015-12-16 18:30:24 |
Sheel Rana |
bug |
|
|
added subscriber Sheel Rana |
| 2016-01-08 05:15:39 |
John Griffith |
tags |
|
liberty-backport-potential |
|
| 2016-03-07 02:29:26 |
wanghao |
cinder: milestone |
|
mitaka-rc1 |
|
| 2016-03-17 14:35:10 |
Sean McGinnis |
cinder: milestone |
mitaka-rc1 |
newton-1 |
|
| 2016-06-05 22:51:55 |
Sean McGinnis |
cinder: milestone |
newton-1 |
newton-2 |
|
| 2016-09-16 12:57:13 |
Sean McGinnis |
cinder: milestone |
newton-2 |
ocata-1 |
|
| 2016-09-18 15:57:55 |
OpenStack Infra |
cinder: status |
In Progress |
Fix Released |
|
