Bug 1799255

Summary: [IPI baremetal]: Add an option to disable CA verification for Redfish
Product: OpenShift Container Platform Reporter: Stephen Benjamin <stbenjam>
Component: Cloud ComputeAssignee: Amit Ugol <augol>
Cloud Compute sub component: BareMetal Provider QA Contact: Amit Ugol <augol>
Status: CLOSED WONTFIX Docs Contact:
Severity: unspecified    
Priority: unspecified CC: augol, beth.white, stbenjam, yroblamo
Version: 4.4   
Target Milestone: ---   
Target Release: 4.3.z   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: 1799219 Environment:
Last Closed: 2020-05-12 16:49:12 UTC Type: ---
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: 1799219, 1799927, 1801228    
Bug Blocks:    

Description Stephen Benjamin 2020-02-06 16:21:12 UTC 
+++ This bug was initially created as a clone of Bug #1799219 +++

When provisioning baremetal IPI using Redfish with virtual media or PXE, the default is for Ironic to verify the CA certificates, however it is typical for the CA certs to be self-signed. We should expose the option for disabling certificate verification so in lab or other environments where they have not replaced BMC certs with trusted ones, they can still test Redfish deployments.

--- Additional comment from Stephen Benjamin on 2020-02-06 16:15:26 UTC ---

Upstream PR: https://github.com/metal3-io/baremetal-operator/pull/396

Once merged, we need to cherry-pick it to openshift/baremetal-operator
Comment 1 Beth White 2020-05-12 16:49:12 UTC 
No longer backporting to 4.3