Repository navigation
Commit c09cda5
committed
fix(e2e): give the kafka teardown delete its own timeout
The verify-pvc-reclaim-on-delete step deletes the Kafka CR and waits on
its finalizer, which unwinds a serial stack: the apps controller removes
the backing HelmRelease, Flux uninstalls the chart, and the Strimzi
operator terminates the broker and ZooKeeper StatefulSets and reclaims
their PVCs (deleteClaim). That is bounded, converging work, not a hang.
On the reported run the CR and its HelmRelease were both gone ~5m13s
after the delete, landing right on the suite-default 5m delete budget,
so the wait flakes on the boundary.
That default was sized for finalizer-draining CRs elsewhere (VMDisk,
FoundationDB, Tenant), so scope the fix to this step rather than widen
the global for everyone. 8m sits above the observed cost with headroom
and stays finite, so a genuine stuck uninstall still fails loudly.
Fixes #4260
Signed-off-by: Alexey Artamonov <[email protected]>1 parent 070dcb1 commit c09cda5
1 file changed
Lines changed: 14 additions & 0 deletions
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
94 | 94 | | |
95 | 95 | | |
96 | 96 | | |
| 97 | + | |
| 98 | + | |
| 99 | + | |
| 100 | + | |
| 101 | + | |
| 102 | + | |
| 103 | + | |
| 104 | + | |
| 105 | + | |
| 106 | + | |
| 107 | + | |
| 108 | + | |
| 109 | + | |
97 | 110 | | |
| 111 | + | |
98 | 112 | | |
99 | 113 | | |
100 | 114 | | |
| |||
0 commit comments