Bug 1814582 - NodeStartupTimeout should be user configurable
Summary: NodeStartupTimeout should be user configurable
Keywords:
Status: CLOSED NEXTRELEASE
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Cloud Compute
Version: 4.4
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ---
: 4.4.z
Assignee: Joel Speed
QA Contact: Jianwei Hou
URL:
Whiteboard:
Depends On: 1814589
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-03-18 10:28 UTC by Joel Speed
Modified: 2020-06-26 10:30 UTC (History)
0 users

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
: 1814589 (view as bug list)
Environment:
Last Closed: 2020-06-26 10:30:56 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

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