Bug 2124642 - [RFE][GSS] Add support to disable SSL check by Noobaa [NEEDINFO]
Summary: [RFE][GSS] Add support to disable SSL check by Noobaa
Keywords:
Status: CLOSED DUPLICATE of bug 2121104
Alias: None
Product: Red Hat OpenShift Data Foundation
Classification: Red Hat Storage
Component: Multi-Cloud Object Gateway
Version: 4.10
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: ---
: ---
Assignee: Nimrod Becker
QA Contact: krishnaram Karthick
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-09-06 17:05 UTC by Sonal
Modified: 2023-08-09 16:49 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-11-15 08:04:32 UTC
Embargoed:
nbecker: needinfo? (sarora)
nbecker: needinfo? (sarora)


Attachments (Terms of Use)

Description Sonal 2022-09-06 17:05:06 UTC
Description of problem (please be detailed as possible and provide log
snippests):

Noobaa does not acceept SSL certificates, configured in Backingstore, causing backingstore to be in creating/pending state.

Version of all relevant components (if applicable):

All supported versions

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

Yes, as backingstore could not be in Ready state, obc can't be created.

Is there any workaround available to the best of your knowledge?

Yes, setting variable 'NODE_TLS_REJECT_UNAUTHORIZED' in noobaa-core and noobaa-endpoint resolved the issue

# oc edit sts noobaa-core
# oc edit deployment noobaa-endpoint

~~~
env:

  name: NODE_TLS_REJECT_UNAUTHORIZED       
  value: "0"
~~~



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

Can this issue reproducible?
Yes



Actual results:
Backingstore stay in creating/pending state as noobaa-core fail on SSL check


Expected results:
noobaa should be configured to acceept SSL certification.


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