Why is the "Install the Tower RPM" Task Failing with Missing Dependencies During an Install/Upgrade of Ansible Tower to 3.5?

Solution Verified - Updated -

Issue

During an install or upgrade to Ansible Tower 3.5, the "Install the Tower RPM" task in the installer playbook fails with the following:

fatal: [host01]: FAILED! => {"changed": true, "msg": "Error: Package: ansible-tower-venv-tower-3.5.0-1.el7at.x86_64 (ansible-tower)\n           Requires: rh-python36-python\nError: Package: ansible-tower-3.5.0-1.el7at.x86_64 (ansible-tower)\n           Requires: rh-python36-runtime\n", "obsoletes": {"pexpect": {"dist": "noarch", "repo": "@centos-7-base", "version": "2.3-11.el7"}, "python-psycopg2": {"dist": "x86_64", "repo": "@centos-7-base", "version": "2.5.1-3.el7"}}, "rc": 1, "results": ["Loaded plugins: fastestmirror, langpacks, priorities\nLoading mirror speeds from cached hostfile\n478 packages excluded due to repository priority protections\nResolving Dependencies\n--> Running transaction check\n---> Package ansible-tower.x86_64 0:3.4.2-1.el7 will be updated\n---> Package ansible-tower.x86_64 0:3.5.0-1.el7at will be an update\n--> Processing Dependency: ansible-tower-ui = 3.5.0-1.el7at for package: ansible-tower-3.5.0-1.el7at.x86_64\n--> Processing Dependency: ansible-tower-server = 3.5.0-1.el7at for package: ansible-tower-3.5.0-1.el7at.x86_64\n--> Processing Dependency: rh-python36-runtime for package: ansible-tower-3.5.0-1.el7at.x86_64\n--> Running transaction check\n---> Package ansible-tower.x86_64 0:3.5.0-1.el7at will be an update\n--> Processing Dependency: rh-python36-runtime for package: ansible-tower-3.5.0-1.el7at.x86_64\n---> Package ansible-tower-server.x86_64 0:3.4.2-1.el7 will be updated\n---> Package ansible-tower-server.x86_64 0:3.5.0-1.el7at will be an update\n--> Processing Dependency: ansible-tower-venv-tower = 3.5.0-1.el7at for package: ansible-tower-server-3.5.0-1.el7at.x86_64\n--> Processing Dependency: ansible-tower-venv-ansible = 3.5.0-1.el7at for package: ansible-tower-server-3.5.0-1.el7at.x86_64\n---> Package ansible-tower-ui.x86_64 0:3.4.2-1.el7 will be updated\n---> Package ansible-tower-ui.x86_64 0:3.5.0-1.el7at will be an update\n--> Running transaction check\n---> Package ansible-tower.x86_64 0:3.5.0-1.el7at will be an update\n--> Processing Dependency: rh-python36-runtime for package: ansible-tower-3.5.0-1.el7at.x86_64\n---> Package ansible-tower-venv-ansible.x86_64 0:3.4.2-1.el7 will be updated\n---> Package ansible-tower-venv-ansible.x86_64 0:3.5.0-1.el7at will be an update\n---> Package ansible-tower-venv-tower.x86_64 0:3.4.2-1.el7 will be updated\n---> Package ansible-tower-venv-tower.x86_64 0:3.5.0-1.el7at will be an update\n--> Processing Dependency: rh-python36-python for package: ansible-tower-venv-tower-3.5.0-1.el7at.x86_64\n--> Finished Dependency Resolution\n You could try using --skip-broken to work around the problem\n You could try running: rpm -Va --nofiles --nodigest\n"]}

Environment

  • Ansible Tower

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.

Current Customers and Partners

Log in for full access

Log In