This repository has been archived by the owner on Jul 25, 2022. It is now read-only.
Fix Vbox fencing #2342
Merged
Fix Vbox fencing #2342
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
Fencing is currently broken for vagrant installs. This appears to be because the fence agent tries to use node.local as the node to fence, but this does not coorespond to any vm name. Instead it should use just node. Signed-off-by: Joe Grund <jgrund@whamcloud.io>
johnsonw
previously approved these changes
Oct 21, 2020
ip1981
previously approved these changes
Oct 21, 2020
utopiabound
previously approved these changes
Oct 22, 2020
…osync relations. Signed-off-by: Joe Grund <jgrund@whamcloud.io>
jgrund
dismissed stale reviews from utopiabound, ip1981, and johnsonw
via
c838137
ip1981
approved these changes
Oct 22, 2020
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Fencing is currently broken for vagrant installs.
This appears to be because the fence agent tries to use node.local as
the node to fence, but this does not coorespond to any vm name.
Instead it should use just node.
Signed-off-by: Joe Grund jgrund@whamcloud.io
This change is