Fix user-api CrashLoopBackOff: restore config dictionary#41
Open
Fix user-api CrashLoopBackOff: restore config dictionary#41
Conversation
Fixes CrashLoopBackOff caused by commit b352481 which set config to None. Root cause: Application crashes on startup with TypeError when trying to access config["host"] because config was set to None. Impact: Pod user-api-69dd5fdb8c-lrz9t has been crashing for 8+ hours with 98+ restart attempts. Solution: Restore config dictionary with host and port values.
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
1 participant
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.
Problem
The user-api application is in CrashLoopBackOff with 98+ restarts over 8 hours.
Root Cause
Commit b352481 changed
configfrom a dictionary toNone, causing immediate crash on startup:The application tries to access
config["host"]at line 7, but config is None.Impact
user-api-69dd5fdb8c-lrz9tin namespaceuserscannot start/healthendpointSolution
Restore the config dictionary with proper host and port values:
Testing
After merge, verify pod starts successfully:
Fixes the issue introduced in commit b352481.