Quota context does not restore original settings on exit
Bug #1595578 reported by
Illia Khudoshyn
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Rally |
Fix Released
|
High
|
Andriy Kurilin |
Bug Description
Quota context on exit just deletes all existing settings on exit.
https:/
If Rally runs against env with existing tenants/users
this causes pre-existing quotas to be reset to theirs defaults.
description: | updated |
Changed in rally: | |
status: | New → Triaged |
importance: | Undecided → High |
Changed in rally: | |
assignee: | nobody → Andrey Kurilin (andreykurilin) |
Changed in rally: | |
status: | Triaged → In Progress |
To post a comment you must log in.
Reviewed: https:/ /review. openstack. org/347866 /git.openstack. org/cgit/ openstack/ rally/commit/ ?id=4bd3518ca21 f81116d633759eb 15df9ff6cc7404
Committed: https:/
Submitter: Jenkins
Branch: master
commit 4bd3518ca21f811 16d633759eb15df 9ff6cc7404
Author: Andrey Kurilin <email address hidden>
Date: Wed Jul 27 17:22:17 2016 +0300
[existing users] Restore original quotas
Behaviors of quotas cleanup should be different in case of existing users and
new ones(created by users context).
In case of existing users, we should not delete quotas, since we should not
change user pre-defined data.
In case of new users, we can't do the same as with existing users. Restore
default quotas means that services databases will continue storing quotas even
after tenant removement. So we need to remove quotas in this case.
Closes-Bug: #1595578
Change-Id: I6d42942f7fcdc6 7f221dc73749566 3eec065c8e4