Bug 1834446

Summary: Update the doc link for Health Checks for 4.5 release
Product: OpenShift Container Platform Reporter: Vikram Raj <viraj>
Component: Dev ConsoleAssignee: Vikram Raj <viraj>
Status: CLOSED ERRATA QA Contact: Gajanan More <gamore>
Severity: low Docs Contact:
Priority: high    
Version: 4.5CC: aos-bugs, nmukherj
Target Milestone: ---   
Target Release: 4.5.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: No Doc Update
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-07-13 17:37:35 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:
Attachments:
Description Flags
docs link none

Description Vikram Raj 2020-05-11 17:51:38 UTC 
Description of problem:
Add/Edit Health Checks page has to Learn More link which redirects the user to 3.11 openshift Health Checks doc page. But this link should redirect the user to the latest openshift Health Checks doc page. 


How reproducible:


Steps to Reproduce:
1. import an application.
2. navigate to topology page.
3. right click on node and select the Add/Edit Health checks option.
4. On health checks page you will see the learn more link redirect you to 3.11 openshift doc.

Actual results:
Health checks learn more link redirect to 3.11 openshift doc.

Expected results:
Health checks learn more link should redirect to latest openshift doc.
Comment 4 Gajanan More 2020-05-15 10:28:19 UTC 
Created attachment 1688885 [details]
docs link
Comment 5 Gajanan More 2020-05-15 10:29:17 UTC 
As it need to validate on 4.5 and the 4.5 docs are not yet released, we are getting some message and not 404.
The validation done on:
Build: 4.5.0-0.ci-2020-05-14-224329
Browser: Google Chrome Version 81.0.4044.129
Please have a look at the screenshot shared
Marking this as verified.
Comment 6 errata-xmlrpc 2020-07-13 17:37:35 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:2409