Bug 1898911
| Summary: | Empty cidfile after container creation | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 8 | Reporter: | Filip Januš <fjanus> |
| Component: | podman | Assignee: | Jindrich Novy <jnovy> |
| Status: | CLOSED ERRATA | QA Contact: | Alex Jia <ajia> |
| Severity: | high | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 8.3 | CC: | bbaude, ddarrah, dwalsh, hhorak, imcleod, jligon, jnovy, kanderso, lbalhar, lsm5, mheon, phracek, pkubat, pthomas, smccarty, tsweeney, umohnani, ypu |
| Target Milestone: | rc | Flags: | pm-rhel:
mirror+
|
| Target Release: | 8.0 | ||
| Hardware: | All | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | podman-2.2 or newer | Doc Type: | If docs needed, set a value |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2021-02-16 14:21:54 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: | |||
Can reproduce this bug on podman-2.1.1-2.module+el8.3.1+8289+097241fc.x86_64 w/ runc-1.0.0-68.rc92.module+el8.3.1+8289+097241fc.x86_64, and verified it on podman-2.2.1-3.module+el8.3.1+9380+85743958.x86_64 w/ runc-1.0.0-69.rc92.module+el8.3.1+9380+85743958.x86_64 1. podman-2.1.1-2.module+el8.3.1+8289+097241fc.x86_64 [root@hpe-dl380pgen8-02-vm-8 ~]# podman run -i --cidfile /tmp/foobar --name myctr1 rhel7 /bin/sh pwd / [root@ibm-x3650m4-01-vm-14 ~]# cat /tmp/foobar NOTE: nothing in /tmp/foobar 2. podman-2.2.1-3.module+el8.3.1+9380+85743958.x86_64 [root@ibm-x3650m4-01-vm-14 rpms]# podman run -i --cidfile /tmp/cidfile --name myctr2 rhel7 /bin/sh pwd / [root@ibm-x3650m4-01-vm-14 ~]# cat /tmp/cidfile 427e4b03313fe60c1ba066368af6c18bc189faaca570f483bfdfb44cbfa8afc6 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-2021:0531 The needinfo request[s] on this closed bug have been removed as they have been unresolved for 500 days |
Matt/Dan/Tom/All, Is there a way that we could roll forward to Podman 2.2.0 for the RHEL 8.3.1 release? I know it's late in the game, but my gut feeling says this is easier/safer/better than back porting. Is there anything that makes us nervous about supporting the 2.2.0 release for 12 weeks until we launch Podman 3.0 in RHEL 8.4?