Make bootstrap timeout configurable

[rabin-io]

This is basically a request to marge/implement #5979.

Version

# openshift-baremetal-install version
openshift-baremetal-install 4.11.0-rc.5
built from commit 37684309bcb598757c99d3ea9fbc0758343d64a5
release image quay.io/openshift-release-dev/ocp-release@sha256:5b1a987e21b199321d200ac20ae27390a75c1f44b83805dadfae7e5a967b9e5d
release architecture amd64

Platform:

• baremetal
• UPI (semi-manual installation on customized infrastructure)

What happened?

In some clusters that I deploy OCP on, there is a small chance the bootstrap process will take a bit longer than 30 minutes, and my pipelines will fail, but when you check 5-10 minutes later, the cluster actually finished installing sucecsfully.

What do you expect to happen?

I prefer to have the flag to change the timeout to any custom value which meets my needs.
and not relay on try/catch and retries.

Other GitHub issues

• Bug 2090816: Make bootstrap timeout configurable #5979

[openshift-bot]

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale

[rabin-io]

This is very annoying for us, as we had to implement some workarounds to go around this arbitrary timeout. Please reconsider the patch to support an external overwrite to timeout for each of the stages.

[yxchiwork]

/remove-lifecycle stale

[adeturner]

Wholeheartedly agree with this request. Timeouts for ARO and OCP are especially low when provisioning in Azure

[openshift-bot]

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale

[rabin-io]

I would appreciate if any of the maintainers/developers can address this, as this still affects us, and break our pipelines, and we forced to have some stupid hacks to avoid this enforced timeout.

/remove-lifecycle stale

[openshift-bot]

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale

[rabin-io]

/remove-lifecycle stale
/lifecycle frozen