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

[Failing Test] [sig-network] ci-kubernetes-e2e-gci-gce-nftables #124437

Closed
pacoxu opened this issue Apr 22, 2024 · 2 comments · Fixed by kubernetes/test-infra#32485
Closed

[Failing Test] [sig-network] ci-kubernetes-e2e-gci-gce-nftables #124437

pacoxu opened this issue Apr 22, 2024 · 2 comments · Fixed by kubernetes/test-infra#32485
Assignees
Labels
kind/failing-test Categorizes issue or PR as related to a consistently or frequently failing test. needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. sig/network Categorizes an issue or PR as relevant to SIG Network.

Comments

@pacoxu
Copy link
Member

pacoxu commented Apr 22, 2024

Which jobs are failing?

ci-kubernetes-e2e-gci-gce-nftables

Which tests are failing?

  • Kubernetes e2e suite [It] [sig-network] Services should fallback to local terminating endpoints when there are no ready endpoints with externalTrafficPolicy=Local
  • and more

Since when has it been failing?

Since this job is created.

Testgrid link

https://testgrid.k8s.io/sig-network-gce#periodic-network-nftables,%20google-gce

Reason for failure (if possible)

{ failed [FAILED] Timed out in 30s: successfully executed curl -i -q -s --connect-timeout 1 http://localhost:10256/healthz in nettest-4395/host-test-container-pod, but output 'HTTP/1.1 503 Service Unavailable
Content-Type: application/json
X-Content-Type-Options: nosniff
Date: Mon, 22 Apr 2024 07:29:36 GMT
Content-Length: 170

{"lastUpdated": "2024-04-22 07:21:24.170926334 +0000 UTC m=+18.018966905","currentTime": "2024-04-22 07:29:36.090882948 +0000 UTC m=+509.938923505", "nodeEligible": true}' doesn't contain expected string '200 OK'
In [It] at: k8s.io/kubernetes/test/e2e/framework/network/utils.go:547 @ 04/22/24 07:29:38.139
}

https://prow.k8s.io/view/gs/kubernetes-jenkins/logs/ci-kubernetes-e2e-gci-gce-nftables/1782306811529924608

Anything else we need to know?

part of #122572?

Relevant SIG(s)

/sig network
/cc @danwinship

@pacoxu pacoxu added the kind/failing-test Categorizes issue or PR as related to a consistently or frequently failing test. label Apr 22, 2024
@k8s-ci-robot k8s-ci-robot added sig/network Categorizes an issue or PR as relevant to SIG Network. needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. labels Apr 22, 2024
@k8s-ci-robot
Copy link
Contributor

This issue is currently awaiting triage.

If a SIG or subproject determines this is a relevant issue, they will accept it by applying the triage/accepted label and provide further guidance.

The triage/accepted label can be added by org members by writing /triage accepted in a comment.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@aojea
Copy link
Member

aojea commented Apr 22, 2024

Discussed in https://kubernetes.slack.com/archives/C09QYUH5W/p1713628805680269

The COS images does not have the necessary kernel modules so it fails and causes other test to fail ... I need to change the OS image or see how long the COS team can release a new image with the necessart modules

/assign @aojea

This is on my plate now

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/failing-test Categorizes issue or PR as related to a consistently or frequently failing test. needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. sig/network Categorizes an issue or PR as relevant to SIG Network.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants