Bug 2042829

Summary:	Topology performance: HPA was fetched for each Deployment (Pod Ring)
Product:	OpenShift Container Platform	Reporter:	Christoph Jerolimov <cjerolim>
Component:	Dev Console	Assignee:	Christoph Jerolimov <cjerolim>
Status:	CLOSED ERRATA	QA Contact:	spathak <spathak>
Severity:	high	Docs Contact:
Priority:	high
Version:	4.7	CC:	aos-bugs, nmukherj
Target Milestone:	---
Target Release:	4.10.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:	2022-03-10 16:40:58 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:
Bug Depends On:
Bug Blocks:	2044259

Description Christoph Jerolimov 2022-01-20 08:33:46 UTC

Description of problem:
The topology loads the complete HorizontalPodAutoscalers (HPA) resource list for each Deployment which is shown on the topology. This happens because the HPA resource reference the Deployment within the spec only. But the topology should avoid fetching the same list again and again anyway.

Version-Release number of selected component (if applicable):
Reproducible on 4.8+
4.6/4.7 not tested yet.

How reproducible:
Always with Topologies with at least two Deployments.

Steps to Reproduce:
1. Import two Deployments
2. Open the network inspector of your browser and navigate to the topology
3. Reload the browser tab

Actual results:
See multiple API calls fetching HPAs, one per Deployment

/api/kubernetes/apis/autoscaling/v2beta2/namespaces/openshift-monitoring/horizontalpodautoscalers?


Expected results:
Should not fetch the same resource more then once.


Additional info:

Comment 3 Christoph Jerolimov 2022-01-24 19:48:32 UTC

Verified on 4.10.0-0.nightly-2022-01-24-181700

See only 1 api call for HPA

Comment 6 errata-xmlrpc 2022-03-10 16:40:58 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 (Moderate: OpenShift Container Platform 4.10.3 security update), 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/RHSA-2022:0056