Bug 1809325 - ROKS: ClusterAutoscalerOperatorDown alert should not fire, Machine Autoscalers should not appear in console UI.
Summary: ROKS: ClusterAutoscalerOperatorDown alert should not fire, Machine Autoscaler...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Cloud Compute
Version: 4.4
Hardware: All
OS: All
unspecified
medium
Target Milestone: ---
: 4.5.0
Assignee: Cesar Wong
QA Contact: Jianwei Hou
URL:
Whiteboard: IBMROKS
Depends On:
Blocks: 1814090
TreeView+ depends on / blocked
 
Reported: 2020-03-02 20:51 UTC by Cesar Wong
Modified: 2020-07-13 17:17 UTC (History)
0 users

Fixed In Version:
Doc Type: No Doc Update
Doc Text:
Clone Of:
: 1814090 (view as bug list)
Environment:
Last Closed: 2020-07-13 17:17:29 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github openshift cluster-autoscaler-operator pull 134 0 None closed Bug 1809325: ROKS - remove additional autoscaler manifests 2020-06-23 08:56:34 UTC
Red Hat Product Errata RHBA-2020:2409 0 None None None 2020-07-13 17:17:57 UTC

Description Cesar Wong 2020-03-02 20:51:10 UTC
Description of problem:
In a ROKS cluster, the ClusterAutoScalerOperatorDown alert is firing because the ClusterAutoScaler operator is not installed. No alert should fire.

Machine Autoscalers appears as an entry under Compute in the UI. Machine Autoscalers should not appear in the UI because machines are managed outside of the cluster.

Comment 3 Jianwei Hou 2020-03-25 03:47:04 UTC
Verified on 4.5.0-0.nightly-2020-03-23-222213

On OCP cluster, the alert ClusterAutoscalerOperatorDown could successfully fire when the cluster-autoscaler operator is down.

On console ui, the machine autoscaler is well displayed.

This is good to move to verified as long as it's verified in 4.5 IBMROKS.

Comment 4 Cesar Wong 2020-03-25 17:26:22 UTC
Verified on 4.5.0-0.nightly-2020-03-23-222213

Comment 6 errata-xmlrpc 2020-07-13 17:17:29 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, 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/RHBA-2020:2409


Note You need to log in before you can comment on or make changes to this bug.