Bug 1817119

Summary: [ci] Problems with TestOperatorProxyConfiguration and TestOperandProxyConfiguration on Azure
Product: OpenShift Container Platform Reporter: Oleg Bulatov <obulatov>
Component: Image RegistryAssignee: Ricardo Maraschini <rmarasch>
Status: CLOSED ERRATA QA Contact: Wenjing Zheng <wzheng>
Severity: urgent Docs Contact:
Priority: unspecified    
Version: 4.5CC: adam.kaplan, aos-bugs, rmarasch
Target Milestone: ---   
Target Release: 4.5.0   
Hardware: Unspecified   
OS: Unspecified   
Fixed In Version: Doc Type: No Doc Update
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-07-13 17:23:43 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Oleg Bulatov 2020-03-25 15:42:34 UTC
TestOperatorProxyConfiguration and TestOperandProxyConfiguration are red on Azure.


    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"}

    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

Comment 6 Wenjing Zheng 2020-05-26 07:21:22 UTC
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:

Comment 8 errata-xmlrpc 2020-07-13 17:23:43 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, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.