Most testgrid jobs are failing due to connection refused to ghproxy.default.svc.cluster.local (cla, stale/rotten issues, etc.)

kubernetes / test-infra

Test infrastructure for the Kubernetes project.

Apache License 2.0

3.82k stars 2.63k forks source link

Most testgrid jobs are failing due to connection refused to ghproxy.default.svc.cluster.local (cla, stale/rotten issues, etc.) #31618

Closed nojnhuh closed 7 months ago

nojnhuh commented 7 months ago

What happened:

Most of the triage-robot's jobs have been failing consistently for at least the last few weeks. I think failures go back to around 21 July 2023 based on searching all of GitHub for stale issue comments: https://github.com/issues?q=commenter%3Ak8s-triage-robot+%22After+30d+of+inactivity+since%22+

Every failure looks more or less like:

2024/01/12 22:20:30 main.go:206: Failed run: search failed: Get "http://ghproxy.default.svc.cluster.local/search/issues?...": dial tcp 10.7.254.218:80: connect: connection refused

What you expected to happen:

The jobs pass.

How to reproduce it (as minimally and precisely as possible):

Please provide links to example occurrences, if any:

https://testgrid.k8s.io/sig-contribex-k8s-triage-robot

e.g. https://prow.k8s.io/view/gs/kubernetes-jenkins/logs/ci-k8s-triage-robot-stale-issues/1745931646969843712

Anything else we need to know?:

nojnhuh commented 7 months ago

/sig contribex

k8s-ci-robot commented 7 months ago

@nojnhuh: The label(s) sig/contribex cannot be applied, because the repository doesn't have them.

In response to [this](https://github.com/kubernetes/test-infra/issues/31618#issuecomment-1890073681): >/sig contribex Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes/test-infra](https://github.com/kubernetes/test-infra/issues/new?title=Prow%20issue:) repository.

nojnhuh commented 7 months ago

/sig testing

aojea commented 7 months ago

21 July 2023

this is a long time, @BenTheElder @ameukam rings a bell?

ameukam commented 7 months ago

21 July 2023

this is a long time, @BenTheElder @ameukam rings a bell?

Looks ghproxy is done in the cluster involved. I'll take a look next week is no one beats me to it.

nojnhuh commented 7 months ago

@ameukam Have you had a chance to take a look at this?

ameukam commented 7 months ago

@nojnhuh https://github.com/kubernetes/k8s.io/pull/6296 should hopefully fix this. Thank you for reporting this.

nojnhuh commented 7 months ago

I see a number of green runs in a row now. Thanks!

/close

k8s-ci-robot commented 7 months ago

@nojnhuh: Closing this issue.

In response to [this](https://github.com/kubernetes/test-infra/issues/31618#issuecomment-1899791255): >I see a number of green runs in row now. Thanks! > >/close Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes/test-infra](https://github.com/kubernetes/test-infra/issues/new?title=Prow%20issue:) repository.