fix: set sbd.service timeout based on SBD_START_DELAY #169
Conversation
This file contains 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
|
[citest] |
richm
reviewed
Dec 4, 2023
richm
reviewed
Dec 4, 2023
richm
reviewed
Dec 4, 2023
richm
approved these changes
Dec 4, 2023
tomjelinek
force-pushed
the
fix-sbd-timeout
branch
from
862253c to
d7c494b
Compare
Timeout for starting the sbd.service needs to be longer than SBD_START_DELAY, otherwise the start of the sbd.service times out and prevents a cluster from starting
tomjelinek
force-pushed
the
fix-sbd-timeout
branch
from
d7c494b to
ddf0fea
Compare
|
[citest] |
richm
approved these changes
Dec 5, 2023
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.
Enhancement:
Add capability to override a timeout of sbd.service
Reason:
Timeout for starting the sbd.service needs to be longer than SBD_START_DELAY, otherwise the start of the sbd.service times out and prevents a cluster from starting
Result:
Cluster starts even when high value of SBD_START_DELAY is set
Issue Tracker Tickets (Jira or BZ if any):
https://issues.redhat.com/browse/RHEL-4684