[patch] add test to monitor for disruption during mongo upgrade #669
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
terenceq
requested review from
durera,
andrercm,
sanjayprab and
whitfiea
as code owners
andrercm
approved these changes
Nov 30, 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.
Monitor MongoDB for Disruption During Upgrade Test
Adding a Task to the
mas-update-after-installpipeline that will invoke a test to monitor for disruption to MongoDB. The test will begin by detecting the current version of MongoDB and will exit successfully after the MongoDB version has been updated and the MongoDB instance is running.The test will tolerate up to five connection issues consecutively or up to 20 total exceptions before failing.