Issue:
The AAP base ansible-core and automation-hub are in both the ansible-automation-platform-2.x-for-rhel-x-x86_64-rpms
and the appstream rhel-x-for-x86_64-appstream-rpms repos. Unfortunately, the appstream repo version is NOT typically compatible with the ansible-automation-platform repo.
On the automation-hub, we typically find our system as a "502 Gateway" error when we try to bring up the web GUI.
Note:
The x above are the OS and AAP versions. Examples:
rhel-8-for-x86_64-appstream-rpms
rhel-9-for-x86_64-appstream-rpms
ansible-automation-platform-2.4-for-rhel-8-x86_64-rpms
ansible-automation-platform-2.4-for-rhel-9-x86_64-rpms
ansible-automation-platform-2.5-for-rhel-9-x86_64-rpms
Resolution:
OS patching must exclude the appstream-rpms library and only use the ansible-automation-platform ansible-core libraries.
Two options are:
- Option 1: Since we use the offline bundles, we can exclude Ansible like so:
a. Update yum:
$ sudo vi /etc/yum.conf
...
exclude=kernel* redhat-release* ansible-*
...
<esc>:wq (to save)
b. Update dnf:
$ sudo vi /etc/dnf/dnf.conf
...
exclude=kernel* redhat-release* ansible-*
...
<esc>:wq (to save)
c. Re-install AAP using the offline bundle installation. See upgrading from AAP 2.1 to AAP 2.4, or the AAP 2.4 to AAP 2.5 instructions in this support repository for specific notes/instructions.
- Option 2: Disable the app-stream repo and install from the AAP repo.
$ sudo dnf info ansible-core
<view output and review the "From repo" line>
$ sudo dnf info automation-hub
<view output and review the "From repo" line>
If uses the appstream repo, to fix:
$ sudo su -
# yum-config-manager --disable rhel-x-for-x86_64-appstream-rpms
# rpm -e --nodeps ansible-core
# dnf install --enablerepo=ansible-automation-platform ansible-core
or if you are reinstalling ansible-core automation-hub:
# dnf install --enablerepo=ansible-automation-platform ansible-core automation-hub
See RHAT technotes: 7048248 and 7024954
previous page
|