Bug 1815578

Summary:	ROKS: stop ClusterMachineApproverDown alert from firing
Product:	OpenShift Container Platform	Reporter:	Cesar Wong <cewong>
Component:	Cloud Compute	Assignee:	Cesar Wong <cewong>
Status:	CLOSED ERRATA	QA Contact:	Milind Yadav <miyadav>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	4.3.z	CC:	jhou
Target Milestone:	---
Target Release:	4.3.z
Hardware:	All
OS:	All
Whiteboard:	IBMROKS
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:	1809329	Environment:
Last Closed:	2020-04-08 07:39:51 UTC	Type:	---
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:	1815587
Bug Blocks:

Comment 4 Milind Yadav 2020-03-27 07:50:13 UTC

Verified on :
NAME      VERSION                             AVAILABLE   PROGRESSING   SINCE   STATUS
version   4.3.0-0.nightly-2020-03-27-012404   True        False         55m     Cluster version is 4.3.0-0.nightly-2020-03-27-012404


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.3.z IBMROKS.

Comment 5 Cesar Wong 2020-03-31 17:20:49 UTC

Verified with 4.3.0-0.nightly-2020-03-30-133721

Comment 7 errata-xmlrpc 2020-04-08 07:39:51 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:1262