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

redis.exceptions.ConnectionError: Error 99 connecting to localhost:6379. Cannot assign requested address. #107

Closed
mgheorghe opened this issue May 5, 2023 · 2 comments
Assignees
Labels
bug Something isn't working

Comments

@mgheorghe
Copy link

nice to have not critical issue
but if run.sh and then exec are executed one after the other all cases will fail with
redis.exceptions.ConnectionError: Error 99 connecting to localhost:6379. Cannot assign requested address.

if we wait 10sec or so between the commands than it it will pass
i assume run.sh does not wait for redis service to start

i believe docker allows a health check and will be good to add one

or try the commands from https://github.com/opencomputeproject/SAI-Challenger/blob/main/docs/standalone_mode.md
./run.sh -a trident2 -t saivs
./exec.sh -t saivs pytest --testbed=saivs_standalone -v -k api/test_vlan.py

this is needed because of #99
ERROR api/test_vlan.py::TestSaiVlan::test_vlan_create - AssertionError: SyncD has not started yet...
whenever a test fails and causes syncd to go in a bad state we need to restart the containers and rerun next test.

@akokhan
Copy link
Contributor

akokhan commented May 11, 2023

@mgheorghe , this issue is expected to be fixed in the latest main branch.

@andriy-kokhan
Copy link
Contributor

Expected to be resolved by PR #110 . Please feel free to reopen if still see the issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

4 participants