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.

Description of problem:
See https://github.com/containers/podman/issues/9492

Version-Release number of selected component (if applicable):
3.x

How reproducible:
See https://github.com/containers/podman/issues/9492

Steps to Reproduce:
1.See https://github.com/containers/podman/issues/9492
2.
3.

Actual results:
See https://github.com/containers/podman/issues/9492

Expected results:
See https://github.com/containers/podman/issues/9492

Additional info:
When this is fixed, also please ensure that the following fixes are also present in same version of RHEL/podman.
https://github.com/containers/podman/issues/9492
https://github.com/containers/podman/issues/9452
https://github.com/cri-o/ocicni/pull/85

thanks

We are looking into this as part of the broader discussion on a rework of the Podman network stack, and have begun initial investigation. However, this will require extensive changes to the Podman network stack to accomplish, and we are still exploring the full extent of the changes that will be required.

As this is part of Podman v4.0 and included in RHEL 8.6 and 9.0, I'm setting this to POST and assigning to Jindrich for any further packaging or BZ needs.

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 (Important: 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-2022:1762

The needinfo request[s] on this closed bug have been removed as they have been unresolved for 120 days