Bug 2269032 - [GSS][ODF 4.12]Noobaa endpoint self signed certificate issue
Summary: [GSS][ODF 4.12]Noobaa endpoint self signed certificate issue
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat OpenShift Data Foundation
Classification: Red Hat Storage
Component: Multi-Cloud Object Gateway
Version: 4.12
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: ---
Assignee: Nimrod Becker
QA Contact: krishnaram Karthick
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2024-03-11 16:01 UTC by Rafrojas
Modified: 2024-04-22 10:42 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2024-04-10 13:26:26 UTC
Embargoed:


Attachments (Terms of Use)

Description Rafrojas 2024-03-11 16:01:36 UTC
Description of problem (please be detailed as possible and provide log
snippests):
It happend on TEST a couple of weeks ago and now we encounter this on ACC as well. A  restart from the pod: nooba-endpoint fixes the issue. But if we have this on PRD we have an outage. 

Version of all relevant components (if applicable):
OCS Version is : 4.12.10-rhodf

Does this issue impact your ability to continue to work with the product
(please explain in detail what is the user impact)?

Yes, connection refused on noobaa-endpoint

Is there any workaround available to the best of your knowledge?
Restart the noobaa-endpoint pod

Rate from 1 - 5 the complexity of the scenario you performed that caused this
bug (1 - very simple, 5 - very complex)?


Can this issue reproducible?
It happened on 2 environments PRE/TEST now we need to change on PROD and need to fix the issue

Can this issue reproduce from the UI?


If this is a regression, please provide more details to justify this:


Steps to Reproduce:
1.
2.
3.


Actual results:


Expected results:


Additional info:

Comment 6 Nimrod Becker 2024-03-12 10:12:38 UTC
Looks very similar to https://bugzilla.redhat.com/show_bug.cgi?id=2268412


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