Closed phvalguima closed 2 months ago
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
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: