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 2044698 - warning message "Failed to add conmon to systemd sandbox cgroup: Unit libpod-conmon-4XXX.scope already exists." when check cert on podman container
Summary: warning message "Failed to add conmon to systemd sandbox cgroup: Unit libpod-...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise Linux 9
Classification: Red Hat
Component: podman
Version: 9.0
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: rc
: ---
Assignee: Valentin Rothberg
QA Contact: atomic-bugs@redhat.com
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-01-25 02:38 UTC by yanpliu
Modified: 2023-09-15 01:19 UTC (History)
13 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-03-16 12:28:48 UTC
Type: Bug
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker RHELPLAN-109454 0 None None None 2022-01-25 02:42:36 UTC

Comment 2 Giuseppe Scrivano 2022-01-26 08:56:09 UTC 
can you easily reproduce this issue?

When the error happens, is the container still running or was it terminated in the meanwhile?  I am asking as it could be a race condition in our code where we try to create the cgroup and if it fails then fallback to moving the process to the cgroup (which could have been deleted).  Just a speculation though.
Comment 6 yanpliu 2022-03-15 08:54:00 UTC 
Verify on DISTRO=RHEL-9.1.0-20220309.3
This issue has been fixed.

# subscription-manager register --username=admin --password=admin --org=Default_Organization --environment=Library
Registering to: intel-waimeabay-hedt-01.ml3.eng.bos.redhat.com:443/rhsm
The system has been registered with ID: d1e57917-9ead-4316-a988-360564f0669a
The registered system name is: kvm-04-guest14.lab.eng.rdu2.redhat.com
[root@kvm-04-guest14 ~]# subscription-manager attach --auto
Installed Product Current Status:
Product Name: Red Hat Enterprise Linux for x86_64 Beta
Status:       Subscribed

[root@kvm-04-guest14 ~]#  podman create -t --name test_container registry-proxy.engineering.redhat.com/rh-osbs/ubi9 && podman start test_container
d9c0c03de09e41190d1d8033c3774e131e1169b548c0508ff719192cf5fd767f
test_container
[root@kvm-04-guest14 ~]# podman exec -i test_container /bin/bash -c "ls /run/secrets/etc-pki-entitlement/"
6582817744791521088-key.pem
6582817744791521088.pem
Comment 9 Tom Sweeney 2022-03-16 12:28:48 UTC 
Thanks yanpliu,

Closing as current release.
Comment 10 Red Hat Bugzilla 2023-09-15 01:19:03 UTC 
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 500 days
Note You need to log in before you can comment on or make changes to this bug.