# 24_det_single_vm_uswest2#1 — FAILED | field | value | |---|---| | campaign | COVERAGE (mongodb × aws) | | archetype | deterministic | | date | 2026-10-13T17:37Z | | gate version | v1 | | deployment | dep-8209a5f2 | | deploy status | healthy (565s) | | gate | healthz=✓ connection=✓ logs=✗ metrics=✗ | | teardown clean | True | ## Attribution - **bucket:** PLATFORM - **class:** single-shot-region-dropped - **evidence:** The ask named us-west-2; the single-shot template match assembled the spec with the account's default region (us-east-1). The database deployed healthy and connectable in us-east-1 while the gate looked for logs and metrics in us-west-2 — the scenario exists to test exactly this. - **resolution:** Fixed (f5ab5416): a region the user names wins over the account default on the single-shot route. Proven live by 24#2 and 24#3 (logs and metrics in us-west-2) and by the 26 Oct re-run of this slot, which passed all four legs. ## Recorded reason (scrubbed) ``` gate failed: {"logs": "log groups exist but carry no entries: ['/mongodb/dep-8209a5f2-ypd54j/mongod']", "metrics": "no datapoints for ['i-0bbab4105d80fcc8b']"} ```