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.
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 and bug fix 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-2023:6939
This bug has been verified on podman-4.4.1-9.module+el8.8.0+18526+1b4372bd.x86_64. [root@kvm-02-guest08 ~]# cat /etc/redhat-release Red Hat Enterprise Linux release 8.8 (Ootpa) [root@kvm-02-guest08 ~]# rpm -q podman runc criu systemd kernel podman-4.4.1-9.module+el8.8.0+18526+1b4372bd.x86_64 runc-1.1.4-1.module+el8.8.0+18060+3f21f2cc.x86_64 criu-3.15-3.module+el8.8.0+18060+3f21f2cc.x86_64 systemd-239-74.el8_8.x86_64 kernel-4.18.0-477.7.1.el8_8.x86_64 [root@kvm-02-guest08 ~]# podman run -d ubi8 sleep 300 3a036c57b7f14c49bf0dbea19b934d75ec64c023d284f7cb202496bc50b0de94 [root@kvm-02-guest08 ~]# podman container ps CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES 3a036c57b7f1 registry.access.redhat.com/ubi8:latest sleep 300 14 seconds ago Up 14 seconds dreamy_banach [root@kvm-02-guest08 ~]# podman container checkpoint -l 3a036c57b7f14c49bf0dbea19b934d75ec64c023d284f7cb202496bc50b0de94 [root@kvm-02-guest08 ~]# podman container ps -a CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES 3a036c57b7f1 registry.access.redhat.com/ubi8:latest sleep 300 39 seconds ago Exited (0) 17 seconds ago dreamy_banach [root@kvm-02-guest08 ~]# podman container inspect --format '{{.State.Status}}:{{.State.Running}}:{{.State.Paused}}:{{.State.Checkpointed}}' 3a036c57b7f1 exited:false:false:true [root@kvm-02-guest08 ~]# podman container restore -l 3a036c57b7f14c49bf0dbea19b934d75ec64c023d284f7cb202496bc50b0de94 [root@kvm-02-guest08 ~]# podman container ps CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES 3a036c57b7f1 registry.access.redhat.com/ubi8:latest sleep 300 About a minute ago Up About a minute dreamy_banach [root@kvm-02-guest08 ~]# podman container inspect --format '{{.State.Status}}:{{.State.Running}}:{{.State.Paused}}:{{.State.Checkpointed}}' 3a036c57b7f1 running:true:false:false