titan/atlas-iac
3
0
Fork 0
Code Issues Pull Requests 9 Actions Packages Projects Releases Wiki Activity

docs: distinguish coordinator success from peer access failure

Browse Source
This commit is contained in:
jenkins 2026-10-04 00:55:40 -05:00
parent d7dd48eee2
commit 1cdcbc7d6c
1 changed files with 2 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

3
docs/CLUSTER_STABILIZATION.md
View File

@ -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 template and corrects Titan-24's administrator to tethys. Both live host configs
were patched without changing unrelated settings and passed Ananke validation. were patched without changing unrelated settings and passed Ananke validation.
- [x] Verify read-only privileged actions using Ananke's own coordinator SSH - [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 Ananke services were restarted separately and returned active/running with
zero automatic restarts. Jenkins credential-helper generation remained 796. zero automatic restarts. Jenkins credential-helper generation remained 796.
- [ ] Resolve the remaining network/physical findings below. - [ ] Resolve the remaining network/physical findings below.