Skip to content
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
wants to merge 1 commit into
base: 202411
Choose a base branch
from

Conversation

mssonicbld
Copy link
Collaborator

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.

Type of change

  • Bug fix
  • Testbed and Framework(new/improvement)
  • New Test case
  • Skipped for non-supported platforms
  • Test case improvement

Back port request

  • 202012
  • 202205
  • 202305
  • 202311
  • 202405
  • 202411

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

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>
@mssonicbld
Copy link
Collaborator Author

Original PR: #16916

@mssonicbld
Copy link
Collaborator Author

/azp run

Copy link

Azure Pipelines successfully started running 1 pipeline(s).

@mssonicbld
Copy link
Collaborator Author

/azp run Azure.sonic-mgmt

Copy link

Azure Pipelines successfully started running 1 pipeline(s).

@kperumalbfn
Copy link
Collaborator

/azp run

Copy link

Azure Pipelines successfully started running 1 pipeline(s).

@mssonicbld
Copy link
Collaborator Author

/azp run Azure.sonic-mgmt

Copy link

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.

@mssonicbld
Copy link
Collaborator Author

/azp run Azure.sonic-mgmt

Copy link

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.

@mssonicbld
Copy link
Collaborator Author

/azp run Azure.sonic-mgmt

Copy link

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
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants