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
Comment 27Red Hat Bugzilla
2024-03-14 04:25:33 UTC
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 120 days
This bug has been verified on podman-4.4.1-13.module+el8.9.0+18566+0239040b. [root@kvm-02-guest05 ~]# cat /etc/redhat-release Red Hat Enterprise Linux release 8.9 Beta (Ootpa) [root@kvm-02-guest05 ~]# rpm -q podman runc systemd kernel podman-4.4.1-13.module+el8.9.0+18566+0239040b.x86_64 runc-1.1.5-1.module+el8.9.0+18566+0239040b.x86_64 systemd-239-74.el8_8.x86_64 kernel-4.18.0-484.el8.x86_64 [root@kvm-02-guest05 ~]# podman play kube my-pod.yaml Pod: e66cf9f615b6f746fe5d553920516bcbd27ecfa6a8b3822f5a2ce32c480d0e50 Container: 8f987ae16efd4e6567d8fb5009b36c9d656f23bdc59a33cfdcf548d89bb0b03d [root@kvm-02-guest05 ~]# top ...ignore... PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND 116575 root 20 0 3900 2996 2772 R 29.6 0.1 0:05.75 bash 13 root 20 0 0 0 0 S 0.3 0.0 0:04.45 ksoftirqd/0 770 root 20 0 380872 18500 16024 S 0.3 0.5 2:47.14 NetworkManager ...ignore...