-
Bug
-
Resolution: Done
-
Minor
-
None
-
4.13.z, 4.12.z, 4.11.z, 4.14.z
-
No
-
2
-
OSDOCS Sprint 255, OSDOCS Sprint 256, OSDOCS Sprint 257, OSDOCS Sprint 258, OSDOCS Sprint 259, OSDOCS Sprint 260, OSDOCS Sprint 261
-
7
-
False
-
Description of problem:
The instructions in the documentation for each OpenShift version contain the same section for "Obtaining the OpenShift installer". This page directs the reader to "Access the Infrastructure Provider page on the OpenShift Cluster Manager site" with a link to https://console.redhat.com/openshift/install. From the linked page, the reader can only download the current latest version of the installer, regardless of which version of the official documentation they originated from. Later in the page of the official documents, instructions for downloading the OpenShift CLI client direct the reader to https://access.redhat.com/downloads/content/290 instead, which while loads up the current latest release by default, it also includes a dropdown box to select a specific previous release. In addition to the client, the version specific page also provides the ability to download other OpenShift tools, including the installer, for the specified version. The URL can also be customised to show a specific version when first loaded, ie: https://access.redhat.com/downloads/content/290/ver=4.12/rhel---8/4.12.47/x86_64/product-software
Version-Release number of selected component (if applicable):
OpenShift 4.x
How reproducible:
Easy
Steps to Reproduce:
1. Go to the official documentation page on installing an OpenShift cluster for a version prior to the current one 2. Navigate to the "Obtaining the OpenShift installer" section 3. Follow the link provided to download the `openshift-install` tool 4. Install the cluster as per the documentation 5. Observe that the cluster version is the latest release, and not the minor version you assumed would be deployed based on the documentation you were following.
Actual results:
The deployed cluster is the latest release version
Expected results:
The deployed cluster major.minor version should match that of the documentation being followed.
Additional info:
An RFE for the console (CONSOLE-3898) was opened earlier to request the ability to select versions other than the latest. This ticket is being created as a complementary or alternative fix for the issue