After upgrading Ansible Automation Platfrom to 2.3, the WebUI of Private Automation Hub is throwing "'502 Bad Gateway " error.

Solution Verified - Updated -

Issue

  • After upgrading Ansible Automation Platfrom to 2.3, the WebUI of Private Automation Hub is throwing "'502 Bad Gateway " error.

  • We upgraded our AAP to 2.3 from 2.2.2-1. After the upgrade, we are not able to access Private Automation Hub. We are getting '502 Bad Gateway' in the browser while accessing PAH. We tried restarting the services in PAH but the issue still persists. We checked the logs in /var/log/messages and found this error, 'FileNotFoundError: [Errno 2] No such file or directory: '/var/lib/pulp/assets/guardian/img/icon-no.svg''

    Jun 15 00:59:11 x388139 gunicorn[446539]: FileNotFoundError: [Errno 2] No such file or directory: '/var/lib/pulp/assets/guardian/img/icon-no.svg'

Environment

  • Ansible Automation Platform 2.3

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content