Requesting serial console output from azure instances to further debug.
The AWS jobs assume access to S3 storage without proxy use, we'll need to be able to assume the same access to Azure blob storage in these Azure tests as well.
(In reply to Scott Dodson from comment #20)
> The AWS jobs assume access to S3 storage without proxy use, we'll need to be
> able to assume the same access to Azure blob storage in these Azure tests as
Hello Scott, do you have a link in the docs or elsewhere that explains that assumption? Should it be included in that list: https://docs.openshift.com/container-platform/4.3/installing/install_config/configuring-firewall.html?
This test was done with the assumption that we wanted to be in a completely internet disconnected network and only allowing outgoing connections through the proxy. Client environments could have similar requirements.
Should an installation work with only the white list of the azure blob storage (*.blob.core.windows.net) + proxy?
I confirm that I was able to create a cluster with the proxy by adding a whitelist towards Azure public IPs.
DEBUG OpenShift Installer v4.3.1
DEBUG Built from commit 2055609f95b19322ee6cfdd0bea73399297c4a3e
Firewall rules added:
NSG with egress access enabled towards Azure Service Tag "AzureCloud" (https://www.microsoft.com/en-us/download/details.aspx?id=56519)
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.