Bug 1929920

+++ This bug was initially created as a clone of Bug #1856803 +++

Description of problem:

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


How reproducible:


Steps to Reproduce:
1. Install operator with the 'operatorframework.io/cluster-monitoring: true' label e.g. https://github.com/eclipse/che-operator/pull/339
2. Navigate to the `cluster monitoring documentation link` 
3. ERROR - 404 docs not found

Actual results:

404 


Expected results:

Link point to the valid documentation


Additional info:

See the gif attached

--- Additional comment from Samuel Padgett on 2020-07-14 13:39:16 UTC ---

Note that we don't show the warning for Red Hat operators, so this only affects non-Red Hat operators.

--- Additional comment from XiaochuanWang on 2020-07-15 06:31:41 UTC ---

This links to https://docs.openshift.com/container-platform/<version>/monitoring/cluster_monitoring/configuring-the-monitoring-stack.html#maintenance-and-support_configuring-monitoring and the page existed.
Verified on 4.6.0-0.nightly-2020-07-14-224428

--- Additional comment from errata-xmlrpc on 2020-10-27 16:14:36 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 (OpenShift Container Platform 4.6 GA Images), 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:4196

--- Additional comment from Ilya Buziuk on 2020-11-17 11:41:14 UTC ---

The issue is still reproducible against the latest OCP 4.6 - docs point to the https://docs.openshift.com/container-platform/4.6/monitoring/cluster_monitoring/configuring-the-monitoring-stack.html#maintenance-and-support_configuring-monitoring which return 404

--- Additional comment from Eric Paris on 2020-11-17 12:00:22 UTC ---

Unsetting the target release because this bug targets a .0 release which has already shipped. For example it may target 4.2.0. Since 4.2.0 has already shipped such bugs may instead wish to target a future 4.2.z.

--- Additional comment from Samuel Padgett on 2020-11-17 13:34:44 UTC ---

Looks like we have an extra `cluster_monitoring` in the path.

--- Additional comment from Samuel Padgett on 2020-12-04 19:29:49 UTC ---

Status: PR open with the corrected link.

--- Additional comment from OpenShift Automated Release Tooling on 2020-12-04 22:24:40 UTC ---

Elliott changed bug status from MODIFIED to ON_QA.

--- Additional comment from Yadan Pei on 2020-12-09 09:29:35 UTC ---

1. Install operator with the 'operatorframework.io/cluster-monitoring: true' label e.g Metering
2. Navigate to the `cluster monitoring documentation link`, it points to https://docs.openshift.com/container-platform/4.7/monitoring/configuring-the-monitoring-stack.html#maintenance-and-support_configuring-monitoring, when I replace 4.7 with 4.6, docs are loaded correctly thus the link is correct 


Moving to VERIFIED and this is checked against 4.7.0-0.nightly-2020-12-08-141245