From 1cdcbc7d6c9a38e4a616b1715720ddb77184e317 Mon Sep 17 00:00:00 2001 From: jenkins Date: Sun, 4 Oct 2026 00:55:40 -0500 Subject: [PATCH] docs: distinguish coordinator success from peer access failure --- docs/CLUSTER_STABILIZATION.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/docs/CLUSTER_STABILIZATION.md b/docs/CLUSTER_STABILIZATION.md index a09c7858..43598b51 100644 --- a/docs/CLUSTER_STABILIZATION.md +++ b/docs/CLUSTER_STABILIZATION.md @@ -80,7 +80,8 @@ replacement. No node was reflashed or rebooted during this work. template and corrects Titan-24's administrator to tethys. Both live host configs were patched without changing unrelated settings and passed Ananke validation. - [x] Verify read-only privileged actions using Ananke's own coordinator SSH - identity on all 13 affected workers, and its peer identity on 12/13/19. Both + identity on all 13 affected workers. The peer's independent SSH check on + 12/13/19 failed before sudo; that identity/known-host path is being diagnosed. Both Ananke services were restarted separately and returned active/running with zero automatic restarts. Jenkins credential-helper generation remained 796. - [ ] Resolve the remaining network/physical findings below.