Bug 1920205

Summary:	operator-registry e2e tests not working properly
Product:	OpenShift Container Platform	Reporter:	Daniel Sover <dsover>
Component:	OLM	Assignee:	Daniel Sover <dsover>
OLM sub component:	OLM	QA Contact:	Jian Zhang <jiazha>
Status:	CLOSED ERRATA	Docs Contact:
Severity:	medium
Priority:	high
Version:	4.7
Target Milestone:	---
Target Release:	4.7.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2021-02-24 15:55:53 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:

Comment 2 Jian Zhang 2021-01-26 03:18:28 UTC

The local registry works well. Only PIT https://github.com/operator-framework/operator-registry/blob/master/test/e2e/opm_test.go#L365 in Pending, others passed, no skipped. Details: https://github.com/operator-framework/operator-registry/runs/1764453692?check_suite_focus=true 
LGTM, verify it.

Comment 3 Jian Zhang 2021-01-26 03:31:16 UTC

Hi Daniel,

One question, I didn't find any new builds in https://travis-ci.com/github/operator-framework/operator-registry/builds, is it deprecated? Thanks!

Comment 7 errata-xmlrpc 2021-02-24 15:55:53 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 (Moderate: OpenShift Container Platform 4.7.0 security, bug fix, and enhancement update), 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/RHSA-2020:5633