+++ This bug was initially created as a clone of Bug #1643476 +++ Description of problem: According to the'Table 5.4. Bandwidth Explained' documentation [1]: ~~~ Defined by user (in Mbps). This value is divided by the number of concurrent migrations (default is 2, to account for ingoing and outgoing migration). Therefore, the user-defined bandwidth must be large enough to accommodate all concurrent migrations. For example, if the Custom bandwidth is defined as 600 Mbps, a virtual machine migration’s maximum bandwidth is actually 300 Mbps. ~~~ According to the 'lib/vdsm/api/vdsm-api.yml': ~~~ 3312 ┆ ┆ ┆ - defaultvalue: needs updating 3313 ┆ ┆ ┆ ┆ ┆ description: maximal bandwidth used by the migration (MiB/s) 3314 name: maxBandwidth 3315 ┆ ┆ ┆ ┆ ┆ type: int 3316 ┆ ┆ ┆ ┆ ┆ added: '4.0' 3317 ~~~ The engine is sending the migration bandwidth limit as Mbps but the vdsm interprets it as MiB/s. [1] https://access.redhat.com/documentation/en-us/red_hat_virtualization/4.2/html/administration_guide/sect-cluster_tasks#Cluster_Migration_Policy_Settings_Explained Version-Release number of selected component (if applicable): 4.2.6.4 How reproducible: Always Steps to Reproduce: 1. Configure the cluster's migration policy and set the migration bandwidth limit to 10 Mbps Actual results: The actual bandwidth consumed is 40Mbps Expected results: According to the documentation, and with a max concurrent migrations equals to 2, the actual bandwidth consumed should be 5Mbps.
WARN: Bug status wasn't changed from MODIFIED to ON_QA due to the following reason: [Found non-acked flags: '{'rhevm-4.3-ga': '?'}', ] For more info please contact: rhv-devops: Bug status wasn't changed from MODIFIED to ON_QA due to the following reason: [Found non-acked flags: '{'rhevm-4.3-ga': '?'}', ] For more info please contact: rhv-devops
Reassigned: ovirt-engine-4.3.0-0.4.master.20181230173049.gitef04cb4.el7.noarch qemu-kvm-ev-2.12.0-18.el7_6.1.1.x86_64 vdsm-4.30.4-81.gitad6147e.el7.x86_64 libvirt-client-4.5.0-10.el7_6.3.x86_64 When setting migration bandwidth limit to 10Mbps, the actual value in source host virsh domjobinfo is: Memory bandwidth: 52.016 MiB/s Observing REST API /ovirt-engine/api/clusters/ shows that the 10Mbps value was set successfully: <bandwidth> <assignment_method>custom</assignment_method> <custom_value>10</custom_value> </bandwidth> Also, need UI fix, the value in Webadmin edit cluster dialog, migration policy => migration bandwidth limit is in Mbps instead of MiB/s
Re-targeting to 4.3.1 since it is missing a patch, an acked blocker flag, or both
Based on the discussion in in bug 1643476, moving back to MODIFIED.
Verified on: ovirt-engine-4.3.0-0.4.master.20181230173049.gitef04cb4.el7.noarch qemu-kvm-ev-2.12.0-18.el7_6.1.1.x86_64 vdsm-4.30.4-81.gitad6147e.el7.x86_64 libvirt-client-4.5.0-10.el7_6.3.x86_64
QE verification bot: the bug was verified upstream
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHEA-2019:1085
sync2jira