Bug 1784224

Summary: Openshift cluster console limitation of item list
Product: OpenShift Container Platform Reporter: sfu <sfu>
Component: Management ConsoleAssignee: Samuel Padgett <spadgett>
Status: CLOSED DUPLICATE QA Contact: Yadan Pei <yapei>
Severity: high Docs Contact:
Priority: unspecified    
Version: 3.11.0CC: aos-bugs, jokerman, scuppett
Target Milestone: ---   
Target Release: 3.11.z   
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-12-17 19:52:17 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 sfu@redhat.com 2019-12-17 01:47:03 UTC 
Description of problem:
In Openshift Cluster console web page,if resource(route,pod) number>250, it won't show all and filter can't retrive correcly

Version-Release number of selected component (if applicable):
3.11

How reproducible:
always

Steps to Reproduce:
create resource(route,pod) > 250,then view them in Cluster-console web page with cluster-admin role user.

Actual results:
Incomplete display and filter can't retrive correcly
we can see the reqeust URL contains "limit=250" param in chrome dev tool,like:

Request URL: https://console.apps.ocp.com/api/kubernetes/apis/route.openshift.io/v1/namespaces/default/routes?limit=250


Expected results:
Paging display would be better.

Additional info:
the origin issue is when listing resources,it will show mismatch numbers between cluster console and oc cmd,after checking console api,we found limit=250 param.
Since in many customer production envirmont,resource number often more then 250 and dev role always check them from UI,not from oc client.

Screenshoot attached.
Comment 2 sfu@redhat.com 2019-12-17 01:52:40 UTC 
Created attachment 1645722 [details]
pods
Comment 3 Samuel Padgett 2019-12-17 19:52:17 UTC 
The limit in the URL is expected and just means we load items 250 at a time.

This is a duplicate of bug 1677545. Please make sure you are running at least version 3.11.98, which contains the fix.

https://access.redhat.com/errata/RHBA-2019:0636

*** This bug has been marked as a duplicate of bug 1677545 ***