Bug 1728555 - Download oc link should point to the version consistent with cluster version
Summary: Download oc link should point to the version consistent with cluster version
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Management Console
Version: 4.2.0
Hardware: Unspecified
OS: Unspecified
unspecified
low
Target Milestone: ---
: 4.2.0
Assignee: Samuel Padgett
QA Contact: Yadan Pei
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-07-10 07:07 UTC by shahan
Modified: 2019-10-16 06:33 UTC (History)
4 users (show)

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

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github openshift console pull 1978 0 None None None 2019-07-10 12:58:45 UTC
Red Hat Product Errata RHBA-2019:2922 0 None None None 2019-10-16 06:33:36 UTC

Description shahan 2019-07-10 07:07:59 UTC 
Description of problem:
Download oc link should point to the version consistent with cluster version

Version-Release number of selected component (if applicable):
4.2.0-0.nightly-2019-07-09-222901

How reproducible:
Always

Steps to Reproduce:
1. Click help dropdown-> Command Line Tools ->click download oc

2.
3.

Actual results:
It will direct to oc version 4.1 /pub/openshift-v4/clients/oc/4.1

Expected results:
Should be /pub/openshift-v4/clients/oc/4.2

Additional info:
Comment 1 Samuel Padgett 2019-07-10 12:59:04 UTC 
https://github.com/openshift/console/pull/1978
Comment 3 Yadan Pei 2019-07-12 09:15:20 UTC 
Now the download oc links to https://mirror.openshift.com/pub/openshift-v4/clients/oc/4.2/

Verified on 4.2.0-0.nightly-2019-07-11-114243
Comment 4 errata-xmlrpc 2019-10-16 06:33: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, 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-2019:2922
Note You need to log in before you can comment on or make changes to this bug.