Bug 1692227
| Summary: | wrong doc link on networkpolicy page | |||
|---|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | shahan <hasha> | |
| Component: | Management Console | Assignee: | Zac Herman <zherman> | |
| Status: | CLOSED ERRATA | QA Contact: | Yadan Pei <yapei> | |
| Severity: | low | Docs Contact: | ||
| Priority: | unspecified | |||
| Version: | 4.1.0 | CC: | aos-bugs, jokerman, mmccomas, spadgett, zherman | |
| Target Milestone: | --- | |||
| Target Release: | 4.3.0 | |||
| Hardware: | Unspecified | |||
| OS: | Unspecified | |||
| Whiteboard: | ||||
| Fixed In Version: | Doc Type: | Bug Fix | ||
| Doc Text: |
Cause:
Outdated link
Consequence:
Users who clicked on link went to the wrong page
Fix:
Updated link URL
Result:
Users now click on the link and it goes to the current docs
|
Story Points: | --- | |
| Clone Of: | ||||
| : | 1775457 1775458 (view as bug list) | Environment: | ||
| Last Closed: | 2020-01-23 11:03:45 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: | ||||
| Bug Depends On: | ||||
| Bug Blocks: | 1775457, 1775458 | |||
|
Description
shahan
2019-03-25 05:29:37 UTC
Can we update the link to https://docs.openshift.com/container-platform/4.2/networking/configuring-networkpolicy.html? Makes sense to me. We should add an OpenShift flag check. We should centralize our doc links in one place like we had previously: https://github.com/openshift/console/commit/2dae49a86c0d3a34c6ed969a575be3c54d47195a#diff-12887fc2371d38a701d3799cb2766141 The doc link has changed to the on https://docs.openshift.com/container-platform/4.3/networking/configuring-networkpolicy.html for 4.3 cluster. Verified this bug. 4.3.0-0.nightly-2019-11-21-122827 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:0062 |