Aleksei Sviridkin 393592a308 test(e2e): lower the seaweedfs volume size limit on a live instance ...

Every existing case installs SeaweedFS at one limit and stays there, so
nothing walks the transition an operator makes when lowering it: each
volume at or above the new value leaves the writable set and the bucket
writes again only after a grow. The failure is a PUT that times out
while every release stays Ready, so the suite ends on a write into a
bucket filled between the two limits.

The suite runs its own instance, created directly so the limit can move
without racing the tenant module, and asserts on the live master that
the value set on the resource arrives with the growth counts intact.

seaweedfs changes now select the suite, which the selector's mapping
and its tests are updated for.

Assisted-by: LLM
Signed-off-by: Aleksei Sviridkin <f@lex.la>

2026-10-02 07:22:42 +03:00

..

bucket.yaml

test(e2e): lower the seaweedfs volume size limit on a live instance

2026-10-02 07:22:42 +03:00

chainsaw-test.yaml

test(e2e): lower the seaweedfs volume size limit on a live instance

2026-10-02 07:22:42 +03:00

seaweedfs.yaml

test(e2e): lower the seaweedfs volume size limit on a live instance

2026-10-02 07:22:42 +03:00