HiveDeployReliability ledger
COVERAGE (mongodb × aws)2026-10-15T17:31Zgate version v1

20_rs3_ec2_multiaz_pbm#3

FAILED
bucket:AGENTclass:localhost-exception-remote-host

evidence:

Attempt 1's fix for a split-horizon finding advertised public DNS names for the members and pointed the bootstrap's own shell at the public name, so the localhost exception no longer applied: replSetInitiate and the first createUser were refused ('requires authentication') and the set was never initiated across three repair turns, none of which saw that the shell's target host was the cause. The plan-stage layers built from 20#2 worked as designed around it: the localhost-exception gate caught that class twice before apply (repaired in-loop at zero cloud cost), every runtime verdict was named, and the progress ledger escalated after the same class recurred three times instead of grinding.

  1. date2026-10-15T17:31Z
  2. deploy statusfailed (5005s)
  3. gate––––healthz=— connection=— logs=— metrics=—
  4. teardown cleanTrue

resolution:

Fixed (d568ae78): a bootstrap that runs replSetInitiate or the first createUser through an unauthenticated shell aimed at anything but localhost is refused before plan; members may still advertise public names. Scenario 20 passed on its 30 Oct re-run.

Recorded reason (scrubbed)

ladder exhausted (auto-repair gave up)