The diagnostic snapshot captured on a failed e2e run spawns a
privileged debug pod per node for its host-log leg. Baseline
PodSecurity rejects every such pod with a 403, and crust-gather's
retry loop keeps trying until it burns the entire --duration budget,
then exits 1 with a deadline error. The snapshot verdict therefore
printed FAILED on every failure capture even though the namespaced
object state had been collected, and the host-log leg itself gathered
nothing usable here.
Pass --disable-additional-logs at all three collect sites: the host
snapshot from the BATS runner, the host snapshot from the Chainsaw
error.catch, and the nested tenant snapshot. The object collection now
finishes cleanly, the happy path reports complete, and FAILED once
again means a genuine collection failure.
Assisted-By: Claude <noreply@anthropic.com>
Signed-off-by: Aleksei Sviridkin <f@lex.la>
Aleksei Sviridkin
8a44b3e408