Conflict between python2-paramiko and python-paramiko (was: Change in ovirt-system-tests[master]: hosted-engine basic suites: Fix collection)
1:45 p.m.
On Sun, Apr 1, 2018 at 12:49 PM, Code Review <gerrit(a)ovirt.org> 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
1:58 p.m.
On 1 April 2018 at 13:45, Yedidyah Bar David <didi(a)redhat.com> wrote:
On Sun, Apr 1, 2018 at 12:49 PM, Code Review <gerrit(a)ovirt.org>
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
9:13 a.m.
On Sun, Apr 1, 2018 at 1:58 PM, Barak Korren <bkorren(a)redhat.com> wrote:
On 1 April 2018 at 13:45, Yedidyah Bar David <didi(a)redhat.com>
wrote:
> On Sun, Apr 1, 2018 at 12:49 PM, Code Review <gerrit(a)ovirt.org> 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?
See above link to jenkins...
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
--
Didi
9:19 a.m.
On 2 April 2018 at 09:13, Yedidyah Bar David <didi(a)redhat.com> wrote:
On Sun, Apr 1, 2018 at 1:58 PM, Barak Korren
<bkorren(a)redhat.com> wrote:
> On 1 April 2018 at 13:45, Yedidyah Bar David <didi(a)redhat.com> wrote:
>> On Sun, Apr 1, 2018 at 12:49 PM, Code Review <gerrit(a)ovirt.org> 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?
See above link to jenkins...
I was hoping you'd save me the trouble of reading through the logs and
reacihng conclusions you must have already reached.
I meant - is this happening in the Lago VM, inside mock or on the slave itself?
--
Barak Korren
RHV DevOps team , RHCE, RHCi
Red Hat EMEA
redhat.com | TRIED. TESTED. TRUSTED. | redhat.com/trusted
9:29 a.m.
On Mon, Apr 2, 2018 at 9:19 AM, Barak Korren <bkorren(a)redhat.com> wrote:
On 2 April 2018 at 09:13, Yedidyah Bar David <didi(a)redhat.com>
wrote:
> On Sun, Apr 1, 2018 at 1:58 PM, Barak Korren <bkorren(a)redhat.com> wrote:
>> On 1 April 2018 at 13:45, Yedidyah Bar David <didi(a)redhat.com> wrote:
>>> On Sun, Apr 1, 2018 at 12:49 PM, Code Review <gerrit(a)ovirt.org> 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?
>
> See above link to jenkins...
>
I was hoping you'd save me the trouble of reading through the logs and
reacihng conclusions you must have already reached.
I meant - is this happening in the Lago VM, inside mock or on the slave itself?
Sorry, didn't look yet. Just searched for 'error' in the console output.
--
Barak Korren
RHV DevOps team , RHCE, RHCi
Red Hat EMEA
redhat.com | TRIED. TESTED. TRUSTED. | redhat.com/trusted
--
Didi
9:46 a.m.
On Mon, Apr 2, 2018 at 9:29 AM, Yedidyah Bar David <didi(a)redhat.com> wrote:
On Mon, Apr 2, 2018 at 9:19 AM, Barak Korren
<bkorren(a)redhat.com> wrote:
> On 2 April 2018 at 09:13, Yedidyah Bar David <didi(a)redhat.com> wrote:
>> On Sun, Apr 1, 2018 at 1:58 PM, Barak Korren <bkorren(a)redhat.com> wrote:
>>> On 1 April 2018 at 13:45, Yedidyah Bar David <didi(a)redhat.com> wrote:
>>>> On Sun, Apr 1, 2018 at 12:49 PM, Code Review <gerrit(a)ovirt.org>
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?
>>
>> See above link to jenkins...
>>
> I was hoping you'd save me the trouble of reading through the logs and
> reacihng conclusions you must have already reached.
>
> I meant - is this happening in the Lago VM, inside mock or on the slave itself?
Sorry, didn't look yet. Just searched for 'error' in the console output.
OK, found:
https://gerrit.ovirt.org/89711
>
>
> --
> Barak Korren
> RHV DevOps team , RHCE, RHCi
> Red Hat EMEA
> redhat.com | TRIED. TESTED. TRUSTED. | redhat.com/trusted
--
Didi
--
Didi
2426
days inactive
2427
days old
5 comments
2 participants
participants (2)
-
Barak Korren -
Yedidyah Bar David