Bug 1814582

Summary: NodeStartupTimeout should be user configurable
Product: OpenShift Container Platform Reporter: Joel Speed <jspeed>
Component: Cloud ComputeAssignee: Joel Speed <jspeed>
Cloud Compute sub component: Other Providers QA Contact: Jianwei Hou <jhou>
Status: CLOSED NEXTRELEASE Docs Contact:
Severity: medium    
Priority: unspecified    
Version: 4.4   
Target Milestone: ---   
Target Release: 4.4.z   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
: 1814589 (view as bug list) Environment:
Last Closed: 2020-06-26 10:30:56 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: 1814589    
Bug Blocks:    

Description Joel Speed 2020-03-18 10:28:43 UTC 
Description of problem:

If a Machine does not get a node within 10 minutes, the MHC determines the Machine to be unhealthy and remediates it.

This 10 minute default is currently hard coded and should instead be user configurable so that different platforms can specify different values

Version-Release number of selected component (if applicable):
4.4
MachineHealthCheck

How reproducible:
Prevent Node from getting machine for 10 minutes

Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

This is related to https://github.com/openshift/machine-api-operator/pull/501
Comment 1 Joel Speed 2020-04-20 11:19:42 UTC 
PR https://github.com/openshift/machine-api-operator/pull/523 will update BZ once 4.4.z release branch is opened