Bug 1861260 - Update the Push extension to add additional status check code in order to restart the pod if an error is occurring #2135
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.
This adds additional checking code to the Push extension daemon. When running the command with the
check
parameter, instead of just returning a PID as is the default, we also check to make sure the database is up and accessible. In the recent past, the database disappeared and the daemon continued to run and checkout but the log was full of MySQL connection errors. This code change allows for Kubernetes to do a liveness check and restart the POD if the daemon can no longer access the database.