-
Notifications
You must be signed in to change notification settings - Fork 94
[crmsh-5.0] Dev: sbd: Improve the process of leveraging maintenance mode #1951
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: crmsh-5.0
Are you sure you want to change the base?
[crmsh-5.0] Dev: sbd: Improve the process of leveraging maintenance mode #1951
Conversation
Codecov Report❌ Patch coverage is
Additional details and impacted files
Flags with carried forward coverage won't be shown. Click here to find out more.
☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
c7c42b1 to
6258cfc
Compare
6258cfc to
e753ef7
Compare
0f33eb9 to
6fb23e1
Compare
- Drop the function `restart_cluster_if_possible` - Introduced a new function `utils.able_to_restart_cluster` to check if the cluster can be restarted. Call it before changing any configurations. - Add leverage maintenance mode in `sbd device remove` and `sbd purge` commands
And give error if the option is not crashdump
f712baa to
7c277c9
Compare
| logger.warning("Please stop all running resources and try again") | ||
| logger.warning("Or use 'crm -F/--force' option to leverage maintenance mode") | ||
| logger.warning("Understand risks that running RA has no cluster protection while the cluster is in maintenance mode and restarting") | ||
| logger.info("INFO: Aborting the configuration change attempt") |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why is this line different with #1950?
Backport from #1950