Bug 1850439

Summary: cockpit ovirt(upstream) docs links point to downstream docs.
Product: [oVirt] cockpit-ovirt Reporter: Wei Wang <weiwang>
Component: Hosted EngineAssignee: Aviv Turgeman <aturgema>
Status: CLOSED CURRENTRELEASE QA Contact: Wei Wang <weiwang>
Severity: medium Docs Contact:
Priority: medium    
Version: 0.14.6CC: bugs, cshao, eslutsky, mavital, peyu, qiyuan, sbonazzo, shlei, weiwang, yaniwang, yturgema
Target Milestone: ovirt-4.4.3Flags: pm-rhel: ovirt-4.4+
pm-rhel: planning_ack+
sbonazzo: devel_ack+
weiwang: testing_ack+
Target Release: 0.14.12   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: cockpit-ovirt-0.14.12 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-10-23 15:31:40 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: Integration RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Wei Wang 2020-06-24 10:20:22 UTC
Description of problem:
cockpit ovirt(upstream) docs links point to downstream docs. When clicking the links in cockpit ovirt hosted engine page(upstream), the links on the upstream project jump to the downstream doc.

Version-Release number of selected component (if applicable):
ovirt-node-ng-4.4.0-0.20200608.0

How reproducible:
100%

Steps to Reproduce:
1. Clean install ovirt-node-ng-4.4.0-0.20200608.0
2. Go to hosted engine page in cockpit ovirt
3. Click the two links "Installation Guide" and "RHV Documents" 

Actual results:
1. cockpit ovirt(upstream) docs links point to downstream docs.
2. The link name of "RHV Documents" displays downstream name RHV

Expected results:
1. Cockpit ovirt(upstream) docs links should point to downstream docs.
2. The link name of "RHV Documents" should display upstream name instead of RHV

Additional info:

Comment 4 Sandro Bonazzola 2020-11-11 06:45:41 UTC
This bugzilla is included in oVirt 4.4.3 release, published on November 10th 2020.

Since the problem described in this bug report should be resolved in oVirt 4.4.3 release, it has been closed with a resolution of CURRENT RELEASE.

If the solution does not work for you, please open a new bug report.