Repository navigation
Ensure pgBackRest schedules have a running cron service - #27
Merged
Merged
Conversation
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
1 participant
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.
pgBackRest setup wrote backup and log-archive schedules without installing cron, so a host without cron could finish setup while scheduled work never ran.
Install cron after reconciling primary and standby schedules, enable it at boot, and fail setup if it is not active. Regression coverage checks both roles and ensures stale standby backup schedules are removed before cron installation.
Validation: full suite passed (367 tests, 1,113 assertions); after extracting the scheduler helper, focused pgBackRest tests passed (39 tests, 181 assertions). RuboCop and diff checks pass. The commit signature is verified.