AAP 2.3 / AAP 2.4 Error Running Job with Podman System Migrate

Mindwatering Incorporated

Author: Tripp W Black

Created: 06/15 at 01:27 PM

 

Category:
RH AAP
Troubleshooting

Issue:
AAP failing jobs.

ERRO ... invalid internal status, try resetting the pause process with "/usr/bin/podman system migrate" ... could not find any running process: no such process


Workarounds:
Manually run podman command as the awx user. Clear the forever Stopping container.
See also RH technote 6988045.


a. Login to the controller:
$ ssh root@mwctl1.mindwatering.net
<enter password if prompted>

b. If using AAP, switch to the podman_mgr user or awx user.
# su - podman_mgr
or
# su - awx
<no password is prompted>

c. Manually run the command:
[awx@mwctl1 ~]$ /usr/bin/podman system migrate
<wait a second or three>

[awx@mwctl1 ~]$ podman ps -a
<locate the pod that is stuck Stopping - note its CONTAINER ID>

[awx@mwctl1 ~]$ podman rm abc12d3e4567
Error: error freeing lock for container abc12d3e4567...: no such file or directory

Note:
- The error displays, but the next call for ps -a will show it gone

[awx@mwctl1 ~]$ podman ps -a
<confirm STOPPING pod now gone>

[awx@mwctl1 ~]$ podman images
<review the returned REPOSITORY TAG IMAGE ID ... columns and rows>

[awx@mwctl1 ~]$ exit

# exit

c: Return to the UI, re-run the failed job again.



previous page

×