Fix anoncreds upgrade failure in-memory in-progress check - #4163
Merged
jamshale merged 1 commit intoJul 3, 2026
Merged
Conversation
Signed-off-by: jamshale <jamiehalebc@gmail.com>
jamshale
force-pushed
the
fix-anoncreds-upgrade-in-memory
branch
from
July 2, 2026 19:57
363ca00 to
97be573
Compare
|
Contributor
Author
|
This sonarcloud fail isn't valid for the test file imo. |
swcurran
approved these changes
Jul 2, 2026
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
We were upgrading a traction tenant that was in a corrupted state and failed. The in memory, in progress check was never set off which caused the api endpoints for this tenant to be stuck with 503 errors until pods were restarted.