AAP 2.5 RPM-based installation fails on TASK Ensure changes are applied to podman

Solution Verified - Updated -

Issue

  • While installing AAP 2.5, setup.sh fails on below task:-

    TASK [ansible.automation_platform_installer.podman : Ensure changes are applied to podman] ***
    fatal: [controller.example.com]: FAILED! => {"changed": true, "cmd": ["podman",
    "system",
    "migrate"], "delta": "0:00:00.083793",
    "end": "2025-05-12 13:25:50.793786",
    "msg": "non-zero return code",
    "rc": 125, "start": "2025-05-12 13:25:50.709993",
    "stderr": "cannot clone: No space left on device\nuser namespaces are not enabled in /proc/sys/user/max_user_namespaces\nError: cannot re-exec process",
    "stderr_lines": ["cannot clone: No space left on device",
    "user namespaces are not enabled in /proc/sys/user/max_user_namespaces",
    "Error: cannot re-exec process"], "stdout": "",
    "stdout_lines": []}
    
  • During the installation of Ansible Automation Platform (AAP) 2.5, the setup script failed while executing the podman system migrate command.

Environment

  • Red Hat Ansible Automation Platform 2.5
  • Red Hat Enterprise Linux

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