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

Bug 1965399

Summary: Multiple network request while searching in search page
Product: OpenShift Container Platform Reporter: Rohit Rai <rorai>
Component: Management ConsoleAssignee: Zac Herman <zherman>
Status: CLOSED DUPLICATE QA Contact: Yadan Pei <yapei>
Severity: low Docs Contact:
Priority: low    
Version: 4.7CC: aos-bugs, jokerman, spadgett
Target Milestone: ---Keywords: Reopened
Target Release: ---   
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: 2021-11-03 16:33:32 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
The screencast showing network requests in console while searching none

Description Rohit Rai 2021-05-27 15:55:47 UTC
Created attachment 1787652 [details]
The screencast showing network requests in console while searching

Description of problem:The search page makes multiple network requests while searching any term using name filter in the search page. It is sending a request for each keystroke in the search box.


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


How reproducible: Always


Steps to Reproduce:
1.Go to search page.
2.Select ClusterRole as resource.
3.Select name filter in the filter bar and enter a search term.
4.Open the browser console and check for network requests.

Actual results:A new network request for each keystroke.


Expected results:No network request should be there. The filtering should happen in frontend.


Additional info:

Comment 1 Zac Herman 2021-06-01 15:24:05 UTC
@rohitrai - Those requests you see are simply updating the URL params and are not making network connections.  Closing as working as designed.

Comment 2 Samuel Padgett 2021-06-01 15:58:34 UTC
I'm able to reproduce. I see a separate network request for each character I type into the name filter on the Home -> Search page. It seems that we're passing a `name` query parameter to the k8s API, but I don't believe that that is used for anything.

Comment 3 Zac Herman 2021-11-03 16:33:32 UTC
This issue will be resolved with the fix to bug 2002896.  While the issue is different, the solution to 2002896 removes the network calls and instead uses the stored values.  Closing this as a dup.

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

Comment 4 Zac Herman 2021-11-03 16:34:50 UTC
Another note, since the filtering was reworked in 4.9, we will not be porting this fix back to 4.7 since it did not affect usage or customer experience.