Re: Conflict between python2-paramiko and python-paramiko (was: Change in ovirt-system-tests[master]: hosted-engine basic suites: Fix collection)

On 1 April 2018 at 13:45, Yedidyah Bar David <didi(a)redhat.com&gt; wrote: > On Sun, Apr 1, 2018 at 12:49 PM, Code Review <gerrit(a)ovirt.org&gt; wrote: >> From Jenkins CI: >> >> Jenkins CI has posted comments on this change. >> >> Change subject: hosted-engine basic suites: Fix collection >> ...................................................................... >> >> >> Patch Set 5: Continuous-Integration-1 >> >> Build Failed >> >> http://jenkins.ovirt.org/job/ovirt-system-tests_master_check-patch-el7-x8... : FAILURE > > 08:08:06 file /usr/lib/python2.7/site-packages/paramiko/__init__.pyc > from install of python2-paramiko-1.16.1-2.el7.noarch conflicts with > file from package python-paramiko-2.1.1-2.el7.noarch > 08:08:06 file /usr/lib/python2.7/site-packages/paramiko/__init__.pyo > from install of python2-paramiko-1.16.1-2.el7.noarch conflicts with > file from package python-paramiko-2.1.1-2.el7.noarch > 08:08:06 file /usr/lib/python2.7/site-packages/paramiko/_version.py > from install of python2-paramiko-1.16.1-2.el7.noarch conflicts with > file from package python-paramiko-2.1.1-2.el7.noarch > ... > > Known issue? > -- > Didi Where is this happening?

We saw this a while ago US as well as DS, and for some reason it resurfaced now. We merged a patch to fix this on slaves (by removing python2-paramiko) on Friday. Generally the issue is that python2-paramiko which is an olde package from epel conflicts with the much newer python-paramiko from RHEL. -- Barak Korren RHV DevOps team , RHCE, RHCi Red Hat EMEA redhat.com | TRIED. TESTED. TRUSTED. | redhat.com/trusted