Closed anishakj closed 1 year ago
Base: 82.87% // Head: 82.75% // Decreases project coverage by -0.12%
:warning:
Coverage data is based on head (
eb5d671
) compared to base (4d2f367
). Patch coverage: 0.00% of modified lines in pull request are covered.
:umbrella: View full report at Codecov.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.
Signed-off-by: anisha.kj anisha.kj@dell.com
Change log description
Pravega cluster upgrade is failing in certain cases. In failed scenarios, while deleting the pod, we are getting error pod not found. Due to that error upgrade status is set to failure and due to that subsequent upgrade of pods is not happening
Purpose of the change
Fixes #643
What the code does
Made changes to not return error in the case of pod deletion fails with pod not found error. This ensures that remaining pods can be upgraded successfully.
How to verify it
Verified upgrade of pravega cluster multiple times and is successful