HA status is in FAILOVER when configuring NFS ganesha with pacemaker 2.1 #3002
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
pacemaker-2.1.x changed the --timeout=$timeout-in-millisecs to --timeout=$timespec and when a bare number is used now, it is interpretted as a timeout in seconds. As a result, when waiting for a domain controller to be elected, the crmadmin waits too long, gluster/glusterd times out and the HA setup is left in an undefined state. Fixes: gluster#2997 Change-Id: Ida39a3ee5e6b4b0d3255bfef95601890afd80709 Signed-off-by: Kaleb S. KEITHLEY <kkeithle@redhat.com>
kalebskeithley
added
CB: ganesha-ha
|
/run regression |
amarts
approved these changes
Dec 3, 2021
mykaul
pushed a commit
to mykaul/glusterfs
that referenced
this pull request
Dec 3, 2021
…2.1 (gluster#3002) pacemaker-2.1.x changed the --timeout=$timeout-in-millisecs to --timeout=$timespec and when a bare number is used now, it is interpretted as a timeout in seconds. As a result, when waiting for a domain controller to be elected, the crmadmin waits too long, gluster/glusterd times out and the HA setup is left in an undefined state. Fixes: gluster#2997 Change-Id: Ida39a3ee5e6b4b0d3255bfef95601890afd80709 Signed-off-by: Kaleb S. KEITHLEY <kkeithle@redhat.com>
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.
pacemaker-2.1.x changed the --timeout=$timeout-in-millisecs to
--timeout=$timespec and when a bare number is used now, it is
interpretted as a timeout in seconds.
As a result, when waiting for a domain controller to be elected, the
crmadmin waits too long, gluster/glusterd times out and the HA setup is
left in an undefined state.
Fixes: #2997
Change-Id: Ida39a3ee5e6b4b0d3255bfef95601890afd80709
Signed-off-by: Kaleb S. KEITHLEY kkeithle@redhat.com