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.

Bug 2066486

Summary: podman 4.0 hangs indefinitely if ipv6 is disabled
Product: Red Hat Enterprise Linux 9 Reporter: Tom Sweeney <tsweeney>
Component: podmanAssignee: Jindrich Novy <jnovy>
Status: CLOSED ERRATA QA Contact: Alex Jia <ajia>
Severity: high Docs Contact:
Priority: unspecified    
Version: 9.0CC: ajia, bbaude, ddarrah, dwalsh, jnovy, lsm5, mheon, pholzing, pthomas, pvlasin, tsweeney, umohnani, ypu
Target Milestone: rcKeywords: Triaged
Target Release: ---Flags: pm-rhel: mirror+
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: podman-4.0.2-4.el9 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
: 2066489 2067488 (view as bug list) Environment:
Last Closed: 2022-05-17 12:42:09 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:
Bug Depends On:    
Bug Blocks: 2066489, 2067488    

Description Tom Sweeney 2022-03-21 21:33:47 UTC 
Description of problem:

Podman 4.0.1 will hang indefinitely with this *warning* if ipv6 is disabled on the system:


level=warning msg="failed to set net.ipv6.conf.default.accept_dad sysctl: open /proc/sys/net/ipv6/conf/default/accept_dad: no such file or directory"


**Steps to reproduce the issue:**

1. disable ipv6 (e.g. with kernel parameter `ipv6.disable=1`

2. `podman run --rm hello-world`

3. <hangs indefinitely>
Comment 2 Tom Sweeney 2022-03-21 21:41:59 UTC 
======= Impact Statement ======= 

What is the benefit of making this change after the deadline? What is the impact on customer satisfaction, and on the business?

a. For bugfixes, there must be support from someone in Customer Support, a Partner Manager, Product Manager, and/or a Business Unit rep. (e.g., potentially from a layered product BU). 
b. It is unusual for new features to be allowed in the release after the deadline. For this reason, additional justification must be obtained from a stakeholder outside of the SST, to ensure an objective review of the benefit to the product. 

What is the risk to the release schedule, quality, and the impact of diverting resources from other efforts? Will there be enough time to do the necessary large-scale, cross-function, regression, stress, or fault-insertion testing that may be required to verify this change? 

This is a one-file simple change.  The IPv6 functionality was just recently added to the Podman project and a community member found an issue while using the code and reported it here:  https://github.com/containers/podman/issues/13388 .  This was fixed upstream a few weeks ago and has been working without an issue there.

There is a low risk to this change and it would only be a problem for IPv6 usage in Podman has issues.  The fix is ready to go, we just need the green light.
Comment 4 Tom Sweeney 2022-03-21 21:50:21 UTC 
Forgot to mention fix is here:  GitHub PR: https://github.com/containers/podman/pull/13555
Comment 6 Tom Sweeney 2022-03-24 15:11:53 UTC 
PR with fix: https://github.com/containers/podman/pull/13555.  Setting to Post and assigning to Jindrich for any further BZ or packaging needs.
Comment 16 Alex Jia 2022-03-30 17:20:33 UTC 
This bug has been verified for podman-4.0.2-4.el9_0 both in rootless and root mode.

[root@kvm-07-guest12 ~]# rpm -q podman crun slirp4netns systemd kernel
podman-4.0.2-4.el9_0.x86_64
crun-1.4.2-1.el9.x86_64
slirp4netns-1.1.12-4.el9.x86_64
systemd-250-4.el9.x86_64
kernel-5.14.0-70.5.1.el9_0.x86_64

1. rootless mode
[test@kvm-07-guest12 ~]$ podman unshare cat /proc/self/uid_map 
         0       1000          1
         1     100000      65536
[test@kvm-07-guest12 ~]$ cat /sys/module/ipv6/parameters/disable
1
[test@kvm-07-guest12 ~]$ ip -6 addr
[test@kvm-07-guest12 ~]$ podman run --rm quay.io/everydayhero/hello_world
Trying to pull quay.io/everydayhero/hello_world:latest...
Getting image source signatures
Copying blob f65a559224b5 done  
Copying blob 74db925ddbf2 done  
Copying blob 6170e5154266 done  
Copying blob 8b4458a3484d done  
Copying blob 1c803ea1ef6b done  
Copying blob c4a954ffa4cc done  
Copying blob 183d53df4053 done  
Copying blob 9af34591e8aa done  
Copying blob 59c1ac66c217 done  
Copying blob 1e5ec2bf2d04 done  
Copying blob 0b70dc1a4e1b done  
Copying blob 4230dc29a428 done  
Copying blob 68bbac26d437 done  
Copying blob e00e5f0e300c done  
Copying blob 5a640e0d8518 done  
Copying blob a3ed95caeb02 done  
Copying blob a3ed95caeb02 skipped: already exists  
Copying blob ffe2ec60f029 done  
Copying blob 437bc7d28bc5 done  
Copying blob 434c776916fb done  
Copying blob a3ed95caeb02 done  
Copying blob 8eda663d1772 done  
Copying blob 244a04c2c844 done  
Copying blob 5cbefce284d9 done  
Copying blob 5bfc08cbe642 done  
Writing manifest to image destination
Storing signatures
Switch to inspect mode.

[test@kvm-07-guest12 ~]$ podman images
REPOSITORY                        TAG         IMAGE ID      CREATED      SIZE
quay.io/everydayhero/hello_world  latest      0b137705d246  6 years ago  939 MB


2. root mode + slirp4netns network backend

[root@kvm-07-guest12 ~]# podman run --network slirp4netns --rm quay.io/everydayhero/hello_world
Trying to pull quay.io/everydayhero/hello_world:latest...
Getting image source signatures
Copying blob 74db925ddbf2 done  
Copying blob c4a954ffa4cc done  
Copying blob 6170e5154266 done  
Copying blob f65a559224b5 done  
Copying blob 8b4458a3484d done  
Copying blob 1c803ea1ef6b done  
Copying blob 183d53df4053 done  
Copying blob 1e5ec2bf2d04 done  
Copying blob 9af34591e8aa done  
Copying blob 0b70dc1a4e1b done  
Copying blob 59c1ac66c217 done  
Copying blob e00e5f0e300c done  
Copying blob 4230dc29a428 done  
Copying blob 68bbac26d437 done  
Copying blob ffe2ec60f029 done  
Copying blob 5a640e0d8518 done  
Copying blob a3ed95caeb02 done  
Copying blob a3ed95caeb02 skipped: already exists  
Copying blob 434c776916fb done  
Copying blob 437bc7d28bc5 done  
Copying blob a3ed95caeb02 skipped: already exists  
Copying blob 244a04c2c844 done  
Copying blob 5bfc08cbe642 done  
Copying blob 8eda663d1772 done  
Copying blob 5cbefce284d9 done  
Writing manifest to image destination
Storing signatures
Switch to inspect mode.

[root@kvm-07-guest12 ~]# podman images
REPOSITORY                        TAG         IMAGE ID      CREATED      SIZE
quay.io/everydayhero/hello_world  latest      0b137705d246  6 years ago  939 MB
Comment 18 errata-xmlrpc 2022-05-17 12:42:09 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 (new packages: podman), 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-2022:2379
Comment 19 Red Hat Bugzilla 2023-09-15 01:53:02 UTC 
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 365 days