Resolving this is needed to support Fedora 23. Fedora 22 is using older libvirt version without this regression.
But it may effect also Fedora 22 when using virt-preview repository.
*** Bug 1255246 has been marked as a duplicate of this bug. ***
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.
Target release should be placed once a package build is known to fix a issue. Since this bug is not modified, the target version has been reset. Please use target milestone to plan a fix for a oVirt release.
In oVirt testing is done on single release by default. Therefore I'm removing the 4.0 flag. If you think this bug must be tested in 4.0 as well, please re-add the flag. Please note we might not have testing resources to handle the 4.0 clone.
Nir, I don't think this bug should be on POST as the patch only fixes the problem on RHEL, can you please confirm?
(In reply to Tal Nisan from comment #7) > Nir, I don't think this bug should be on POST as the patch only fixes the > problem on RHEL, can you please confirm? Yes, we need to require the Fedora 23 package fixing this. When I opened this bug, it was not available.
Removing the blocker flag. Even without this fix a used can always manually dnf update to get the libvirt package that solves the issue.
We are not verifying Fedora, On RHEL7.2 it looks ok Verified (vdsm-4.17.17-0.el7ev.noarch) [root@camel-vdsc ~]# rpm -q --requires vdsm |grep libvirt libvirt-client libvirt-daemon >= 1.2.17-9 libvirt-daemon-config-nwfilter libvirt-daemon-driver-network libvirt-daemon-driver-nwfilter libvirt-daemon-driver-qemu libvirt-lock-sanlock libvirt-python >= 1.2.17-2