Bug 1846922 - "downloads" pod does not work on the node which is disabled IPv6
Summary: "downloads" pod does not work on the node which is disabled IPv6
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Management Console
Version: 4.4
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
: 4.6.0
Assignee: Daein Park
QA Contact: Yadan Pei
: 1795325 (view as bug list)
Depends On:
Blocks: 1847523
TreeView+ depends on / blocked
Reported: 2020-06-15 08:53 UTC by Daein Park
Modified: 2020-10-27 16:07 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Cause: when IPv6 is disabled, "downloads" pod socket cannot bind. Consequence: "downloads" pod crashed. Fix: If IPv6 is not enabled, IPv4 will use for the socket. Result: "downloads" pod can work regardless of enabling IPv4 and IPv6.
Clone Of:
Last Closed: 2020-10-27 16:07:13 UTC
Target Upstream Version:

Attachments (Terms of Use)

System ID Private Priority Status Summary Last Updated
Github openshift console-operator pull 438 0 None closed Bug 1846922: "downloads" pod does not work on the node which is disabled IPv6 2020-12-11 21:18:43 UTC
Red Hat Product Errata RHBA-2020:4196 0 None None None 2020-10-27 16:07:38 UTC

Description Daein Park 2020-06-15 08:53:38 UTC
Description of problem:

When the "downloads" pod scheduled on the worker node which is disabled IPv6, the pods does not work with the following log messages.

$ oc get pod -n openshift-console -o wide
NAME                             READY   STATUS             RESTARTS   AGE     IP            NODE                      NOMINATED NODE   READINESS GATES
pod/console-1111111111-aaaaa     1/1     Running            0          8d    node02.ocp4.example.com   <none>           <none>
pod/console-1111111111-bbbbb     1/1     Running            0          8d   node03.ocp4.example.com   <none>           <none>
pod/downloads-aaaaaaaaaa-xxxxx   0/1     CrashLoopBackOff   5          1m54s   node03.ocp4.example.com   <none>           <none>
pod/downloads-aaaaaaaaaa-yyyyy   0/1     CrashLoopBackOff   5          3m14s   node02.ocp4.example.com   <none>           <none>

$ oc logs pod/downloads-aaaaaaaaaa-xxxxx --container=download-server --timestamps
2020-06-11T00:47:48.113162338Z serving from /tmp/tmpC8Eoy8
2020-06-11T00:47:48.11326402Z Traceback (most recent call last):
2020-06-11T00:47:48.11326402Z   File "/tmp/serve.py", line 59, in <module>
2020-06-11T00:47:48.11326402Z     sock = socket.socket(socket.AF_INET6, socket.SOCK_STREAM)
2020-06-11T00:47:48.11326402Z   File "/usr/lib64/python2.7/socket.py", line 187, in __init__
2020-06-11T00:47:48.11326402Z     _sock = _realsocket(family, type, proto)
2020-06-11T00:47:48.11326402Z socket.error: [Errno 97] Address family not supported by protocol

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

OCP 4.4.4

How reproducible:

You can always reproduce this issue after the worker node is disabled IPv6 for running the "downloads" pods.

Steps to Reproduce:

Actual results:

"downloads" pod does not work when the node is disabled IPv6.

Expected results:

"downloads" pod work well regardless of the IPv6 enabled or disabled.

Additional info:

Comment 4 Samuel Padgett 2020-06-15 17:33:44 UTC
*** Bug 1795325 has been marked as a duplicate of this bug. ***

Comment 7 Yadan Pei 2020-07-27 05:41:40 UTC

As I understand that we need following steps to verify this bug

1) Add RHEL worker nodes to the cluster(IPv4 cluster is ok)
2) Disable IPv6 on the RHEL worker node
3) Re-schedule downloads pods to the new added RHEL worker node to see if downloads pods are running

Is it correct? Can you also please give some guidance about how to disable IPv6 for a RHEL worker node?

Comment 8 Daein Park 2020-07-28 01:49:41 UTC
@Yadan hi,

> Is it correct? Can you also please give some guidance about how to disable IPv6 for a RHEL worker node?

You need not to add new worker. Just add "ipv6.disable=1" to kernel parameter when existing any worker node reboot, then you can disable IPv6 on the node.

Comment 11 errata-xmlrpc 2020-10-27 16:07:13 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 (OpenShift Container Platform 4.6 GA Images), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.


Note You need to log in before you can comment on or make changes to this bug.