Description of problem: rhevh-7.2-20160912.2 involved the wrong qemu-kvm-rhev package. It should involve qemu-kvm-rhev-2.3.0-31.el7_2.21 which released on 2016-Aug-12. Version-Release number of selected component (if applicable): rhevh-7.2-20160912.2.el6ev.iso kernel-3.10.0-327.28.3.el7.x86_64 qemu-kvm-rhev-2.3.0-31.el7_2.16.x86_64 ovirt-node-3.6.1-15.0.el7ev.noarch How reproducible: 100% Steps to Reproduce: 1. Clean install rhevh-7.2-20160912.2 2. Check the qemu-kvm-rhev package Actual results: After step2, qemu-kvm-rhev package is not the latest package, should include newer package. # rpm -qa | grep qemu-kvm-rhev qemu-kvm-rhev-2.3.0-31.el7_2.16.x86_64 Expected results: After step3, It should include package qemu-kvm-rhev-2.3.0-31.el7_2.21 Additional info:
Test version: rhev-hypervisor7-7.2-20160913.0.iso kernel-3.10.0-327.28.3.el7.x86_64 qemu-kvm-rhev-2.3.0-31.el7_2.21.x86_64 ovirt-node-3.6.1-15.0.el7ev.noarch Test Steps: 1. Clean install rhev-hypervisor7-7.2-20160913.0.iso 2. Check the qemu-kvm-rhev package Test results: After step2, It include package qemu-kvm-rhev-2.3.0-31.el7_2.21 # rpm -qa | grep qemu-kvm-rhev qemu-kvm-rhev-2.3.0-31.el7_2.21.x86_64 So this bug is fixed in rhev-hypervisor7-7.2-20160913.0.iso, change the status to VERIFIED
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://rhn.redhat.com/errata/RHBA-2016-1936.html