Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
DescriptionDamien Ciabrini
2019-08-01 20:46:25 UTC
Description of problem:
When podman creates a container, it creates two additional systemd
scopes dynamically:
- libpod-conmon-<CONTAINERID>.scope - runs a conmon process that
tracks a container's pid1 into a dedicated pidfile.
- libpod-<CONTAINERID>.scope - created dynamically by runc,
for cgroups accounting.
The liveness of the scopes is directly tied to that of the podman
container.
On shutdown, systemd stops both services like pacemaker _and_ scopes,
in no particular order. Which means that it can happen that systemd
stops the container's scopes _before_ pacemaker itself. When that
it the case, the following :
- the stopped scope sends a SIGTERM to the pid1 of the pacemaker
container (i.e. pacemaker remote).
- this makes the pacemaker container stops.
- pacemaker notices that the pacemaker remote node stopped
unexpectedly and pacemaker may try to restart it.
Ultimately the whole sequence of shutdown gets polluted and sometimes
yields an error that blocks the regular shutdown, or block the restart
once the node has rebooted.
There's no option in podman to configure the scope file to not stop
before pacemaker is stopped. The only workaround so far is to inject
an additional drop-in file for each scope, with extra dependencies
that prevents systemd from stopping the scopes file before pacemaker
is stopped (so effectively, giving back the entire control to
pacemaker).
Version-Release number of selected component (if applicable):
resource-agents-4.1.1-17.el8_0.3.x86_64
How reproducible:
Always
Steps to Reproduce:
1. create a bundle ocf resource in the cluster.
2. shutdown one cluster node
3. check in the journal whether the pacemaker-remote process received a SIGTERM before the pacemaker service was stopped by pacemaker
Actual results:
A pacemaker-managed podman container is stopped by systemd instead of pacemaker
Expected results:
pacemaker should be the only one to stop pacemaker-managed container.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
https://access.redhat.com/errata/RHBA-2019:3307
Description of problem: When podman creates a container, it creates two additional systemd scopes dynamically: - libpod-conmon-<CONTAINERID>.scope - runs a conmon process that tracks a container's pid1 into a dedicated pidfile. - libpod-<CONTAINERID>.scope - created dynamically by runc, for cgroups accounting. The liveness of the scopes is directly tied to that of the podman container. On shutdown, systemd stops both services like pacemaker _and_ scopes, in no particular order. Which means that it can happen that systemd stops the container's scopes _before_ pacemaker itself. When that it the case, the following : - the stopped scope sends a SIGTERM to the pid1 of the pacemaker container (i.e. pacemaker remote). - this makes the pacemaker container stops. - pacemaker notices that the pacemaker remote node stopped unexpectedly and pacemaker may try to restart it. Ultimately the whole sequence of shutdown gets polluted and sometimes yields an error that blocks the regular shutdown, or block the restart once the node has rebooted. There's no option in podman to configure the scope file to not stop before pacemaker is stopped. The only workaround so far is to inject an additional drop-in file for each scope, with extra dependencies that prevents systemd from stopping the scopes file before pacemaker is stopped (so effectively, giving back the entire control to pacemaker). Version-Release number of selected component (if applicable): resource-agents-4.1.1-17.el8_0.3.x86_64 How reproducible: Always Steps to Reproduce: 1. create a bundle ocf resource in the cluster. 2. shutdown one cluster node 3. check in the journal whether the pacemaker-remote process received a SIGTERM before the pacemaker service was stopped by pacemaker Actual results: A pacemaker-managed podman container is stopped by systemd instead of pacemaker Expected results: pacemaker should be the only one to stop pacemaker-managed container.