Bug 2035318 - Upgrade management workflow needs to allow custom upgrade graph path for disconnected env
Summary: Upgrade management workflow needs to allow custom upgrade graph path for disc...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Telco Edge
Version: 4.10
Hardware: Unspecified
OS: Unspecified
unspecified
urgent
Target Milestone: ---
: 4.10.0
Assignee: Nishant Parekh
QA Contact: yliu1
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-12-23 15:06 UTC by yliu1
Modified: 2022-03-10 16:36 UTC (History)
3 users (show)

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

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github openshift-kni cnf-features-deploy pull 883 0 None open bug 2035318: added upstream field in the clusterVerion CR 2021-12-23 15:28:00 UTC
Red Hat Product Errata RHSA-2022:0056 0 None None None 2022-03-10 16:36:34 UTC

Description yliu1 2021-12-23 15:06:54 UTC 
Description of problem:
In disconnected env, we need to use a custom upgrade graph image to build the upgrade path, because the default will try to build from a public registry that is not accessible from disconnected env.


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

How reproducible:
100%

Steps to Reproduce:
1. try to specify "upstream" variable in cluster version config before upgrade
2.
3.

Actual results:
User can specify upstream via PGT

Expected results:
Currently cannot specify it

Additional info:
Comment 4 yliu1 2022-02-04 15:01:44 UTC 
Verified on 4.10.fc.1 with latest TALO.
Comment 6 errata-xmlrpc 2022-03-10 16:36:23 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.