Bug 2139785 - ODF 4.12 installation is stuck with "odf-console not available" [NEEDINFO]
Summary: ODF 4.12 installation is stuck with "odf-console not available"
Keywords:
Status: CLOSED DUPLICATE of bug 2173161
Alias: None
Product: Red Hat OpenShift Data Foundation
Classification: Red Hat Storage
Component: odf-operator
Version: 4.12
Hardware: Unspecified
OS: Unspecified
medium
high
Target Milestone: ---
: ---
Assignee: Sanjal Katiyar
QA Contact: Elad
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-11-03 12:20 UTC by Rahul Lepakshi
Modified: 2023-08-09 17:00 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2023-03-30 12:22:16 UTC
Embargoed:
skatiyar: needinfo? (rlepaksh)


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github red-hat-storage odf-operator pull 305 0 None Merged add nginx configurations for the odf-console 2023-03-29 13:57:19 UTC
Github red-hat-storage odf-operator pull 306 0 None Merged Bug 2139785:[release-4.13] add nginx configurations for the odf-console 2023-03-30 12:07:32 UTC

Comment 2 Nitin Goyal 2022-11-03 12:31:29 UTC
Moving it to the management console

Comment 4 Sanjal Katiyar 2022-11-04 07:20:55 UTC
To point out few things:

1) Please attach must gathers for the issues which are not reproducible always or we are not sure how to reproduce them again (as mentioned in the description).

2) Priority of the issue is wrong, I can understand we might be facing this issue on the cluster, but it does not mean that priority can be urgent (unless we need to stop all our current work and just look into fixing this bug).
Also, you can always create a new cluster and resume your work, I don't think nodes reboot so often (All other 4.12 BZs are still getting VERIFIED everyday).

3) I can see error message "secret "odf-console-serving-cert" not found" as well, it could be one of the reasons why "odf-console" pod is not running successfully. I doubt node reboot can delete a Secret from etcd. So, it might have gotten deleted by mistake ??

Anyway I will investigate further into the issue.


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