chore(mayastor): regenerate DiskPools for the current worker set #158
Loading…
Reference in a new issue
No description provided.
Delete branch "chore/diskpool-b6ceba"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
seanfarm-worker-d87376 was replaced by seanfarm-worker-b6ceba (remove-then-add, no N+1). This drops the DiskPool for the old node and adds one for the new node so Mayastor can rebuild the five degraded volumes onto it.
Generated with the logic of
scripts/regen-diskpools.shagainst the live amd64 platform worker list, shipped through Forgejo instead of the script's direct codeberg push so the admission gate sees it.After Flux applies:
pool-seanfarm-worker-b6cebacomes Online, then the stalepool-seanfarm-worker-d87376gets retired through the Mayastor REST API (k3s-remove-node.sh Phase 8).https://claude.ai/code/session_01LeVatedQ4sCA1u6LHjo7B5