-
Spike
-
Resolution: Done
-
Critical
-
None
-
None
-
None
-
None
-
False
-
None
-
False
-
-
Impact statement for the OCPBUGS-33715 series.
Which 4.y.z to 4.y'.z' updates increase vulnerability?
- Updates into 4.16.0, 4.16.1, 4.16.2, and 4.16.3 versions
Which types of clusters?
- Any type of production OCP cluster.
What is the impact? Is it serious enough to warrant removing update recommendations?
- No direct impact on an updated OCP cluster.
- An OpenShift Cluster Manager (OCM) cluster of a given cluster (if existing) is put under a higher load of requests to obtain the ORGANIZATION_ID.
How involved is remediation?
- An admin can manually disable the telemetry reporting of a given cluster.
Is this a regression?
- Yes, the issue was fixed in the 4.16.4 version.
- is related to
-
OCPBUGS-34012 Reduce the number of calls to the subscriptions fetchOrganization endpoint from console-operator
- Closed