Bug 1920205 - operator-registry e2e tests not working properly
Summary: operator-registry e2e tests not working properly
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: OLM
Version: 4.7
Hardware: Unspecified
OS: Unspecified
high
medium
Target Milestone: ---
: 4.7.0
Assignee: Daniel Sover
QA Contact: Jian Zhang
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-01-25 18:59 UTC by Daniel Sover
Modified: 2021-02-24 15:56 UTC (History)
0 users

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-02-24 15:55:53 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github operator-framework operator-registry pull 552 0 None open feat: use secure local registry for e2e tests 2021-01-25 18:59:57 UTC
Red Hat Product Errata RHSA-2020:5633 0 None None None 2021-02-24 15:56:25 UTC

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