Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1922127

Summary: [build-watch] e2e-aws-proxy test consistently fails
Product: OpenShift Container Platform Reporter: Kevin Pouget <kpouget>
Component: Test InfrastructureAssignee: Steve Kuznetsov <skuznets>
Status: CLOSED DUPLICATE QA Contact:
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 4.7CC: wking
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Overall
Last Closed: 2021-01-29 22:20:20 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:
Embargoed:

Description Kevin Pouget 2021-01-29 10:08:10 UTC 
Test "redhat-openshift-ocp-release-4.7-informing" is consistently failing in the CI since the beginning of the week: (2020-01-22)

https://testgrid.k8s.io/redhat-openshift-ocp-release-4.7-informing#periodic-ci-openshift-release-master-ocp-4.7-e2e-aws-proxy

It seems to be always linked with this failure:

> [must-gather      ] OUT Get "https://api.ci-op-ytjycsc0-2659c.origin-ci-int-aws.dev.rhcloud.com:6443/apis/image.openshift.io/v1/namespaces/openshift/imagestreams/must-gather": dial tcp 54.215.8.18:6443: connect: connection refused
> [must-gather      ] OUT 
> [must-gather      ] OUT Using must-gather plug-in image: registry.redhat.io/openshift4/ose-must-gather:latest
> The connection to the server api.ci-op-ytjycsc0-2659c.origin-ci-int-aws.dev.rhcloud.com:6443 was refused - did you specify the right host or port?
Comment 1 W. Trevor King 2021-01-29 22:20:20 UTC 

*** This bug has been marked as a duplicate of bug 1920027 ***