-
Notifications
You must be signed in to change notification settings - Fork 39.9k
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
Comments
@aojea: The label(s) In response to this:
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. |
This issue is currently awaiting triage. If a SIG or subproject determines this is a relevant issue, they will accept it by applying the The 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. |
/sig network |
Cloud controller manager has a lot of interesting logs. Not sure if it is related. Looks like something is calling the cloud controller manager with bad parameters. |
I looked at a successful job and it has the same kind of logs. I don't think this is related. |
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
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
The text was updated successfully, but these errors were encountered: