Lezama telemetry repoint: DSN still targets dead whey-tunnel 172.30.0.1; decide venus-PG repoint vs retire. Step 1 (nw-lezama): test TCP 91.99.136.171:5432 from lezama (GCABA egress 80/443-only suspected). Open->repoint DSN + nw-venus pg_hba grant for lezama egress (IP rotates - needs range or hostssl). Blocked->Elazar governance call (retire lezama telemetry writes vs spool-sync) per Lezama-RESTRICTED policy. Interim: JSONL spool = no data loss; nw-lezama stops sys-check.timer if erroring hard. Also: whey pg_hba:136 dead 172.30.0.2/32 telemetry_rw line - nw-whey pulls it whichever branch wins.

Sub-tickets

Activity

• wi-cli-whey created · 2026-07-02
• wi-cli-whey commented · 2026-07-02
  lezama test: 91.99.136.171:5432 BLOCKED (GCABA egress 80/443-only, confirmed by nc timeout). Interim safe: metrics_write fails-soft, no spool yet created, sys-check clean. Elazar DMed with recommendation: retire lezama telemetry writes (nw-lezama concurs). Awaiting retire/keep.
• wi-cli-whey blocked · 2026-07-02
  awaiting Elazar retire/keep call
• wi-cli-whey completed · 2026-07-02
  Elazar ruling (via pm-llmmsgsrv, SAVETOKE-34): retire — no repoint. Lezama telemetry writers stop entirely; nw-lezama removes timer/DSN, nw-whey pulls stale pg_hba 172.30.0.2/32 line. Fleet-wide telemetry retirement continues under SAVETOKE-34.
• wi-cli-venus unblocked · 2026-08-19
  backfill: blockedReason cleared on a closed row; it described a dependency discharged before the item closed and pre-dated the d6153e2 fix that now clears it automatically (Elazar decision 1b, 2026-08-19)