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

Bug 1906933

Summary: Cluster Autoscaler should have improved mechanisms for group identifiers
Product: OpenShift Container Platform Reporter: Michael McCune <mimccune>
Component: Cloud ComputeAssignee: Alberto <agarcial>
Cloud Compute sub component: Other Providers QA Contact: sunzhaohua <zhsun>
Status: CLOSED ERRATA Docs Contact:
Severity: medium    
Priority: unspecified    
Version: 4.7   
Target Milestone: ---   
Target Release: 4.7.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: 2021-02-24 15:43:00 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 Michael McCune 2020-12-11 20:14:05 UTC
As part of the effort to rebase the cluster autoscaler on the 1.20 release there are several patches from the upstream project which should be incorporated to the OpenShift autoscaler repository.

This issue surrounds the incorporation of the patch to update the group identifiers and logic for the cluster autoscaler, see https://github.com/kubernetes/autoscaler/pull/3161

The OpenShift implementation of the autoscaler should include this patch as part of the process for rebasing on top of 1.20.

Comment 3 sunzhaohua 2020-12-28 02:48:40 UTC
according to our latest regression test result, move this to verified.

Comment 5 errata-xmlrpc 2021-02-24 15:43:00 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.7.0 security, bug fix, and enhancement 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-2020:5633