Bug 1844104 - Currently there is no Self Signed SSL cert support for Manila integration
Summary: Currently there is no Self Signed SSL cert support for Manila integration
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Installer
Version: 4.5
Hardware: Unspecified
OS: Unspecified
urgent
urgent
Target Milestone: ---
: 4.5.0
Assignee: Mike Fedosin
QA Contact: Wei Duan
URL:
Whiteboard:
Depends On: 1839226
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-06-04 15:51 UTC by OpenShift BugZilla Robot
Modified: 2020-07-13 17:43 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-07-13 17:43:18 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github openshift csi-driver-manila-operator pull 32 0 None closed [release-4.5] Bug 1844104: Implement self-signed certificates support for the driver and the operator 2020-07-29 11:11:02 UTC
Red Hat Product Errata RHBA-2020:2409 0 None None None 2020-07-13 17:43:38 UTC

Comment 3 Chris Janiszewski 2020-06-19 14:00:10 UTC 
this fix works for me!
Comment 4 Wei Duan 2020-06-30 11:18:48 UTC 
Verified pass.

[wduan@MINT config]$ oc get clusterversion
NAME      VERSION                             AVAILABLE   PROGRESSING   SINCE   STATUS
version   4.5.0-0.nightly-2020-06-26-215024   True        False         5m27s   Cluster version is 4.5.0-0.nightly-2020-06-26-215024

We using the osp16 cluster to install manila driver, no authentication error found.
Comment 5 errata-xmlrpc 2020-07-13 17:43:18 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, 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-2020:2409
Note You need to log in before you can comment on or make changes to this bug.