Make assisted-installer cluster install timeout configurable - #9902
Open
rhjcd wants to merge 1 commit into
Open
Conversation
The Start cluster installation task hardcoded async/wait_timeout at 5400s (90 min). On Ceph-backed CNV environments the assisted-installer cluster install can run slightly longer, causing a spurious Timeout exceeded failure while the install is still progressing. Add ai_cluster_install_timeout (default 5400, unchanged behavior) in the role vars and use it for both async and wait_timeout, so consumers can raise it via agnosticv without altering the conservative role default.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
The
host-ocp4-assisted-installertask Start cluster installation hardcodesasync: 5400/wait_timeout: 5400(90 min). On Ceph-backed CNV environments the assisted-installer cluster install can run slightly past 90 minutes, so Ansible kills the still-progressing install withTimeout exceeded.Observed in prod job 116558 (HCP-on-CNV, guid
bfgzt): the install ran 13:30:53 → 15:02:03 = 91m 9s and was killed while still pollingfinished=0.Change
ai_cluster_install_timeouttoroles/host-ocp4-assisted-installer/vars/main.yaml, defaulting to 5400 — behavior is unchanged for every existing consumer.asyncandwait_timeouton the install task.This lets consumers raise the timeout via agnosticv without changing the conservative role default — the same pattern @agonzalezrh requested for
ai_workers_vm_ready_retrieson #9886 ("add a default value ... use agV to set a higher value").The higher value for HCP-on-CNV is set in agnosticv (
ai_cluster_install_timeout: 7200), not here.Related: RHDPOPS-23971.