We're currently using ovirt-engine-wildfly-8.2.0 final in 3.6 and we're already going to test 10 CR1 on master. We don't want that a casual yum update / dnf update may break the running engine. So we need to lock the version of ovirt-engine-wildfly as well and allow the setup to take care of the update.
Isn't it enough to Conflict?
Verified with: ovirt-engine-3.6.1-0.0.master.20151019163841.gitacec65b.el6.noarch # cat /etc/yum/pluginconf.d/versionlock.list ovirt-engine-webadmin-portal-3.6.1-0.0.master.20151019163841.gitacec65b.el6.noarch ovirt-engine-wildfly-8.2.0-1.el6.x86_64 ovirt-engine-restapi-3.6.1-0.0.master.20151019163841.gitacec65b.el6.noarch ovirt-engine-dbscripts-3.6.1-0.0.master.20151019163841.gitacec65b.el6.noarch ovirt-engine-userportal-3.6.1-0.0.master.20151019163841.gitacec65b.el6.noarch ovirt-engine-3.6.1-0.0.master.20151019163841.gitacec65b.el6.noarch ovirt-engine-backend-3.6.1-0.0.master.20151019163841.gitacec65b.el6.noarch ovirt-engine-wildfly-overlay-001-2.el6.noarch ovirt-engine-tools-3.6.1-0.0.master.20151019163841.gitacec65b.el6.noarch
oVirt 3.6.0 has been released on November 4th, 2015 and should fix this issue. If problems still persist, please open a new BZ and reference this one.