Bug 1758623

Summary:	The details card is showing the host instead of the node, and clicking on it leads to a 404
Product:	OpenShift Container Platform	Reporter:	Udi Kalifon <ukalifon>
Component:	Console Metal3 Plugin	Assignee:	Honza Pokorny <hpokorny>
Status:	CLOSED ERRATA	QA Contact:	Udi Kalifon <ukalifon>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	4.3.0	CC:	aos-bugs, cvultur, hpokorny, jtomasek
Target Milestone:	---
Target Release:	4.3.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	No Doc Update
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2020-05-13 21:26:54 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 Udi Kalifon 2019-10-04 16:01:33 UTC

Description of problem:
In the baremetal host dashboard, there is a new details card in 4.3, and it shows the node object which is associated the host. However, the name of the node is wrong and is actually the host's name, and the link to the node is broken.


How reproducible:
100%


Steps to Reproduce:
1. Browse to the baremetal hosts page, which lists the hosts and their nodes in a table vew. In my environment, host openshift-master-2 is associated with node rhhi-node-master-0.
2. Click on the host and switch to the dashboards tab.
3. Look at the node in the details card.


Actual results:
The node has a "N" icon like a node object, but the name is really the host's name "openshift-master-2" (it was supposed to be the node "rhhi-node-master-0"). Try to click on it - it leads to a 404.


Expected results:
The associated node should appear in the card, and clicking on it should bring you to the details page of the node object.

Comment 2 Constantin Vultur 2019-11-08 14:19:39 UTC

This is fixed. 
While clicking on the Node link on the Bare Metal Host/Dashboard it arrived on the Node Overview page. 

Given that there was not possibility to have and end-to-end system installed,
I tested this locally in a combination of 'yarn dev' and ./bin/bridge
The local yarn was poining to a system running     4.3.0-0.ci-2019-10-30-082153

The git console log:
commit 6d8ab1f335135d959b8943b09fb172185d785fe4 (HEAD -> master, origin/release-4.4, origin/release-4.3, origin/master, origin/HEAD)
Merge: e38f53c73 8450c4d9b
Author: OpenShift Merge Robot <openshift-merge-robot.github.com>
Date:   Fri Nov 8 13:28:09 2019 +0100

Comment 3 Constantin Vultur 2019-11-08 14:46:55 UTC

Noting that, the system had CNV installed by hand , from https://raw.githubusercontent.com/kubevirt/hyperconverged-cluster-operator/master/deploy/deploy.sh

Comment 5 errata-xmlrpc 2020-05-13 21:26:54 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:0062