Description of problem: Create new quota with name , get 201. then try to create VM with this quota - bad request 400. it is regression from 4.1. Version-Release number of selected component (if applicable): rhvm-4.2.0-0.5.master.el7.noarch How reproducible:100% Steps to Reproduce: 1. Create minimal quota, like Content-Type: application/xml POST https://compute-ge-3.scl.lab.tlv.redhat.com/ovirt- engine/api/datacenters/bb4bff86-9243-4fc2-b57e-fdc29a93b176/quotas <quota> <name>q1</name> </quota> 2. Create new vm with this quota Actual results: in webUI the quota even not in the quota list (Edit VM/Genera/quota). Trying to send by Rest API returns error 400 <fault> <detail>[Cannot add VM. Quota is not valid.]</detail> <reason>Operation Failed</reason> </fault> Expected results: it is regression from 4.1 Additional info:
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.