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>
I'm seeing the same thing installing tripleoclient via quickstart so I suspect some repo conflict is causing this