Andrei Kvapil 330acfe6e2 fix(e2e): widen tenant node-join deadline to 18m ...

The kubernetes-latest and kubernetes-previous suites flaked on the
worker node-join wait under host load. In run 30260770694 both failed at
exactly 12m with zero tenant Nodes registered and the tenant cilium HR
still mid-install: a transient drbd.linbit.com/lost-quorum taint delayed
the worker DataVolume imports, so the KubeVirt VMIs were only created ~2m
into this wait and the guests then had ~10m to import Talos, boot,
register a kubelet and let cilium turn the nodes Ready.

This single deadline absorbs the entire worker bring-up (the
machinedeployment replicas=2 gate clears before the VMIs even exist), so
under storage pressure 12m is too tight. A less-loaded fleet run passed
both suites unchanged, confirming load-induced slowness rather than a
stuck bring-up. Widen the deadline to 18m, which restores margin and
still sits well inside the 40m chainsaw step timeout.

Assisted-By: Claude <noreply@anthropic.com>
Signed-off-by: Andrei Kvapil <andrei.kvapil@aenix.io>

2026-07-28 17:48:40 +02:00

..

etcd-cleanup.sh

test(e2e): address review nits — shellcheck directive + ports-workaround TODO

2026-07-10 17:02:46 +05:00

etcd-probe.sh

test(etcd): stop losing the metrics probe's output to the attach race

2026-07-19 20:16:01 +03:00

remediation-guard.sh

test(e2e): address review nits — shellcheck directive + ports-workaround TODO

2026-07-10 17:02:46 +05:00

run-kubernetes.sh

fix(e2e): widen tenant node-join deadline to 18m

2026-07-28 17:48:40 +02:00

talos-image-cache.sh

test(e2e): address review nits — shellcheck directive + ports-workaround TODO

2026-07-10 17:02:46 +05:00