Bug 2012173 - Azure Stack Hub does not handle additionalTrustBundle
Summary: Azure Stack Hub does not handle additionalTrustBundle
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Installer
Version: 4.10
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
: 4.9.z
Assignee: Patrick Dillon
QA Contact: Mike Gahagan
Depends On: 2010921
TreeView+ depends on / blocked
Reported: 2021-10-08 13:44 UTC by Patrick Dillon
Modified: 2022-02-14 12:01 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 2010921
Last Closed: 2022-02-14 12:00:47 UTC
Target Upstream Version:

Attachments (Terms of Use)

System ID Private Priority Status Summary Last Updated
Github openshift installer pull 5573 0 None Merged Bug 2012173: Azure Stack: Add UPI Instructions for internal CA 2022-02-07 20:23:06 UTC
Red Hat Product Errata RHBA-2022:0488 0 None None None 2022-02-14 12:01:00 UTC

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

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
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.


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