Bug 1312896 - Update vm quota with name instead of Id does not work
Summary: Update vm quota with name instead of Id does not work
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: ovirt-engine
Classification: oVirt
Component: RestAPI
Version: 3.6.3.3
Hardware: x86_64
OS: Linux
unspecified
low
Target Milestone: ovirt-4.0.0-alpha
: ---
Assignee: Doron Fediuck
QA Contact: Pavel Stehlik
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-02-29 13:26 UTC by Artyom
Modified: 2016-04-06 11:37 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-04-06 11:37:30 UTC
oVirt Team: SLA
dfediuck: ovirt-4.0.0?
rule-engine: planning_ack?
rule-engine: devel_ack?
rule-engine: testing_ack?


Attachments (Terms of Use)

Description Artyom 2016-02-29 13:26:44 UTC
Description of problem:
When I update vm quota with:
<vm>
  <quota><name>quota_name</name></quota>
</vm>
Request succeed and show me 200, but vm stay with old quota.

Version-Release number of selected component (if applicable):
rhevm-restapi-3.6.3.2-0.1.el6.noarch

How reproducible:
Always

Steps to Reproduce:
1. Change datacenter quota mode to audit
2. Choose quota test for vm
3. Try to change vm quota to test_1 via REST
<vm>
  <quota><name>test_1</name></quota>
</vm>

Actual results:
REST return status 200, but vm stay with old quota test

Expected results:
REST return status 200 and vm has quota test_1

Additional info:
same for vm disk

Comment 1 Juan Hernández 2016-02-29 14:40:32 UTC
I'm lowering the severity because this isn't a bug, but an enhancement. The quota name is just completely ignored, only the id is taken into account for this kind of updates.

Comment 2 Red Hat Bugzilla Rules Engine 2016-03-20 10:04:12 UTC
Target release should be placed once a package build is known to fix a issue. Since this bug is not modified, the target version has been reset. Please use target milestone to plan a fix for a oVirt release.

Comment 3 Doron Fediuck 2016-04-06 11:37:30 UTC
Closing old issues based on capacity.
Please re-open only if relevant and needed.


Note You need to log in before you can comment on or make changes to this bug.