Bug 2028243

Summary:	podman fails to run container in a rootless pod after reboot
Product:	Red Hat Enterprise Linux 8	Reporter:	Blake Henderson <bhenders>
Component:	podman	Assignee:	Tom Sweeney <tsweeney>
Status:	CLOSED NEXTRELEASE	QA Contact:	atomic-bugs <atomic-bugs>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	8.4	CC:	bbaude, cpippin, dornelas, dwalsh, jligon, jnovy, lsm5, mheon, pthomas, snanda, tsweeney, umohnani, vithakur, ypu
Target Milestone:	rc	Flags:	pm-rhel: mirror+
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2022-04-26 21:41:19 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Blake 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

Comment 1 Daniel Walsh 2021-12-01 19:51:12 UTC

Urvashi could you take a look.

Comment 2 Urvashi Mohnani 2021-12-10 17:18:50 UTC

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?

Comment 10 Daniel Walsh 2022-03-09 15:09:32 UTC

Is there a reason that the customer can not move to 4.0?

Comment 12 Daniel Walsh 2022-03-22 21:18:49 UTC

We only currently back port to long support cycle podman.  Which would be the Podman in 8.4, Not in 8.5.  Tom what podman do we support in 8.4?

Comment 13 Tom Sweeney 2022-03-23 13:46:28 UTC

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?

Comment 14 Daniel Walsh 2022-03-23 13:53:28 UTC

No I think we only support porman 3.0.1 on RHEL8.4 3.2.3 is on the module stream and continues to get updated.

Comment 17 Vijay Thakur 2022-04-12 07:50:20 UTC

Hi Team,

Can you please update current status on backporting. Also please confirm which version of RHEL podman 4.0 is landing.

Thanks

Comment 18 Daniel Walsh 2022-04-12 10:36:39 UTC

Podman 4.0 will be in RHEL8.6 and RHEL9.0

Comment 19 Tom Sweeney 2022-04-12 14:26:23 UTC

@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.

Comment 20 Urvashi Mohnani 2022-04-14 14:23:15 UTC

Created a PR for the backport to v3.2.2-rhel branch https://github.com/containers/podman/pull/13879.

Comment 21 Jindrich Novy 2022-04-20 05:54:54 UTC

Please switch this bugzilla to POST once merged, thanks!

Comment 22 Urvashi Mohnani 2022-04-21 17:48:55 UTC

Backport PR merged

Comment 23 Tom Sweeney 2022-04-21 19:30:33 UTC

Assigning to Jindrich for any further BZ or packaging needs.

Comment 27 Derrick Ornelas 2022-04-22 16:50:39 UTC

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.

Comment 32 Tom Sweeney 2022-04-26 21:41:19 UTC

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.