Bug 1517492
| Summary: | Create VM with new created quota fails. | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [oVirt] ovirt-engine | Reporter: | Polina <pagranat> | ||||
| Component: | Backend.Core | Assignee: | Andrej Krejcir <akrejcir> | ||||
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Polina <pagranat> | ||||
| Severity: | medium | Docs Contact: | |||||
| Priority: | high | ||||||
| Version: | 4.2.0 | CC: | akrejcir, bugs, michal.skrivanek, pagranat | ||||
| Target Milestone: | ovirt-4.2.1 | Keywords: | Regression | ||||
| Target Release: | --- | Flags: | rule-engine:
ovirt-4.2+
rule-engine: blocker+ |
||||
| Hardware: | x86_64 | ||||||
| OS: | Linux | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||
| Doc Text: |
Cause:
Using the REST API it was possible to create an empty quota with no storage or cluster limits.
Consequence:
This quota could not be assigned to a VM and was not visible form the UI.
Fix:
When a new quota is created using the API, the storage and cluster limit objects are also created and set to unlimited.
Result:
The newly created quota can be used and is visible in the UI.
|
Story Points: | --- | ||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2018-02-12 11:56:07 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: |
|
||||||
|
Description
Polina
2017-11-26 07:16:11 UTC
Expected results: it is regression from 4.1. So, expected - the VM is created successfully. 1. Please rephrase the title. 2. Please provide all relevant logs. 3. As the error says - please check the quota is valid. 1. Created attachment 1359148 [details]
engine.log attached
1. The title is rephrased. 2. engine.log added 3. quota is valid. Created with status 201. and I also checked that the same quota is created in 4.1. At least according to engine.log, the name of the quota is 'quota_1' and not 'q1': 2017-11-26 14:44:09,168+02 INFO [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (default task-27) [d676b66d-33de-41d0-a4bc-a0b88de77277] EVENT_ID: USER_ADD_QUOTA(3,000), Quota quota_1 has been added by admin@internal-authz. yes, you are right. to attach the logs I reproduced the scenario anew and put the new quota name = 'quota_1'. So, In POST request the same name must be used accordingly : POST https://compute-ge-3.scl.lab.tlv.redhat.com/ovirt- engine/api/datacenters/bb4bff86-9243-4fc2-b57e-fdc29a93b176/quotas <quota> <name>quota_1</name> </quota> nothing obvious in the logs, just returning ACTION_TYPE_FAILED_QUOTA_NOT_EXIST. moving to SLA area This bug report has Keywords: Regression or TestBlocker. Since no regressions or test blockers are allowed between releases, it is also being identified as a blocker for this release. Please resolve ASAP. verified by running regression test rhevmtests/compute/sla/quota/quota_test.py for rhv-release-4.2.1-1-001.noarch This bugzilla is included in oVirt 4.2.1 release, published on Feb 12th 2018. Since the problem described in this bug report should be resolved in oVirt 4.2.1 release, it has been closed with a resolution of CURRENT RELEASE. If the solution does not work for you, please open a new bug report. |