Issue 357: Fix for error messages coming in operator logs #367
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
In ClearUpgradeStatus() function, we were not updating the zookeeper cluster, only the status was getting updated 2 times. Due to that again we try to update the cluster, was getting error as below.
,
Operation cannot be fulfilled on zookeeperclusters.zookeeper.pravega.io \"zookeeper\": the object has been modified; please apply your changes to the latest version and try again"
Purpose of the change
_Fixes #357
What the code does
Update the cluster instance correctly
How to verify it
Verify that during upgrade of zookeeper cluster, error messages are not coming frequently in operator logs.