mirror of
https://github.com/cozystack/cozystack.git
synced 2026-11-04 02:57:27 +09:00
Myasnikov Daniil
6ce140412e
The post-install-prep helper waited for each LINSTOR prerequisite with a separate fixed timeout anchored to the script's start: timeout 60 for the linstor HelmRelease object to exist, timeout 300 for the controller Deployment, timeout 60 for nodes Online. Those budgets raced the platform reconcile chain. The cozystack-operator alone needs ~70s just to emit the linstor HR, so the 60s exists-wait expired ~10s before the object appeared and 'set -e' aborted the whole script, failing the install with a single log line and no diagnostics. Across recent CI runs healthy LINSTOR convergence is ~11-13 min, so the per-hop guesses had no margin and passed only on favourable variance. Replace the exists+ready pairs with a wait_for helper that polls 'kubectl wait' under one shared 15m deadline -- the same window the installer's 'kubectl wait hr --all' already uses -- tolerating not-yet-created objects (kubectl wait exits non-zero on NotFound) without the set -e cliff, while still failing hard if a resource never becomes ready inside the budget. Bump the 3-nodes-Online wait 60s to 300s for the same reason. Assisted-By: Claude <noreply@anthropic.com> Signed-off-by: Myasnikov Daniil <myasnikovdaniil2001@gmail.com>