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

Bug 1791182

Summary:	Add stable-4.3, fast-4.3, and candidate-4.3 channels to UI in 4.2.z
Product:	OpenShift Container Platform	Reporter:	Yadan Pei <yapei>
Component:	Management Console	Assignee:	Jakub Hadvig <jhadvig>
Status:	CLOSED ERRATA	QA Contact:	Yadan Pei <yapei>
Severity:	unspecified	Docs Contact:
Priority:	high
Version:	4.2.z	CC:	aos-bugs, jforrest, jhadvig, jokerman, vlaad, yapei
Target Milestone:	---
Target Release:	4.2.z
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:	2020-01-22 10:46:40 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 Yadan Pei 2020-01-15 07:14:34 UTC

Description of problem:
Since OCP 4.3 is going to be released soon, we need to add *-4.3 channels so that OCP 4.2 customer can upgrade to OCP 4.3 from UI.

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

How reproducible:
Always

Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 1 Yadan Pei 2020-01-15 07:15:41 UTC

Channels should be added are: stable-4.3, fast-4.3, candidate-4.3 Let me know if I'm wrong

Comment 4 Yadan Pei 2020-01-19 03:25:27 UTC

1. Setup a cluster with quay.io/openshift-release-dev/ocp-release:4.2.16-x86_64
2. Patch upstream to make https://openshift-release.svc.ci.openshift.org/ as update server
$ oc patch clusterversion/version --patch '{"spec":{"upstream":"https://openshift-release.svc.ci.openshift.org/graph"}}' --type=merge
3. admin user login to console, check upgrade channel in Adminitration -> Cluster Settings -> Channel, we can see stable-4.3, fast-4.3, candidate-4.3 in the list


Verified on 4.2.16

Comment 6 errata-xmlrpc 2020-01-22 10:46:40 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, 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/RHBA-2020:0107