Bug 1809325

Summary: ROKS: ClusterAutoscalerOperatorDown alert should not fire, Machine Autoscalers should not appear in console UI.
Product: OpenShift Container Platform Reporter: Cesar Wong <cewong>
Component: Cloud ComputeAssignee: Cesar Wong <cewong>
Cloud Compute sub component: Other Providers QA Contact: Jianwei Hou <jhou>
Status: CLOSED ERRATA Docs Contact:
Severity: medium    
Priority: unspecified    
Version: 4.4   
Target Milestone: ---   
Target Release: 4.5.0   
Hardware: All   
OS: All   
Whiteboard: IBMROKS
Fixed In Version: Doc Type: No Doc Update
Doc Text:
Story Points: ---
Clone Of:
: 1814090 (view as bug list) Environment:
Last Closed: 2020-07-13 17:17:29 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: 1814090    

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