Bug 2029600
| Summary: | connect vm to an external network quickstart has 404 link to network bridge doc | ||
|---|---|---|---|
| Product: | Container Native Virtualization (CNV) | Reporter: | Dale Bewley <dbewley> |
| Component: | Installation | Assignee: | Simone Tiraboschi <stirabos> |
| Status: | CLOSED ERRATA | QA Contact: | Satyajit Bulage <sbulage> |
| Severity: | medium | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 4.8.3 | CC: | bgaydos, cnv-qe-bugs, dbasunag, dholler, fdeutsch, gouyang, kmajcher, stirabos, tnisan, ycui, yzamir |
| Target Milestone: | --- | Keywords: | UserExperience |
| Target Release: | 4.10.3 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | hco-bundle-registry-container-v4.10.3-1 | Doc Type: | If docs needed, set a value |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2022-07-20 16:01:13 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
Dale Bewley
2021-12-06 20:59:46 UTC
@tnisan Looks like the broken link is in the UI in a hover-over message. I'll ask the writer's to find the correct link but we'll need an engineer to update the UI. Should we assign this to your team or should I contact the CNV network lead for engineering? Quickstart has bad URL The issue still exists on latest 4.11 console. Hi I don't know what team eploy the quickstarts that to doc team writes, moving to SSP because I think SSP is the team that deploy the quickstarts CRs, please move to the correct team if another team deploys the quickstarts. @stirabos is taking care of the quickstarts, reassigning According to the OpenShift writers, here is the correct URL: https://docs.openshift.com/container-platform/4.7/networking/multiple_networks/configuring-additional-network.html#nw-multus-bridge-object_configuring-additional-network I would not recommend hard coding a release number in the link. If you already know that, that's great. If you need more details on how to generalize the link so it works across future releases, just ask. @bgaydos Hi @stirabos - I thought I had a solution for you, but I do not. :-( When using docs.openshift.com, you can substitute `current_release` for the release number in a path and the link resolves to the latest release doc page, but this does not work anywhere other than docs.openshift.com. Current management direction is to steer users to the portal and it's associated pages. According to our Content Strategist, Avital Pinnock, the portal team has on it's list of improvements the ability to support the `current_release` variable, but there is no firm data when this enhancement will be implemented. If I hear anything, I will let you know. Thanks, Bob cc: @ctomasko Here is a link to the most-recent 4.10 content. https://docs.openshift.com/container-platform/4.10/networking/multiple_networks/configuring-additional-network.html Postponing due to capacity waiting for the first build for 4.10.3 ConsoleQuickStart: connect-to-extenal network in pointing to correct 4.10 link. Verifying. 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 Virtualization 4.10.3 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/RHEA-2022:5675 |