Bug 2019129 - SRO in operator hub points to wrong repo for README
Summary: SRO in operator hub points to wrong repo for README
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Special Resource Operator
Version: 4.10
Hardware: Unspecified
OS: Unspecified
medium
high
Target Milestone: ---
: 4.10.0
Assignee: Brett Thurber
QA Contact: liqcui
URL:
Whiteboard:
Depends On:
Blocks: 2022488
TreeView+ depends on / blocked
 
Reported: 2021-11-01 16:37 UTC by Brett Thurber
Modified: 2022-03-10 16:24 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-03-10 16:23:41 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2022:0056 0 None None None 2022-03-10 16:24:03 UTC

Description Brett Thurber 2021-11-01 16:37:26 UTC 
Description of problem:
When installing the SRO operator from operator hub, the README repo link points to the incorrect repo.

Current: https://github.com/openshift-psap/special-resource-operator

Proposed: https://github.com/openshift/special-resource-operator

Version-Release number of selected component (if applicable):


How reproducible:
Every time

Steps to Reproduce:
1. In the OCP console, deploy SRO from Operator Hub.
2.
3.

Actual results:
Incorrect repo link for README

Expected results:
Correct repo link for README

Additional info:
Comment 1 Brett Thurber 2021-11-08 15:29:27 UTC 
PR for issue:  https://github.com/openshift/special-resource-operator/pull/67
Comment 2 Brett Thurber 2021-11-11 19:15:31 UTC 
Updated PR:  https://github.com/openshift/special-resource-operator/pull/70
Comment 5 errata-xmlrpc 2022-03-10 16:23:41 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.10.3 security 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-2022:0056
Note You need to log in before you can comment on or make changes to this bug.