Bug 848289
| Summary: | ovirt-engine-backend [Quota]: we can diminish the quota set after reaching the limit with no warning and circumvent the quota for storage | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | Red Hat Enterprise Virtualization Manager | Reporter: | Dafna Ron <dron> | ||||||
| Component: | ovirt-engine | Assignee: | ofri <omasad> | ||||||
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Dafna Ron <dron> | ||||||
| Severity: | high | Docs Contact: | |||||||
| Priority: | unspecified | ||||||||
| Version: | unspecified | CC: | acathrow, dfediuck, dyasny, hateya, iheim, lpeer, omasad, Rhev-m-bugs, yeylon, ykaul | ||||||
| Target Milestone: | --- | ||||||||
| Target Release: | --- | ||||||||
| Hardware: | Unspecified | ||||||||
| OS: | Unspecified | ||||||||
| Whiteboard: | sla | ||||||||
| Fixed In Version: | si18 | Doc Type: | Bug Fix | ||||||
| Doc Text: | Story Points: | --- | |||||||
| Clone Of: | Environment: | ||||||||
| Last Closed: | 2012-12-04 20:05:31 UTC | Type: | Bug | ||||||
| Regression: | --- | Mount Type: | --- | ||||||
| Documentation: | --- | CRM: | |||||||
| Verified Versions: | Category: | --- | |||||||
| oVirt Team: | SLA | RHEL 7.3 requirements from Atomic Host: | |||||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||||
| Embargoed: | |||||||||
| Attachments: |
|
||||||||
Indeed a warning should be provided, as in enforcing mode this quota will not allow any changes / additions. Posted to upstream: http://gerrit.ovirt.org/#/c/7824/ merged downstream: https://gerrit.eng.lab.tlv.redhat.com/gitweb?p=ovirt-engine.git;a=commit;h=98f567c97e2ed76d27faf63cd83518e0699ca243 and https://gerrit.eng.lab.tlv.redhat.com/gitweb?p=ovirt-engine.git;a=commit;h=8daf3f96b889afd358a919ce79dff87c7bf91fac The solution includes double notification. When a quota is changed, if the new size is under the current utilization, an alert icon is shown next to the quota utilization column (in the edit quota popup). this icon will apear next to any exceeded quota. after approving the change (clicking ok) - a worning message will appear in the log (telling that the new size is less then the current utilization). tested on si18 *the exclamation mark appears when we exceed the quota (with the grace period). - it also appears when we exceed the quota with the grace period. - you also have to edit the quota to know that it was exceeded - I think that it would be good to show the same exclamation mark near the quota name in the main quota tab. * there was no warning at all when I pressed OK. moving back to dev. Created attachment 615313 [details]
logs
Thanks Dafna. I think comment 5 is correct, but current state is a solution for the original issue. Please see comment 4. If needed we can start a new RFE for additional improvements you suggested such as a better indication on the main quota tab. Doron said that the only fix at this time is the exclamation mark so moving to to verified on si18 |
Created attachment 604526 [details] log Description of problem: I created a 30GB quota and a vm with 30GB disk. than I edited the quota to 20GB. there was no warning at all although I can see that the quota is reporting that 30 out of 20GB quota is used. this is not major and I do not think should be blocked but I think a warning should be issued. Version-Release number of selected component (if applicable): si13.3 How reproducible: 100% Steps to Reproduce: 1. create a 30GB quota and a vm with 30GB disk 2. edit the quota to 20GB 3. Actual results: we can edit the quota and as a result exceed from it. On Doron's suggestion I tried moving the disk and failed. Expected results: we should issue a warning to the user that quota was changed and as a result we are exceeding its limit. Additional info: log