[ovirt-users] RPM conflicts when upgrading from 4.1.9 to 4.2.2

[Matthias Leopold]

Hi,

i tried to upgrade my oVirt 4.1.9 test environment to version 4.2.2.
this failed on the engine host with messages like

2018-04-23 11:10:57,716+0200 ERROR 
otopi.plugins.otopi.packagers.yumpackager yumpackager.error:85 Yum 
Test-Transaktionsfehler:   file /usr/share/ansible/roles/ovirt-manageiq 
from install of ovirt-ansible-roles-1.0.4-1.el7.centos.noarch conflicts 
with file from package ovirt-ansible-manageiq-1.1.6-1.el7.centos.noarch
   file /usr/share/ansible/roles/ovirt-image-template from install of 
ovirt-ansible-roles-1.0.4-1.el7.centos.noarch conflicts with file from 
package ovirt-ansible-image-template-1.1.5-1.el7.centos.noarch
   file /usr/share/ansible/roles/ovirt-infra from install of 
ovirt-ansible-roles-1.0.4-1.el7.centos.noarch conflicts with file from 
package ovirt-ansible-infra-1.1.4-1.el7.centos.noarch
   file /usr/share/ansible/roles/ovirt-vm-infra from install of 
ovirt-ansible-roles-1.0.4-1.el7.centos.noarch conflicts with file from 
package ovirt-ansible-vm-infra-1.1.5-1.el7.centos.noarch
   file /usr/share/ansible/roles/ovirt-cluster-upgrade from install of 
ovirt-ansible-roles-1.0.4-1.el7.centos.noarch conflicts with file from 
package ovirt-ansible-cluster-upgrade-1.1.6-1.el7.centos.noarch

i'm attaching the setup log file.

fact is that the engine host CentOS 7.4 OS hasn't been updated for a 
while before the oVirt upgrade, i wanted to do that after successful 
oVirt upgrade. this seems to have played a role in failure to start the 
openvswitch service which happened before the final failure (seems to be 
a problem of SELinux policy)

engine host OS configuration is roughly:

kernel: 3.10.0-693.17.1.el7.x86_64
SELinux policy: 3.13.1-166.el7_4.7.noarch

repolist:

centos-opstools-release/x86_64
centos-sclo-rh-release/x86_64
centos7-x86_64
centos7-x86_64-extras
centos7-x86_64-sclo-rh
centos7-x86_64-updates
ovirt-4.1/7
ovirt-4.1-centos-gluster38/x86_64
ovirt-4.1-centos-qemu-ev/x86_64
ovirt-4.1-epel/x86_64
ovirt-4.1-patternfly1-noarch-epel/x86_64
ovirt-4.2/7
ovirt-4.2-centos-gluster312/x86_64
ovirt-4.2-centos-opstools/x86_64
ovirt-4.2-centos-ovirt42/x86_64
ovirt-4.2-centos-qemu-ev/x86_64
ovirt-4.2-epel/x86_64
ovirt-4.2-virtio-win-latest
ovirt-centos-ovirt41/x86_64
sac-gdeploy/x86_64
virtio-win-stable

the host that is the engine is a VMware VM (no self hosted engine setup)

thanks for any help

-- 
Matthias Leopold
IT Systems & Communications
Medizinische Universität Wien
Spitalgasse 23 / BT 88 /Ebene 00
A-1090 Wien
Tel: +43 1 40160-21241
Fax: +43 1 40160-921200
-------------- next part --------------
A non-text attachment was scrubbed...
Name: ovirt-engine-setup-20180423105714-kx8t8a.log.gz
Type: application/gzip
Size: 300602 bytes
Desc: not available
URL: <http://lists.ovirt.org/pipermail/users/attachments/20180423/a2c6acc2/attachment.bin>