20_rs3_ec2_multiaz_pbm#2
FAILEDAttribution
20_rs3_ec2_multiaz_pbm_2.mdMDevidence:
The bootstrap guarded every createUser with a getUser lookup through the localhost shell before authorization was enabled; usersInfo is not permitted there, so none of the five principals (application, backup, exporter, probe, role) was ever created, and once authorization switched on every client was refused with code 334. The ladder first met rs-not-initiated three times (a member-certificate name mismatch, fixed at attempt 4), counted the three identical verdicts as three distinct findings because the driver's volatile topology description sat inside the signature, and escalated at attempt 5 before it reached the user defect. The harness then missed the ladder's give-up marker and redeployed blind four times (about an hour).
- date2026-10-14T15:17Z
- deploy statusfailed (8935s)
- gate––––healthz=— connection=— logs=— metrics=—
- teardown cleanTrue
resolution:
Fixed (2931a391): a data-layer verdict is the ladder's finding signature (same class, same finding), a pre-plan gate refuses a check-then-create through the localhost exception, hard rule §13 says so, and the harness reads the give-up marker inside its claim window. Scenario 20 passed on its 30 Oct re-run.
Recorded reason (scrubbed)
(none recorded)