TestOperatorProxyConfiguration and TestOperandProxyConfiguration are red on Azure. https://prow.svc.ci.openshift.org/view/gcs/origin-ci-test/pr-logs/pull/openshift_cluster-image-registry-operator/458/pull-ci-openshift-cluster-image-registry-operator-master-e2e-azure-operator/9 https://prow.svc.ci.openshift.org/view/gcs/origin-ci-test/pr-logs/pull/openshift_cluster-image-registry-operator/458/pull-ci-openshift-cluster-image-registry-operator-master-e2e-azure-operator/10 TestOperatorProxyConfiguration: condition.go:58: &errors.errorString{s:"condition StorageExists status should be \"Unknown\" but was True instead"} condition.go:58: &errors.errorString{s:"condition StorageExists reason should have been \"Unknown Error Occurred\" but was ContainerExists instead"} condition.go:58: &errors.errorString{s:"timed out waiting for the condition"} TestOperandProxyConfiguration: configuration_test.go:339: waiting for the operator to recreate the deployment... configuration_test.go:355: waiting for the operator to recreate the deployment... envvars.go:54: unable to find environment variable: wanted NO_PROXY envvars.go:54: unable to find environment variable: wanted HTTP_PROXY envvars.go:54: unable to find environment variable: wanted HTTPS_PROXY
This test has been passed and also I can start an Azure+proxy cluster with 4.5.0-0.nightly-2020-05-25-232952 successfully: https://deck-ci.apps.ci.l2s4.p1.openshiftapps.com/view/gs/origin-ci-test/pr-logs/pull/openshift_cluster-image-registry-operator/551/pull-ci-openshift-cluster-image-registry-operator-master-e2e-azure-operator/21
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. https://access.redhat.com/errata/RHBA-2020:2409