Unable to unstall openshift

Bug #1807893 reported by Martin Mágr
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
tripleo
Invalid
High
Unassigned

Bug Description

I'm trying to deploy OpenShift on three nodes via TripleO and am currently on packaging conflict on master and worker nodes:

2018-12-10 17:28:10,798 p=1 u=root | Failure summary:

  1. Hosts: telemetry-openshiftmaster-0, telemetry-openshiftworker-0, telemetry-openshiftworker-1
     Play: Install packages necessary for installer
     Task: Ensure openshift-ansible installer package deps are installed
     Message: ^[[0;31m^[[0m
               ^[[0;31m^[[0m
               ^[[0;31mTransaction check error:^[[0m
               ^[[0;31m file /usr/lib/python2.7/site-packages/docker/__init__.py from install of python-docker-py-1:1.10.6-7.el7.noarch conflicts with file from package python2-docker-3.3.0-1.el7.noarch^[[0m
               ^[[0;31m file /usr/lib/python2.7/site-packages/docker/api/__init__.py from install of python-docker-py-1:1.10.6-7.el7.noarch conflicts with file from package python2-docker-3.3.0-1.el7.noarch^[[0m
               ^[[0;31m file /usr/lib/python2.7/site-packages/docker/transport/__init__.py from install of python-docker-py-1:1.10.6-7.el7.noarch conflicts with file from package python2-docker-3.3.0-1.el7.noarch^[[0m
               ^[[0;31m file /usr/lib/python2.7/site-packages/docker/types/__init__.py from install of python-docker-py-1:1.10.6-7.el7.noarch conflicts with file from package python2-docker-3.3.0-1.el7.noarch^[[0m
               ^[[0;31m file /usr/lib/python2.7/site-packages/docker/utils/__init__.py from install of python-docker-py-1:1.10.6-7.el7.noarch conflicts with file from package python2-docker-3.3.0-1.el7.noarch^[[0m
               ^[[0;31m file /usr/lib/python2.7/site-packages/docker/__init__.pyc from install of python-docker-py-1:1.10.6-7.el7.noarch conflicts with file from package python2-docker-3.3.0-1.el7.noarch^[[0m
               ^[[0;31m file /usr/lib/python2.7/site-packages/docker/api/__init__.pyc from install of python-docker-py-1:1.10.6-7.el7.noarch conflicts with file from package python2-docker-3.3.0-1.el7.noarch^[[0m
               ^[[0;31m file /usr/lib/python2.7/site-packages/docker/transport/__init__.pyc from install of python-docker-py-1:1.10.6-7.el7.noarch conflicts with file from package python2-docker-3.3.0-1.el7.noarch^[[0m
               ^[[0;31m file /usr/lib/python2.7/site-packages/docker/types/__init__.pyc from install of python-docker-py-1:1.10.6-7.el7.noarch conflicts with file from package python2-docker-3.3.0-1.el7.noarch^[[0m
               ^[[0;31m file /usr/lib/python2.7/site-packages/docker/utils/__init__.pyc from install of python-docker-py-1:1.10.6-7.el7.noarch conflicts with file from package python2-docker-3.3.0-1.el7.noarch^[[0m
               ^[[0;31m file /usr/lib/python2.7/site-packages/docker/__init__.pyo from install of python-docker-py-1:1.10.6-7.el7.noarch conflicts with file from package python2-docker-3.3.0-1.el7.noarch^[[0m
               ^[[0;31m file /usr/lib/python2.7/site-packages/docker/api/__init__.pyo from install of python-docker-py-1:1.10.6-7.el7.noarch conflicts with file from package python2-docker-3.3.0-1.el7.noarch^[[0m
               ^[[0;31m file /usr/lib/python2.7/site-packages/docker/transport/__init__.pyo from install of python-docker-py-1:1.10.6-7.el7.noarch conflicts with file from package python2-docker-3.3.0-1.el7.noarch^[[0m
               ^[[0;31m file /usr/lib/python2.7/site-packages/docker/types/__init__.pyo from install of python-docker-py-1:1.10.6-7.el7.noarch conflicts with file from package python2-docker-3.3.0-1.el7.noarch^[[0m
<snip>

Revision history for this message
Steven Hardy (shardy) wrote :

I'm seeing the same thing installing tripleoclient via quickstart so I suspect some repo conflict is causing this

Changed in tripleo:
assignee: nobody → Steven Hardy (shardy)
assignee: Steven Hardy (shardy) → nobody
status: New → Triaged
importance: Undecided → High
Revision history for this message
Steven Hardy (shardy) wrote :

python-docker-py-1:1.10.6-7.el7.noarch seems to be pulled in from centos extras - disabling that repo on my virthost seems to have resolved the issue, Martin can you confirm if that also resolves your problem?

Revision history for this message
Steven Hardy (shardy) wrote :

Hmm actually -extras is also defined in tripleo-quickstart (config/release/tripleo-ci/CentOS-7/master.yml if you're using the tripleo-ci master release) so we may need to remove that?

Revision history for this message
Steven Hardy (shardy) wrote :

Ok after disabling -extras it then fails installing skopeo so it seems like there is more than one repo config, probably we need to confirm if --release master-tripleo-ci is still tested in CI or if that should now be removed

Revision history for this message
Steven Hardy (shardy) wrote :

So after some discussion on IRC (thanks marios & ykarel!) it seems this is a duplicate of https://bugs.launchpad.net/tripleo/+bug/1806853, which was fixed by https://review.rdoproject.org/r/#/c/17746/3/deps.yml

So it seems we both have some stale repo config such that we're getting the old version of python-docker?

Revision history for this message
Steven Hardy (shardy) wrote :

Ok so the fix in my case was to rm -fr /var/cache/tripleo-quickstart, the cached images were stale.

Martin can you confirm if the same fix works for you?

Revision history for this message
Juan Antonio Osorio Robles (juan-osorio-robles) wrote :

Is this still an issue?

Revision history for this message
Martin Mágr (mmagr) wrote :

Closing this really old bug.

Changed in tripleo:
status: Triaged → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.