Version: 4.10.6 Platform: aws (but really any) Please specify: IPI What happened? We are deploying clusters with c5.metal instance types on AWS (for OpenShift Virtualization). It takes AWS sometimes too long to provision these instances and the installer therefore times out. We could of course add manual logic to "wait-for-install-complete" but I don't think there is a timeout parameter for that command - it'll just sit there forever. It would be a quick fix to add a few timeout parameters to the openshift-install command. e.g. --wait-for-bootstrap-timeout = 20m, --wait-for-cluster-complete=40m These would have sensible defaults (e.g. what is hardcoded right now) but could be overwritten if necessary. Note while our use case is a Single Node Bare Metal install on AWS (which technically is not a supported environment) this problem surfaces even more when a whole control plane would be provisioned on bare metal instances. Also note that this may not just be AWS - bare metal providers have much longer times to create machines than VMs.
Can you try with a newer installer version, e.g 4.10.24? We've increased the bootstrap timeout for baremetall installs [1] [1] https://github.com/openshift/installer/pull/6017/files
About configurable timeouts, see discussions at https://github.com/openshift/installer/pull/5979
I don't think the referenced pull request will help - how does it determine that it's bare metal. My use case is just an IPI install on AWS usinc c5.metal instances.
(In reply to Wolfgang Kulhanek from comment #3) > I don't think the referenced pull request will help - how does it determine > that it's bare metal. It determines by the platform name used in the install-config. > My use case is just an IPI install on AWS usinc c5.metal instances. Ah, you had mentioned "Note while our use case is a Single Node Bare Metal install on AWS (which technically is not a supported environment) this problem surfaces even more when a whole control plane would be provisioned on bare metal instances.", so I assumed you set the platform to "baremetal" in the install-config.
Thanks for bringing this up. I am closing this as NOTABUG, because we are managing the addition of this functionality in https://issues.redhat.com/browse/CORS-2087 I have added a link to this BZ in that Jira card. You can track the work there.