Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1754412

Summary:	Baremetal host dashboard page flickers too long as it updates every 5 seconds
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:	unspecified	CC:	aos-bugs, cvultur, hpokorny, jtomasek, tjelinek
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-01-23 11:06:39 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-09-23 08:02:27 UTC

Description of problem:
The dashboards page in the baremetal host details is automatically refreshing every 5 seconds. Each refresh is causing a long flicker, where the items in the page temporarily disappear and spinners appear instead, and it makes it hard to view updates. It doesn't happen in the system overview dashboards page.


How reproducible:
100%


Steps to Reproduce:
1. Click on any bare metal host, and switch to the dashboards tab
2. Wait for the automatic refreshes every 5 seconds.


Actual results:
Each update is accompanied with a long flicker.


Expected results:
The update should happen after the updated data already finished to download, and the spinners should not be visible.

Comment 1 Honza Pokorny 2019-11-05 17:55:57 UTC

Resolved by https://github.com/openshift/console/pull/3139

Comment 2 Jiri Tomasek 2019-11-06 09:10:06 UTC

Honza, please link the BZ with github PR by changing the PR title to `Bug 1754412: <PR title>`. That will automatically link the PR and update the bug according to PR status. It can be done after the PR has been merged as well. BZ should be in 'Modified'. It will be put into 'ON_QA' automatically by errata system.

Comment 4 Honza Pokorny 2019-11-06 11:44:06 UTC

I can't read :(

Comment 5 Constantin Vultur 2019-11-08 14:02:14 UTC

This is fixed. 

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 6 Constantin Vultur 2019-11-08 14:47:05 UTC

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

Comment 8 errata-xmlrpc 2020-01-23 11:06:39 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