Bug 1720487 - [REST] Unable to set 'Unlimited' QOS for vNIC profile using RESTAPI
Summary: [REST] Unable to set 'Unlimited' QOS for vNIC profile using RESTAPI
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: ovirt-engine
Classification: oVirt
Component: RestAPI
Version: 4.3.3.1
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ovirt-4.3.6
: 4.3.6.1
Assignee: Dominik Holler
QA Contact: msheena
URL:
Whiteboard:
Depends On:
Blocks: 1597537
TreeView+ depends on / blocked
 
Reported: 2019-06-14 06:55 UTC by Martin Necas
Modified: 2019-09-26 19:43 UTC (History)
5 users (show)

Fixed In Version: ovirt-engine-4.3.6.1
Clone Of:
Environment:
Last Closed: 2019-09-26 19:43:24 UTC
oVirt Team: Network
Embargoed:
pm-rhel: ovirt-4.3+


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
oVirt gerrit 102237 0 master MERGED restapi: Allow removing QoS of VnicProfile 2020-11-02 13:56:41 UTC
oVirt gerrit 102238 0 master MERGED Allow updating qos and networkFilter of VnicProfile 2020-11-02 13:56:58 UTC
oVirt gerrit 102361 0 ovirt-engine-4.3 MERGED restapi: Allow removing QoS of VnicProfile 2020-11-02 13:56:41 UTC
oVirt gerrit 102362 0 model_4.3 MERGED Allow updating qos and networkFilter of VnicProfile 2020-11-02 13:56:41 UTC

Description Martin Necas 2019-06-14 06:55:57 UTC
Description of problem:
Cannot remove qos from vNIC profile using API.

Version-Release number of selected component (if applicable):
Version 4.3.3.1-1.el7

How reproducible:
always

Steps to Reproduce:
1. Have vNIC profile with qos
2. Send PUT request with: <vnic_profile><qos></qos></vnic_profile>


Actual results:
Qos is not removed from vNIC.

Expected results:
To remove qos. 
Network_filter has this functionality(<vnic_profile><network_filter></network_filter></vnic_profile>).

Additional info:

Comment 1 Martin Perina 2019-07-18 08:34:48 UTC
Setting severity to high, it's blocking BZ1597537.

Dominik, could you please prioritize?

Comment 2 Michael Burman 2019-07-23 10:55:58 UTC
Why this is a bug at all??

You can't remove QoS, you need to to set 'Unlimited', no option to remove QoS, there is no such thing. 
In network filter, you can set 'No network filter' , this is why you can remove it. Because you can have a vNIC profile with any network filter, but you can't have a vNIC profile without QoS.

Comment 3 Ondra Machacek 2019-07-23 12:40:36 UTC
'Unlimited' in UI is represented as no value in API. The bug is about we can't set the "Unlimited" value in API. It should be possible to "Unlimited" value by setting the <qos/> as described in the description of the bug.

Comment 5 Dominik Holler 2019-07-29 09:48:20 UTC
mnecas, can you please share an example of how the update works for network_filter in the way you like to have the update for qos?
If there is no network_filter example, would you please provide an example request you would prefer to use?

Comment 6 Martin Perina 2019-07-29 12:03:27 UTC
(In reply to Dominik Holler from comment #5)
> mnecas, can you please share an example of how the update works for
> network_filter in the way you like to have the update for qos?
> If there is no network_filter example, would you please provide an example
> request you would prefer to use?

As Ondra mentioned in Comment 3: if you post a PUT request with empty qos element (<qos/>), the QOS for VNIC profile should be set to Unlimited. If qos element has a name (<qos>NAME</qos>), then the QOS should be set to specified QOS.

Comment 7 Dominik Holler 2019-07-29 21:23:26 UTC
(In reply to Martin Perina from comment #6)
> (In reply to Dominik Holler from comment #5)
> > mnecas, can you please share an example of how the update works for
> > network_filter in the way you like to have the update for qos?
> > If there is no network_filter example, would you please provide an example
> > request you would prefer to use?
> 
> As Ondra mentioned in Comment 3: if you post a PUT request with empty qos
> element (<qos/>), the QOS for VNIC profile should be set to Unlimited. If
> qos element has a name (<qos>NAME</qos>), then the QOS should be set to
> specified QOS.

Thanks, I was confused by another problem (fix proposed in https://gerrit.ovirt.org/#/c/102236/ )

Comment 8 msheena 2019-08-12 10:07:38 UTC
Verified using
==============
ovirt-engine-4.3.6.1-0.1.el7.noarch

Comment 9 Sandro Bonazzola 2019-09-26 19:43:24 UTC
This bugzilla is included in oVirt 4.3.6 release, published on September 26th 2019.

Since the problem described in this bug report should be
resolved in oVirt 4.3.6 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.


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