-
Notifications
You must be signed in to change notification settings - Fork 790
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[action] [PR:16916] chore: add sleep to wait for redis to be ready #16921
Open
mssonicbld
wants to merge
1
commit into
sonic-net:202411
Choose a base branch
from
mssonicbld:cherry/202411/16916
base: 202411
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
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
Description of PR Summary: Fixes # (issue) After database service is ready, we observe that redis is not connectable yet and showed RuntimeError: Unable to connect to redis - Connection refused(1): Cannot assign requested address As a result, adding some delays here to ensure this will be available before running show command. Approach What is the motivation for this PR? Described above How did you do it? Added some sleep of 1 minute to ensure database is ready to connect How did you verify/test it? Verified on T2 Signed-off-by: Austin Pham <austinpham@microsoft.com>
11 tasks
Original PR: #16916 |
/azp run |
Azure Pipelines successfully started running 1 pipeline(s). |
/azp run Azure.sonic-mgmt |
Azure Pipelines successfully started running 1 pipeline(s). |
/azp run |
Azure Pipelines successfully started running 1 pipeline(s). |
/azp run Azure.sonic-mgmt |
Azure Pipelines will not run the associated pipelines, because the pull request was updated after the run command was issued. Review the pull request again and issue a new run command. |
/azp run Azure.sonic-mgmt |
Azure Pipelines will not run the associated pipelines, because the pull request was updated after the run command was issued. Review the pull request again and issue a new run command. |
/azp run Azure.sonic-mgmt |
Azure Pipelines successfully started running 1 pipeline(s). |
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.
Description of PR
Summary:
Fixes # (issue)
After database service is ready, we observe that redis is not connectable yet and showed
As a result, adding some delays here to ensure this will be available before running show command.
Type of change
Back port request
Approach
What is the motivation for this PR?
Described above
How did you do it?
Added some sleep of 1 minute to ensure database is ready to connect
How did you verify/test it?
Verified on T2
Any platform specific information?
Supported testbed topology if it's a new test case?
Documentation