Podman スコープユニットが失敗としてリストされている
Issue
'systemctl | grep -i failed' を実行すると、systemd スコープユニットが失敗することがわかります。
[root@controller ~]# systemctl | grep -i failed
● libpod-3f61c4efc9f5f576d12e6d04b3d3b420c524392088678234857e8f5cf4736174.scope loaded failed failed libcontainer container
詳細は、以下のようになります。
[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.
ただし、サービスが参照しているコンテナーは稼働しており、正常に見えます。
[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
Environment
- Red Hat Enterprise Linux 8
- Red Hat OpenStack Platform 16.1
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.