Bug 1922127 - [build-watch] e2e-aws-proxy test consistently fails
Summary: [build-watch] e2e-aws-proxy test consistently fails
Keywords:
Status: CLOSED DUPLICATE of bug 1920027
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Test Infrastructure
Version: 4.7
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: ---
Assignee: Steve Kuznetsov
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-01-29 10:08 UTC by Kevin Pouget
Modified: 2021-01-29 22:20 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Overall
Last Closed: 2021-01-29 22:20:20 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

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 ***
Note You need to log in before you can comment on or make changes to this bug.