(PE-40162) XL PE approach to CI #540
Closed
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
CI test for XL PE setup with server replica (I used .github folder based on where other files were, I can move the file elsewhere if needed)
CoMfUcIoS
reviewed
Jan 28, 2025
CI test for XL PE setup with server replica (I used .github folder based on where other files were, I can move the file elsewhere if needed)
…bs/puppetlabs-peadm into PE-40162-approach-to-CI
…extra tests when testing the file this PR adds
B00885424
force-pushed
the
PE-40162-approach-to-CI
branch
from
1461a1b to
054b2de
Compare
…isioning a single node as the backup
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.
Summary
CI test for XL PE setup with server replica. Provision node, then provision a second VM to act as replacement for failed node (I used .github folder based on where other files were, I can move the file elsewhere if needed)
Additional Context
Add any additional context about the problem here.
Related Issues (if any)
Mention any related issues or pull requests.
Checklist
Changes include test coverage?
Have you updated the documentation?