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.
Bug 2052697 - Inconsistency in how the podman service behaves depending on whether it is providing API via UNIX or TCP socket.
Summary: Inconsistency in how the podman service behaves depending on whether it is pr...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: podman
Version: 8.5
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: rc
: ---
Assignee: Jindrich Novy
QA Contact: Edward Shen
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-02-09 19:35 UTC by Matt Mezynski
Modified: 2023-09-18 04:31 UTC (History)
15 users (show)

Fixed In Version: podman-4.2.0-1.el8
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-11-08 09:14:55 UTC
Type: Bug
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github containers podman pull 13450/files#diff-704e475171a87afc20abd8f6775b00ea9127213539ea2aba81abec16b400c6eb 0 None None None 2022-03-16 22:39:11 UTC
Github containers podman pull 14596 0 None Merged libpod: improve check to create conmon cgroup 2022-07-04 11:57:13 UTC
Red Hat Issue Tracker RHELPLAN-111742 0 None None None 2022-02-09 19:39:44 UTC
Red Hat Product Errata RHSA-2022:7457 0 None None None 2022-11-08 09:15:35 UTC

Comment 2 Daniel Walsh 2022-02-10 21:54:28 UTC 
Jhon, Valentin and Giuseppe any thouhgts on why this would happen, or is this a red herring?

I can't imagine this is much of a difference which would bring down the container started by the service.  As long as the service is moved out of the services cgroup.

Could someone try to verify if they can get this to happen.
Comment 5 Daniel Walsh 2022-03-02 18:06:27 UTC 
Jon any idea what is going on here?
Comment 6 Jhon Honce 2022-03-16 22:39:11 UTC 
The exit code handling is addressed in https://github.com/containers/podman/pull/13450

I was unable to reproduce the problem with the current podman code. I introduced systemd_activate_test.go to verify container state when `systemctl stop podman.service` is used.
Comment 16 Daniel Walsh 2022-06-14 16:45:59 UTC 
Is this different when you are using a unix domain socket, or does it break there as well?
Comment 17 Giuseppe Scrivano 2022-06-14 19:56:32 UTC 
I do not see any difference when I use a UNIX domain socket
Comment 18 Daniel Walsh 2022-06-14 19:58:15 UTC 
Ok, to fix this we would want to move the conmons out to their own cgroup correct?
Comment 19 Giuseppe Scrivano 2022-06-15 09:07:15 UTC 
opened a PR upstream: https://github.com/containers/podman/pull/14596
Comment 20 Tom Sweeney 2022-06-28 20:21:37 UTC 
As the PR is merged, I'm assigning this @jnovy for any further BZ/packaging needs
Comment 29 errata-xmlrpc 2022-11-08 09:14:55 UTC 
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 (Moderate: container-tools:rhel8 security, bug fix, and enhancement update), 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/RHSA-2022:7457
Comment 30 Red Hat Bugzilla 2023-09-18 04:31:46 UTC 
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 120 days
Note You need to log in before you can comment on or make changes to this bug.