Conversation
infrastructure.md covered bringing back a MariaDB/Galera cluster that had stopped completely in two sentences and one command, with no word on what to have ready or how to tell that the recovery worked. Give it its own page under the operations guide. It lists what to gather first on the manager, the MariaDB hosts and their count from osism get hosts and database_password from osism vault view, then runs osism apply mariadb-recovery and verifies the result. The check queries wsrep status on every node directly rather than through the load balancer and compares the cluster size against the inventory count, not against what a running node reports, since API success alone cannot detect a separate single-member Primary. It ends with OpenStack reads and a network create and delete from the manager. This is a routine operation, for example after a power outage, not part of restoring a backup, so the page stands on its own rather than sitting in the backup and restore material. The Recovery subsection in infrastructure.md becomes a pointer to it. Assisted-by: Claude:claude-opus-5-5 Signed-off-by: Roger Luethi <luethi@osism.tech>
✅MegaLinter analysis: Success
See detailed reports in MegaLinter artifacts Your project could benefit from a custom flavor, which would allow you to run only the linters you need, and thus improve runtime performances. (Skip this info by defining
|
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.

Gives bringing back a MariaDB/Galera cluster that stopped completely, for example after a power outage, its own page in the operations guide. The Recovery subsection in
infrastructure.mdbecomes a pointer to it.What the page covers
osism get hosts -l mariadb, anddatabase_passwordfromosism vault view.osism apply mariadb-recovery, which starts the cluster from the member with the highest Galera sequence number and joins the others to it.The page stands on its own. Recovery is a routine operation, not part of restoring a backup, so it is kept apart from the MariaDB backup and restore guide:
The two PRs touch separate parts of
infrastructure.mdand merge cleanly in either order.🤖 Generated with Claude Code