Bug 2173161
Summary: | ODF-console can not start when you disable IPv6 on Node with kernel parameter. | ||
---|---|---|---|
Product: | [Red Hat Storage] Red Hat OpenShift Data Foundation | Reporter: | Raimund Sacherer <rsachere> |
Component: | odf-operator | Assignee: | Sanjal Katiyar <skatiyar> |
Status: | CLOSED ERRATA | QA Contact: | Shay Rozen <srozen> |
Severity: | high | Docs Contact: | |
Priority: | unspecified | ||
Version: | unspecified | CC: | asriram, jomarque, kbg, muagarwa, nberry, ocs-bugs, odf-bz-bot, rlepaksh, skatiyar, sostapov, srozen, tnielsen |
Target Milestone: | --- | ||
Target Release: | ODF 4.13.0 | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: |
Previously, when IPv6 was disabled at node's kernel level, `IPv6 listen` directive of `nginx` configuration for the `odf-console` pod gave an error. As a result, OpenShift Data Foundation was stuck with `odf-console` not available and `odf-console` is in `CrashLoopBackOff` errors.
With this fix, all the `nginx` configurations are added through the ConfigMap created by the `odf-operator`. You need to perform the following steps to overcome the issue:
1. Go to ConfigMap: "odf-console-nginx-conf".
2. Comment out the followig line as shown:
----
# listen [::]:9001 ssl;
----
3. Restart the `odf-console` pod by deleting it.
4. Refresh the user interface.
|
Story Points: | --- |
Clone Of: | Environment: | ||
Last Closed: | 2023-06-21 15:24:01 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: | 2154341 |
Description
Raimund Sacherer
2023-02-24 11:00:26 UTC
As far as I know, "::" is the IPv6 unspecified address, and should not be used to reference any specific host. But in any case, it is a an IPv6 address, so if you trying to disable IPv6 what is the expectation here when you then use an IPv6 address? I guess I do not understand this issue. The behavior seems correct to me. (In reply to Scott Ostapovicz from comment #3) > As far as I know, "::" is the IPv6 unspecified address, and should not be > used to reference any specific host. But in any case, it is a an IPv6 > address, so if you trying to disable IPv6 what is the expectation here when > you then use an IPv6 address? I guess I do not understand this issue. The > behavior seems correct to me. Hi Scott, The issue is that CU for internal requirements or compliance want to disable IPV6 on all hosts on their system. Doing this breaks the odf-console, as soon as you deactivate IPV6 on the host via kernel parameter, odf-console does not start anymore. The problem seems to be the default configuration of nginx in odf-console. It seems to expect that IPV6 is present, if not, nginx does not start. Best regards Raimund So an address somewhere in the stack is still an IPv6 address even though the script nominally disables IPv6. Perhaps you can suss this out @tnielsen ? *** Bug 2139785 has been marked as a duplicate of this bug. *** Check on 4.13.0-205. Changed the configmap as above. Restarted odf console. Still in CrashLoopBackOff. Moving to assigned. Hi Shay, I have added a detailed recording https://bugzilla.redhat.com/show_bug.cgi?id=2173161#c19 on how to test this (basically video version of https://bugzilla.redhat.com/show_bug.cgi?id=2173161#c11) Feel free to connect with me offline, if there is still any issue you might be facing. Thanks. Hi Sanjal. I've commented the wrong line. Looks like it is working now. I saw that no doc update for this BZ. Who is responsible to create KCS for this hack. Added the doc text, also adding need_info on reporter for getting help with KCS doc. Sanjal/Kusum Doc text should be a bug fix and not a known issue as we have fixed something here. If there are steps which some one needs to follow while disabling IPv6 then these steps should be added to the deployment guide or the guide where we are providing enabling/disabling steps for IPv6 Yeah, my intension for adding it as "Known Issue" is exactly as you mentioned: Earlier there was no workaround to fix this issue (other than enabling IPv6 again on the nodes). As per this BZ, we added the functionality so that users can now use a workaround manually. I will let doc team decide the correct place for this issue and the correct "Doc Type" as well. Thanks. Thanks Mudit/Anjana/Kusuma... updated... 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 (Red Hat OpenShift Data Foundation 4.13.0 enhancement 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/RHBA-2023:3742 |