openshift / openshift/installer
Make bootstrap timeout configurable
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 1.6k
- Forks
- 1.5k
- Avg merge
- 5d 5h
- Merged PRs (30d)
- 39
Description
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
- #5979
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the openshift-baremetal-install bootstrap timeout handling and review the requested implementation in issue #5979. Add a configurable timeout that accepts custom values, then verify that bootstrap runs longer than 30 minutes without premature pipeline failure.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- cli, infrastructure
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100