Bug 2071897

Summary:	Dashboard is breaking when object value is null
Product:	[Red Hat Storage] Red Hat OpenShift Data Foundation	Reporter:	Bipul Adhikari <badhikar>
Component:	management-console	Assignee:	Bipul Adhikari <badhikar>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Aman Agrawal <amagrawa>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	4.10	CC:	amagrawa, jefbrown, kramdoss, madam, muagarwa, nthomas, ocs-bugs, odf-bz-bot, rperiyas
Target Milestone:	---
Target Release:	ODF 4.10.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	4.10.0-220	Doc Type:	No Doc Update
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2022-04-21 09:12: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 Bipul Adhikari 2022-04-05 06:28:12 UTC

Description of problem (please be detailed as possible and provide log
snippests):
Dashboard breaks when it can't read object properties sometimes due to network issues. 


Version of all relevant components (if applicable): 4.10


Does this issue impact your ability to continue to work with the product
(please explain in detail what is the user impact)? Yes


Is there any workaround available to the best of your knowledge? No


Rate from 1 - 5 the complexity of the scenario you performed that caused this
bug (1 - very simple, 5 - very complex)? 3


Can this issue reproducible? Yes


Can this issue reproduce from the UI? Yes



Steps to Reproduce:
1. Go to ODF Dashboard
2. Stop network calls from the browser Inspector
3.


Actual results: Page shouldn't break.


Expected results: Page breaks.


Additional info: Dashboard cards should handle null values.

Comment 8 Bipul Adhikari 2022-04-07 09:53:03 UTC

I do not believe a customer has a high chance of hitting this hence proposing this issue as a low severity issue. The precise timing of data connectivity loss required has been always present and we never hit this issue in 4.9 and in 4.10 as well this requires a precise timed network connectivity lost when the user presses ODF (for the first time). A easy workaround is just refreshing the page after the internet connection is restored.