Issue 620: Fix for pravega upgrade failure #627
Merged
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.
Signed-off-by: anishakj [email protected]
Change log description
While doing upgrade of pravega cluster, we are finding outdated pod in segment store using the pravega cluster labels. Since the controller and segment store share the same labels, outdated pod lists controller pod as well and upgrade is not happening correctly.
Purpose of the change
Fixes #620
What the code does
Corrected the labels for finding outdated pod
How to verify it
Verified that upgrade is working fine