Bug 1815578 - ROKS: stop ClusterMachineApproverDown alert from firing
Summary: ROKS: stop ClusterMachineApproverDown alert from firing
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Cloud Compute
Version: 4.3.z
Hardware: All
OS: All
unspecified
medium
Target Milestone: ---
: 4.3.z
Assignee: Cesar Wong
QA Contact: Milind Yadav
URL:
Whiteboard: IBMROKS
Depends On: 1815587
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-03-20 15:58 UTC by Cesar Wong
Modified: 2020-04-08 07:40 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 1809329
Environment:
Last Closed: 2020-04-08 07:39:51 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github openshift cluster-machine-approver pull 66 0 None closed [release-4.3] Bug 1815578: ROKS - remove ClusterMachineApproverDown prometheus rule 2020-04-03 17:31:10 UTC
Red Hat Product Errata RHBA-2020:1262 0 None None None 2020-04-08 07:40:03 UTC

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
Note You need to log in before you can comment on or make changes to this bug.