Bug 1728957

Summary: API Explorer list keeps display loading instead of No API Found
Product: OpenShift Container Platform Reporter: XiaochuanWang <xiaocwan>
Component: Management ConsoleAssignee: Samuel Padgett <spadgett>
Status: CLOSED ERRATA QA Contact: Yadan Pei <yapei>
Severity: medium Docs Contact:
Priority: medium    
Version: 4.2.0CC: aos-bugs, jokerman, mmccomas
Target Milestone: ---   
Target Release: 4.2.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-10-16 06:33:27 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
404 not found message none

Description XiaochuanWang 2019-07-11 06:25:43 UTC 
Description of problem:
On API Explorer page, filter some non-existed API and check the list. API Explorer list keeps display loading instead of showing clear result such as "No API Found"

Version-Release number of selected component (if applicable):
4.2.0-0.nightly-2019-07-10-062553

How reproducible:
Always

Steps to Reproduce:
1.Go to API Explorer page, filter some non-existed API and check the list


Actual results:
API Explorer list keeps display loading instead of No API Found 

Expected results:
Should display a result cuch as "No API Found"

Additional info:
Comment 1 Samuel Padgett 2019-07-11 13:21:09 UTC 
I'm unable to reproduce. I get a 404: Not Found page. Can you paste the exact URL you are using?
Comment 2 Samuel Padgett 2019-07-11 13:21:35 UTC 
Created attachment 1589497 [details]
404 not found message
Comment 3 Samuel Padgett 2019-07-12 20:14:04 UTC 
Sorry, I see now. This is a text filter with no matches. I can reproduce.
Comment 5 XiaochuanWang 2019-07-22 02:46:11 UTC 
It correctly shows "No API Resources Found" when the filter does not match anything. This issue could be closed now.
Verified on 4.2.0-0.nightly-2019-07-21-222447
Comment 6 errata-xmlrpc 2019-10-16 06:33:27 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-2019:2922