The real fix for this problem is in libvirt, via bug 1461303. There are no code changes required from vdsm's side, so simply dnf updating libvirt to get libvirt-3.2.0-12.el7 once it's released will solve the problem.

RHV 4.1.4 will be released *before* this libvirt, so we can't require it there. On the other hand, the original bug occured on an unreleased libvirt build which no customer should ever encounter, so requiring it is a useful safety measure, but not a hard requirement.

Reducing priotiy/severity accordingly.

bug 1467826 is also a critical libvirt bug which should be delivered as a 0day errata by libvirt.

We should wait till that is released and require the right libvirt version that contains fixes for both bugs - bug 1461303 and bug 1467826.

There's nothing blocking here - customers who just yum update their environments will get these fixes. Having vdsm require them is an additional safety measure, but definitely not a must.

I prefer waiting for CentOS 7.4 instead of uglifying the spec file - pushing out.

The underlying issue is fixed by libvirt - this is just to track a failsagfe of requiring it.
Removing alarming keywords and the blocker flag.

According to comment #4 - verifying