Aleksei Sviridkin e441edc2aa test(e2e): stop the mongodb backup suite before the restore leg ...

A to-copy restore replays the source cluster's system users into the
target, so the target's own generated credentials stop authenticating
and the harness cannot read the sentinel back out of the restored copy.
The suite has never passed for that reason, holding the in-tree e2e run
red on every branch that selects it.

Drive run-all.sh with SKIP_RESTORE=1 so the suite still proves the
backup half end to end, and pin the skip by asserting the skip branch's
own log line: exit zero alone is also what a completed round-trip
returns, so without that assertion the step could not tell a skipped
flow from a full one, nor notice SKIP_RESTORE failing to reach the
harness.

The to-copy manifest and the example README both stated that CI covers
the restore, which stops being true here, so both now say where
coverage ends. The asserted log line is annotated at its source, since
rewording it would red the suite with a bare match failure.

Coverage returns by dropping SKIP_RESTORE together with the assertion
on that line, once the credential handling behind the restore is
fixed.

Assisted-By: Claude <noreply@anthropic.com>
Signed-off-by: Aleksei Sviridkin <3811295@gmail.com>

2026-08-14 21:18:09 +03:00

..

chainsaw-test.yaml

test(e2e): stop the mongodb backup suite before the restore leg

2026-08-14 21:18:09 +03:00

mongodb.yaml

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

2026-06-25 13:42:34 +05:00