CLOUD-46: Fix 'exit 1' on replset-init of restarted CR w/existing PVC data #226
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.
This fixes a problem where the operator fails to initiate a replset that was already initiated before CR creation time. We should skip and exit 0, but instead we exit 1 with a "not master" error.
The fix ensures the replset config is loaded from the session before .IsInitiated() is called to check if the replset was already initiated here:
mongodb-orchestration-tools/controller/replset/initiator.go
Lines 60 to 62 in 9068d0e
Without this PR this ^^^ block is getting skipped.