Bug 1878204

Summary:	MAO alert timing too aggressive
Product:	OpenShift Container Platform	Reporter:	Michael Gugino <mgugino>
Component:	Cloud Compute	Assignee:	Michael Gugino <mgugino>
Cloud Compute sub component:	Other Providers	QA Contact:	sunzhaohua <zhsun>
Status:	CLOSED ERRATA	Docs Contact:
Severity:	medium
Priority:	unspecified	CC:	mimccune
Version:	4.6
Target Milestone:	---
Target Release:	4.6.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:	2020-10-27 16:40:12 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:	1888206

Description Michael Gugino 2020-09-11 15:03:40 UTC

More details here: https://issues.redhat.com/browse/OCPCLOUD-842

Current alert timings are arbitrary and have some race conditions with MHC and cluster autoscaler that result in flapping for broken nodes.

Comment 3 sunzhaohua 2020-09-24 03:15:10 UTC

Verified
clusterversion: 4.6.0-0.nightly-2020-09-22-213802

Scale up machineset, then delete nodes but machine still exist.
Enable machinehealthcheck
Check Alerting,  alert MachineWithoutValidNode severity is Warning.

Comment 6 errata-xmlrpc 2020-10-27 16:40:12 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 (OpenShift Container Platform 4.6 GA Images), 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:4196