-
Notifications
You must be signed in to change notification settings - Fork 9
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
[self-hosted] Microceph setup fixture often fails with: "error to connect to http://localhost/testbucket" #171
Labels
bug
Something isn't working
Comments
Posting in https://chat.canonical.com/canonical/channels/github-actions-self-hosted-runners, since it appears to be an issue with self-hosted runners I believe aproxy is supposed to be configured on the self-hosted runners so that no changes are needed on our end with regards to the proxy |
phvalguima
added a commit
that referenced
this issue
May 7, 2024
Check the microceph status before continuing with the fixture code. Closes #171
carlcsaposs-canonical
added a commit
that referenced
this issue
May 8, 2024
Fixes #171 (on self-hosted runners, microceph is not ready before we create bucket)
carlcsaposs-canonical
added a commit
that referenced
this issue
May 14, 2024
Fixes #171 (on self-hosted runners, microceph is not ready before we create bucket)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
We have two types of backup tests: 2x runners as self-hosted (bigger VMs) to run the large-deployments; and 2x runners as GH-hosted for the small-deployments in OpenSearch.
The self-hosted runners are often failing in the microceph setup. One example: https://github.com/canonical/opensearch-operator/actions/runs/8959102660/job/24604651827
The error rate is often enough (last 2x runs I executed, 3 of 4 tests for backup with self-hosted failed with this error).
Given this error is only observed on self-hosted, I believe it has to do with the
NO_PROXY
settings. Generally, we must have in our no-proxy setup something like:This ensures the host will not forward local-bound traffic to the proxy and instead resolve within the host.
The full stack trace is:
The text was updated successfully, but these errors were encountered: