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 Job] gce-cos jobs started failing #129305

Open
aojea opened this issue Dec 19, 2024 · 5 comments
Open

[Failing Job] gce-cos jobs started failing #129305

aojea opened this issue Dec 19, 2024 · 5 comments
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

@aojea
Copy link
Member

aojea commented Dec 19, 2024

https://prow.k8s.io/view/gs/kubernetes-ci-logs/logs/ci-kubernetes-e2e-gce-cos-k8sstable1-ingress/1869575322135957504
https://testgrid.k8s.io/sig-network-gce#gce-cos-1.12-ingress

It seems it started to fail around 23:15 CET on Dec 18

image

It is not clear looking at the logs the problem, seems something related to the cluster start

https://prow.k8s.io/view/gs/kubernetes-ci-logs/logs/ci-kubernetes-e2e-gce-cos-k8sstable1-ingress/1869514923629875200

/sig networking
/kind failing-test

@k8s-ci-robot
Copy link
Contributor

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

In response to this:

https://prow.k8s.io/view/gs/kubernetes-ci-logs/logs/ci-kubernetes-e2e-gce-cos-k8sstable1-ingress/1869575322135957504
https://testgrid.k8s.io/sig-network-gce#gce-cos-1.12-ingress

It seems it started to fail around 23:15 CET on Dec 18

image

It is not clear looking at the logs the problem, seems something related to the cluster start

https://prow.k8s.io/view/gs/kubernetes-ci-logs/logs/ci-kubernetes-e2e-gce-cos-k8sstable1-ingress/1869514923629875200

/sig networking
/kind failing-test

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-sigs/prow repository.

@k8s-ci-robot k8s-ci-robot added kind/failing-test Categorizes issue or PR as related to a consistently or frequently failing test. needs-sig Indicates an issue or PR lacks a `sig/foo` label and requires one. needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. labels Dec 19, 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-sigs/prow repository.

@aojea
Copy link
Member Author

aojea commented Dec 19, 2024

/sig network

@k8s-ci-robot k8s-ci-robot added sig/network Categorizes an issue or PR as relevant to SIG Network. and removed needs-sig Indicates an issue or PR lacks a `sig/foo` label and requires one. labels Dec 19, 2024
@kannon92
Copy link
Contributor

Cloud controller manager has a lot of interesting logs. Not sure if it is related.

https://storage.googleapis.com/kubernetes-ci-logs/logs/ci-kubernetes-e2e-gce-cos-k8sstable1-ingress/1869575322135957504/artifacts/test-519f5e2df7-master/cloud-controller-manager.log

Looks like something is calling the cloud controller manager with bad parameters.

@kannon92
Copy link
Contributor

I looked at a successful job and it has the same kind of logs. I don't think this is related.

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

No branches or pull requests

3 participants