Safe Stop / Start Sequence for Red Hat Ansible Automation Platform 2.5

Solution Verified - Updated -

Issue

  • Administrators need a clear, repeatable order to shut down and power up a multi-node Ansible Automation Platform (AAP) 2.5 deployment.

  • Stopping the wrong service first can drop running jobs, corrupt queues, or leave the web front end unreachable after maintenance.

Environment

  • Clustered Ansible Auotomation Platform 2.5 or higher with nodes below:

    • Platform Gateway ×1

    • Automation Controller ×1

    • Execution Node ×1

    • Private Automation Hub ×1

    • Event-Driven Ansible ×1

    • External PostgreSQL 15 & Redis

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