Require vmfex-dev hook installation for VDSM 3.6.
Why this hook should be required? This hook is built with vdsm, and can be installed if needed. If the functionality of this hook is always required, we should integrate this hook in the networking code instead.
Sorry, I have to redirect this question.
vdsm-hook-vmfex-dev allows connecting oVirt VMs to UCS-defined port profiles, as explained in http://www.ovirt.org/Features/UCS_Integration#Level_IV:_.22A_New_Hook.22 This functionality (connecting to VM-FEX) is repeatedly requested by customers. Since this hook is well tested and mature, shipping it with Vdsm is safe and useful.
Verified on - vdsm-4.17.14-0.el7ev.noarch vdsm-hook-vmfex-dev-4.17.14-0.el7ev.noarch
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-0362.html
It seems to be a duplicated of this bug: https://bugzilla.redhat.com/show_bug.cgi?id=805884