Bug 2012173

Summary:	Azure Stack Hub does not handle additionalTrustBundle
Product:	OpenShift Container Platform	Reporter:	Patrick Dillon <padillon>
Component:	Installer	Assignee:	Patrick Dillon <padillon>
Installer sub component:	openshift-installer	QA Contact:	Mike Gahagan <mgahagan>
Status:	CLOSED ERRATA	Docs Contact:
Severity:	high
Priority:	high	CC:	awestbro, mgahagan, mstaeble, tsze
Version:	4.10	Keywords:	TestBlocker
Target Milestone:	---
Target Release:	4.9.z
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:	2010921	Environment:
Last Closed:	2022-02-14 12:00:47 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:	2010921
Bug Blocks:

Description Patrick Dillon 2021-10-08 13:44:49 UTC

+++ This bug was initially created as a clone of Bug #2010921 +++

Platform: Azure Stack Hub
IPI & UPI

Azure Stack Hub does not add the additionalTrustBundle to the cloud provider config or the bootstrap ignition stub, so this does not allow for installation in environments that need certificates signed by internal CAs. 

Our new environment Azure Stack environment, WWT, uses certificates signed by internal CAs so we see that installations fail there.

First, installations fail when trying to pull ignition from the storage blob. This can be handled in the UPI instructions.

Second, installations fail when operators do not have the trust bundle. 

The installer needs to place the additional trust bundle in the cloud provider config, then we need to follow up with operators to make sure they are using it. The operators we know we need to follow up with are:
CCM (cloud team and machine-api for 4.10 only)
image registry
storage
network edge for ingress controller

--- Additional comment from Matthew Staebler on 2021-10-05 17:45:32 UTC ---

We are looking for some alternative workarounds for this and reaching out to Microsoft to see the impact to potential customers if there is no workaround.

Comment 3 Patrick Dillon 2022-02-07 20:24:52 UTC

This BZ represents changes to the docs in https://github.com/openshift/installer/pull/5573

Comment 4 Mike Gahagan 2022-02-07 20:39:46 UTC

We have had numerous successful installs in an ASH environment that requires additional trust bundle so this one can be verified.

Comment 8 errata-xmlrpc 2022-02-14 12:00:47 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 (OpenShift Container Platform 4.9.21 bug fix update), 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-2022:0488