Bug 1801228

Summary: [IPI baremetal]: MAO Add an option to disable CA verification for Redfish
Product: OpenShift Container Platform Reporter: Steven Hardy <shardy>
Component: Cloud ComputeAssignee: Steven Hardy <shardy>
Cloud Compute sub component: BareMetal Provider QA Contact: Amit Ugol <augol>
Status: CLOSED ERRATA Docs Contact:
Severity: unspecified    
Priority: unspecified CC: augol, rbartal, shardy, stbenjam, vlaad, yroblamo
Version: 4.4   
Target Milestone: ---   
Target Release: 4.4.0   
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-15 16:07:38 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    
Bug Blocks: 1799255, 1799927    

Description Steven Hardy 2020-02-10 13:27:05 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.

This is to track updating the MAO copy of the BMH CRD to match https://github.com/openshift/baremetal-operator/pull/51

https://github.com/openshift/machine-api-operator/blob/master/install/0000_30_machine-api-operator_08_baremetalhost.crd.yaml

Without this fix deployment of workers with baremetal IPI and Redfish will not work.