Files
cozystack/hack/e2e-chainsaw/_lib/leak-allowlist.txt
T
Aleksei Sviridkin c5cd21af96 test(e2e): fail the suite whose pods outlive its cleanup
A Chainsaw suite could pass while its workloads kept running after its
own cleanup: brokers of Kafka releases whose application was deleted,
a TenantControlPlane stuck on its finalizer holding its apiserver pods.
Nothing noticed until a later suite failed on Insufficient memory,
hours on and under the wrong name.

Chainsaw v0.2.15 has no hook after a test's cleanup, so the suite now
runs one `chainsaw test` per suite directory and checks between them.
A pod is charged to the suite when it is not terminal, did not exist
before the suite, and the root of its ownerReferences chain was created
at or after the suite started on the apiserver's clock. That leaves
alone a platform pod a rollout, an eviction or a crash replaces
mid-suite, though not one whose platform object is itself recreated
mid-suite. Charged pods get the default cleanup timeout of the chainsaw
configuration, five minutes, counted from the moment chainsaw returns;
past that the run names the suite, each pod and its root, and fails.
A timeout or a spent budget takes the verdict from the last good pod
list; any other read failure before then stops the wait and is
reported as inconclusive rather than as a leak; a failed first reading
after the suite leaves it unchecked, and it fails.

The runner hands chainsaw the tests a single invocation would discover
and merges the per-suite JUnit reports into the chainsaw-report.xml
the workflows already collect. Suites with a filed leak are exempt by
an allowlist that must name existing suite directories, so a rename
cannot keep an exemption alive.

Assisted-by: LLM
Signed-off-by: Aleksei Sviridkin <f@lex.la>
2026-09-26 15:06:42 +03:00

16 lines
803 B
Plaintext

# Suites whose leaked pods hack/e2e-chainsaw-run.sh reports as a warning
# instead of failing the suite. One line per suite directory:
#
# <suite-dir> <issue-ref>
#
# Every entry has to name an existing suite directory, or the run stops before
# the first suite. An entry exempts the whole suite, so any new leak in it is
# hidden too until the line goes: the PR that fixes the issue deletes the line.
#
# A TenantControlPlane can sit on its finalizer after the Kubernetes application
# is deleted, holding its apiserver pods. Both suites create one through
# hack/e2e-chainsaw/_lib/run-kubernetes.sh; the stuck finalizer was seen in
# kubernetes-latest only, but nothing in the defect is specific to that suite.
kubernetes-latest cozystack/cozystack#4489
kubernetes-previous cozystack/cozystack#4489