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.
DescriptionBlake Henderson
2021-12-01 19:16:41 UTC
Description of problem:
- when trying to run a new container in a rootless pod after a system reboot we encounter the error
"Error: pod 3e339e128e6f7dabe65d3ed1c26202e983db93da373c697b14b166e4314e6c51 cgroup is not set: internal libpod error""
How reproducible:
- For me everytime
Steps to Reproduce:
1. create a test pod as a rootless podman user
2. add a container to the rootless pod
3. reboot the machine
4. try to add a second container to rootless pod
Actual results:
- encounter error mentioned above
Expected results:
- successfully run a new container in the pod
Additional info:
- I am able to replicate this in RHEL 8.4 and 8.5 however when I try in RHEL 7.9
it works as expected. Most up-to-date podman versions per release
Case 03093325
Hi Blake,
I tried reproducing the issue and wasn't able to. Can you please give me some exact steps - did you start the pod after creating the first container and then rebooted the machine or was it just in created state? And does this work when you create the pod and container as root?
Dan, we currently have:
Podman 3.0.1 to RHEL 8.4
Podman 3.2.3 to RHEL 8.4.0.2 and RHEL 9 Alpha
So we would need to get something into Podmans v3.2.3-rhel branch and then have Jindrich prepare it for the next 8.4.0.z release. I'm not sure which that would be. @snanda Thoughts on that?
@umohnani I don't see any backports for this. Can you prepare a backport for at least the v3.2.3-rhel branch, please?
This we can then get into RHEL 8.4.0.9 and we'll need to complete this by the end of April if not sooner. @snanda please note this BZ on your list for that release.
@dornelas or @jnovy are there other places either of you think we should drop the fix into? This works in RHEL 7.9, but is not working in RHEL 8.3, 8.4, or 8.5.
https://access.redhat.com/support/policy/updates/containertools
---
The Container-Tools AppStreams do not provide support nor maintenance updates in conjunction with the Extended Update Support (EUS) channels. Systems configured to use Red Hat Enterprise Linux 8 EUS will not receive updates if the Container-Tools AppStreams are configured. Users seeking security and select bug fixes for fixed versions of Container-Tools should configure an available Stable Stream for an active minor release of RHEL.
---
The currently supported Stable module streams are:
container-tools:2.0 which contains podman v1.6.4
container-tools:3.0 which contains podman v3.0.1
With the release of Red Hat Enterprise Linux 8.6, the container-tools:4.0 module stream will be available. At that time both container-toos:4.0 and the rolling container-tools:rhel8 module stream will include podman v4.0.2, and podman v3.2.3 will no longer be maintained.
For users utilizing the container-tools:rhel8 stream, this issue will be addresses in podman v4.0.2. Users that are consuming either of the active Stable module streams should talk to their support representative about requesting a fix for their relevant stream.
Based on Derrick's comments in https://bugzilla.redhat.com/show_bug.cgi?id=2028243#c27, we just missed the RHEL 8.4 window and will have to close this as current "NextRelase" which will be RHEL 8.6 coming out in a few weeks. Apologies for the missed mark.