Myasnikov Daniil 00c6eb18bf docs(e2e): name the container lane's one-per-host limit ...

SANDBOX_NAME is per-checkout and these are not, which reads like an
oversight until you notice that hack/e2e-compose.yaml's container names
and the data-srvN zpools are global too. Two checkouts on one host
therefore share nodes and pools, and the second one's teardown destroys
the first one's storage.

Recorded rather than fixed. CI cannot reach it -- the lane already asks
for 24 vCPU and 72 GiB against a 32 vCPU / 128 GiB runner, so a second
one does not fit beside it -- and isolating it properly means renaming
the pools, which the LINSTOR storage-pool registration reads.

Signed-off-by: Myasnikov Daniil <myasnikovdaniil2001@gmail.com>
Assisted-By: LLM

2026-09-05 14:51:06 +05:00

..

images/e2e-sandbox

test(e2e): migrate app suite from BATS to Chainsaw and wire into CI (#2826)

2026-07-12 11:58:08 +05:00

Chart.yaml

[testing] Add aliases and autocomplete

2026-01-05 16:29:39 +03:00

Makefile

docs(e2e): name the container lane's one-per-host limit

2026-09-05 14:51:06 +05:00

values.yaml

Prepare release v1.6.0 (promoted from v1.6.0-rc.4)

2026-07-22 13:00:10 +00:00