Getting an "Error: current system boot ID differs from cached boot ID" message after restarting an Ansible Automation Platform cluster node

Solution Verified - Updated -

Issue

  • After restarting the node, the Ansible Automation Platform process does not start.
  • On the user where Ansible Automation Platform was installed, we execute the podman ps command.

  • This error occurs with Ansible Automation Platform 2.5 Containerized Setup installations.

    [user@aap25 ~]$ podman ps
Error: current system boot ID differs from cached boot ID; an unhandled reboot has occurred. Please delete directories "/tmp/storage-run-1000/containers" and "/tmp/storage-run-1000/libpod/tmp" and re-run Podman

Environment

  • Red Hat Ansible Automation Platform 2.5, Containerized install
  • Red Hat Enterprise Linux release 9
  • Podman 5.2 or later

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