This repository has been archived on 2026-07-30. You can view files and clone it. You cannot open issues or pull requests or push a commit.

beatzaplentyandClaude Sonnet 4.6 fe9fc7364b fix(ha/cluster-init): explicitly start pacemaker after corosync restart ...

At first boot, pacemaker fails with 'Dependency failed' because ipa-activation
fails (IPA not enrolled yet) before corosync/authkey are ready, causing a
systemd boot-ordering race.  The service recovers fine when started manually.
Add an explicit 'systemctl start pacemaker' on both nodes immediately after
restarting corosync so cluster-init doesn't time out waiting for it.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01HaH1cSGvhogRP5ExoF6nD8

2026-07-28 19:47:33 +10:00

..

acceptance-tests.sh

fix(ha): all 7 acceptance tests pass — targetctl, fencing, failover, data integrity

2026-07-28 19:03:39 +10:00

cluster-enable-stonith.sh

feat(ha): promote HA file server to production flake targets

2026-07-27 11:26:37 +10:00

cluster-init.sh

fix(ha/cluster-init): explicitly start pacemaker after corosync restart

2026-07-28 19:47:33 +10:00

deploy.sh

fix(ha/deploy): remove _patch_targetctl — iscsi-target.nix now correct

2026-07-28 19:41:20 +10:00

fence-pve-ssh.py

feat(ha): promote HA file server to production flake targets

2026-07-27 11:26:37 +10:00