Created attachment 1313043 [details] logs Description of problem: While adding network QOS to NIC of the VM and running the VM, the values aren't configured on libvirt Version-Release number of selected component (if applicable): ovirt-engine-4.2.0-0.0.master.20170808202742.git7c42951.el7.centos.noarch How reproducible: 100 Steps to Reproduce: 1. Create new Network QoS profile under DC with default parameters. 2. Create VNIC profile with configured QoS and add it to the NIC of the VM. 3. Run VM 4. Check that provided bw values are the same as the values configured on libvirt Actual results: The values aren't configured on libvirt Expected results: The values should be configured on libvirt Additional info: get xml from the vm: virsh -r dumpxml <vm_name> <interface type='bridge'> <mac address='00:1a:4a:16:20:74'/> <source bridge='ovirtmgmt'/> <target dev='vnet0'/> <model type='virtio'/> <filterref filter='vdsm-no-mac-spoofing'/> <alias name='net0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x04' function='0x0'/> </interface>
I suspect that this is a regression due to the Engine domxml work.
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 on ovirt-engine-4.2.0-0.0.master.20170820180837.git59243e9.el7.centos.noarch
This bugzilla is included in oVirt 4.2.0 release, published on Dec 20th 2017. Since the problem described in this bug report should be resolved in oVirt 4.2.0 release, published on Dec 20th 2017, it has been closed with a resolution of CURRENT RELEASE. If the solution does not work for you, please open a new bug report.