make DB bad connection error message more specific #598
Conversation
This file contains 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
|
Hi @KubeKyrie, DetailsInstructions for interacting with me using comments are available here. |
Signed-off-by: KubeKyrie <qinshao2009@outlook.com>
KubeKyrie
force-pushed
the
enhance-db-error
branch
from
db30b1d
to
035d5c9
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
What type of PR is this?
/kind feature
What this PR does / why we need it:
make DB bad connection error message more specific and make it easier for people who are not familiar with DB error to troubleshoot.
Which issue(s) this PR fixes:
Fixes # NONE
Special notes for your reviewer:
Does this PR introduce a user-facing change?: