Bug 1390890
| Summary: | Broken 404 not found link in BuildConfig edit screen on Web Console | ||
|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | Takayoshi Kimura <tkimura> |
| Component: | Management Console | Assignee: | Jessica Forrester <jforrest> |
| Status: | CLOSED ERRATA | QA Contact: | Yadan Pei <yapei> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 3.3.0 | CC: | aos-bugs, jokerman, mmccomas, tdawson |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: |
Cause: The build triggers help link in the console contained the .org suffix instead of .com.
Consequence: The build triggers help link would return a 404 because the requested page did not exist under the docs.openshift.org website.
Fix: The build triggers help link was updated to the correct URL.
Result: The build triggers help link will load the correct help documentation for openshift container platform 3.4
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2017-01-18 12:48:51 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: | |||
|
Description
Takayoshi Kimura
2016-11-02 08:12:00 UTC
This is fixed in 3.4 This has been merged into ose and is in OSE v3.4.0.19 or newer. Checked against v3.4.0.19+346a31d Now "Learn more" link next to "Triggers" points to correct address https://docs.openshift.com/container_platform/3.4/dev_guide/builds.html#build-triggers Please note 404 Not Found is returned since docs for OCP 3.4 are still not published Move to VERIFIED 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-2017:0066 |