Podman scope unit is listed as failed

Issue

If you run 'systemctl | grep -i failed', you discovered a failed systemd scope unit:

[root@controller ~]# systemctl | grep -i failed
● libpod-3f61c4efc9f5f576d12e6d04b3d3b420c524392088678234857e8f5cf4736174.scope                                                        loaded failed failed    libcontainer container 

A closer inspection of the service shows:

[root@controller ~]# systemctl status libpod-3f61c4efc9f5f576d12e6d04b3d3b420c524392088678234857e8f5cf4736174.scope
● libpod-3f61c4efc9f5f576d12e6d04b3d3b420c524392088678234857e8f5cf4736174.scope - libcontainer container 3f61c4efc9f5f576d12e6d04b3d3b420c524392088678234857e8f5cf4736174
   Loaded: loaded (/run/systemd/transient/libpod-3f61c4efc9f5f576d12e6d04b3d3b420c524392088678234857e8f5cf4736174.scope; transient)
Transient: yes
   Active: failed
      CPU: 0

Nov 24 07:09:04 controller systemd[1]: libpod-3f61c4efc9f5f576d12e6d04b3d3b420c524392088678234857e8f5cf4736174.scope: Failed to add PIDs to scope's control group: No such process
Nov 24 07:09:04 controller systemd[1]: libpod-3f61c4efc9f5f576d12e6d04b3d3b420c524392088678234857e8f5cf4736174.scope: Failed with result 'resources'.
Nov 24 07:09:04 controller systemd[1]: Failed to start libcontainer container 3f61c4efc9f5f576d12e6d04b3d3b420c524392088678234857e8f5cf4736174.

However the container the service is referring to is up and looks healthy:

[root@controller ~]# podman ps | grep -i 3f61c4efc9f5
3f61c4efc9f5  director.local:8787/osp16-redhat_osp_rhel_8-horizon:16.1                     kolla_start           24 hours ago    Up 4 hours ago            horizon