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.
Bug 1942753 - IPv6 errors after exiting crictl [rhel-8.4.0.z]
Summary: IPv6 errors after exiting crictl [rhel-8.4.0.z]
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: podman
Version: 8.5
Hardware: All
OS: Linux
medium
medium
Target Milestone: rc
: ---
Assignee: Jindrich Novy
QA Contact: Alex Jia
URL:
Whiteboard:
: 1942665 (view as bug list)
Depends On: 1932399
Blocks: 1937847
TreeView+ depends on / blocked
 
Reported: 2021-03-24 21:37 UTC by RHEL Program Management Team
Modified: 2021-08-10 14:38 UTC (History)
18 users (show)

Fixed In Version: podman-3.2.3-0.2.el8_4 or newer
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 1932399
Environment:
Last Closed: 2021-08-10 13:54:32 UTC
Type: Bug
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2021:3070 0 None None None 2021-08-10 13:54:46 UTC

Comment 1 Derrick Ornelas 2021-03-24 21:41:50 UTC 
*** Bug 1942665 has been marked as a duplicate of this bug. ***
Comment 4 Daniel Walsh 2021-03-25 12:20:39 UTC 
8.4.0.2 will contain whatever is shipping in Fedora 34 at the time of the freeze.
Comment 22 Alex Jia 2021-07-29 09:53:59 UTC 
Thank you Peter and Tom!

The podman-3.2.3-0.10.module+el8.4.0+11989+6676f7ad works well for me.

In terminal 1
$ podman run --pod=new:alpine-sandbox --name alpine --cap-add NET_RAW alpine sleep 3600

In terminal 2
$ sudo podman pod ps
POD ID        NAME            STATUS      CREATED        INFRA ID      # OF CONTAINERS
f32daae270df  alpine-sandbox  Running     6 seconds ago  eb1ee0effb9a  2

$ sudo podman pod stop alpine-sandbox
f32daae270df9fa18a97adf6292cdfcdb71fda99cfe17134e0ca4ee992c8e905

$ sudo podman pod ps
POD ID        NAME            STATUS      CREATED             INFRA ID      # OF CONTAINERS
f32daae270df  alpine-sandbox  Exited      About a minute ago  eb1ee0effb9a  2

$ sudo podman pod rm alpine-sandbox
f32daae270df9fa18a97adf6292cdfcdb71fda99cfe17134e0ca4ee992c8e905

$ sudo podman pod ps
POD ID      NAME        STATUS      CREATED     INFRA ID    # OF CONTAINERS
Comment 26 errata-xmlrpc 2021-08-10 13:54:32 UTC 
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 (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/RHBA-2021:3070
Note You need to log in before you can comment on or make changes to this bug.