AAP 2.4 to 2.5 Upgrade Fails – automation-controller-operator-controller-manager Pod Enters CrashLoopBackOff due to insufficient memory limit

Solution Verified - Updated -

Issue

  • During an upgrade from AAP 2.4 to 2.5, the upgrade process stalls, and the automation-controller-operator-controller-manager pod fails to start AND the pod enters a CrashLoopBackOff state;
  • How to set resource limits for the automation hub pod of Ansible Automation Platform 2.5?

Environment

  • Red Hat Ansible Automation Platform (Ansible Automation Platform) 2.5
  • Red Hat OpenShift Container Platform (RHOCP) 4

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