Bug 1827490

Summary: [IPI on BM] Bare Metal Hosts Details page always shows a loading icon for Pods when BMH is in inspection error status
Product: OpenShift Container Platform Reporter: Yadan Pei <yapei>
Component: Console Metal3 PluginAssignee: Yadan Pei <yapei>
Status: CLOSED ERRATA QA Contact: Yadan Pei <yapei>
Severity: low Docs Contact:
Priority: low    
Version: 4.4CC: aos-bugs, jokerman, jtomasek, yapei
Target Milestone: ---   
Target Release: 4.5.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Cause: Pods are determined by BMH Node. In some cases Node is not available. Consequence: Pods item in Overview page keeps loading Fix: Detect when BMH Node is not available Result: Pods items shows 0 pods instead of loading state
 Story Points: ---
Clone Of: Environment:
Last Closed: 2020-07-13 17:30:56 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:
Attachments:
Description Flags
0 Pods are shown none

Description Yadan Pei 2020-04-24 03:42:28 UTC 
Description of problem:
When a BMH is in 'Inspection error' status, it always shows a loading icon in Inventory card on BMH details page

Version-Release number of selected component (if applicable):
4.4.0-0.nightly-2020-04-18-095545

How reproducible:
Always

Steps to Reproduce:
1. Visit BMH details page from Nodes -> Bare Metal Hosts -> click the one in inspection error status
2. check Inventory card
3.

Actual results:
2. It always shows a loading icon besides 'Pods'

Expected results:
2. If there is no pods, we should show correct number 0 instead of always showing loading icon

Additional info:
Comment 3 Yadan Pei 2020-06-17 03:00:37 UTC 
Created attachment 1697729 [details]
0 Pods are shown

When a BMH is in Registration error status, Bare Metal Host Details page shows '0 Pods' in Inventory card


Verified on 4.5.0-0.nightly-2020-06-11-183238
Comment 4 errata-xmlrpc 2020-07-13 17:30:56 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:2409