Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1580285

Summary: QoS burst - wrong units displayed in engine webadmin and engine-config and wrong values passed to libvirt
Product: [oVirt] ovirt-engine Reporter: eraviv
Component: BLL.NetworkAssignee: eraviv
Status: CLOSED CURRENTRELEASE QA Contact: Michael Burman <mburman>
Severity: medium Docs Contact:
Priority: low    
Version: 4.2.2CC: bugs, danken, eedri, mburman
Target Milestone: ovirt-4.2.5Flags: rule-engine: ovirt-4.2+
mburman: testing_plan_complete+
mburman: testing_ack+
Target Release: ---   
Hardware: All   
OS: All   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-07-31 15:25:22 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: Network RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
webadmin network QoS form none

Description eraviv 2018-05-21 07:27:41 UTC 
Created attachment 1439423 [details]
webadmin network QoS form

Description of problem:
QoS burst units of measure are displayed incorrectly and inconsistently in the webadmin form and in the engine-config output

Version-Release number of selected component (if applicable):
4.2

How reproducible:
100%

Steps to Reproduce:
1. run engine-cofing -l | grep QoS --> max burst units are Mb, inbound\outbound burst units are Mbps
2. webadmin > compute > datacenter > network QoS > MB/s

Actual results:
wrong and inconsistent units are reported\displayed

Expected results:
displayed units for all burst values should be MiB as is reported by the REST API documentation.

Additional info:
Burst units are not mentioned in https://access.redhat.com/documentation/en-us/red_hat_virtualization/4.2/html-single/administration_guide/
Comment 2 Michael Burman 2018-07-03 12:21:37 UTC 
Verified on - 4.2.5-0.1.el7ev
Comment 3 Sandro Bonazzola 2018-07-31 15:25:22 UTC 
This bugzilla is included in oVirt 4.2.5 release, published on July 30th 2018.

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