ci-operator/jobs/openshift/ovn-kubernetes: Move master presubmits to build01 #12386
Conversation
wking
force-pushed
the
ovn-kube-build01
branch
from
02ed594 to
b2271d3
Compare
|
e2e-gcp-ovn is the job where we see the i/o timeout the most. I would say 80-90% of the time. So focus on that one. |
…build01 We're seeing errors like [1]: INFO: Unexpected error listing nodes: Get "https://api.ci-op-t47nsmsc-99b10.origin-ci-int-gce.dev.openshift.com:6443/api/v1/nodes?fieldSelector=spec.unschedulable%3Dfalse&resourceVersion=0": dial tcp 35.231.18.254:6443: i/o timeout in CI jobs running on build02, and are wondering if these are related to the host cluster. Move some highly-impacted jobs over to build01 to see if that impacts the error rate. Generated by editing core-services/sanitize-prow-jobs/_config.yaml and running 'make jobs'. [1]: https://prow.ci.openshift.org/view/gs/origin-ci-test/pr-logs/pull/openshift_ovn-kubernetes/297/pull-ci-openshift-ovn-kubernetes-master-e2e-gcp-ovn/1311628791914696704#1:build-log.txt%3A19
wking
force-pushed
the
ovn-kube-build01
branch
from
b2271d3 to
2f517e1
Compare
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: wking The full list of commands accepted by this bot can be found here. DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
|
From the first round of rehearsals, gcp-ovn passed. The only failures were ovn-hybrid-step-registry, operator-with-custom-vxlan-port, and openstack, which all died on install. I dunno how reliable those tests are outside of the hypothetical build02 connectivity issue. I've pushed b2271d3986 -> 2f517e1, pivoting from |
|
@wking the ovn-hybrid-step-registry job is AWS and usually stable. openstack never usually passes, and e2e-operator-with-custom-vxlan-port takes a few tries. I wouldn't be concerned about those last 2. |
|
The latest GCP run "failed" but it actually looks pretty good. No i/o timeout: |
|
The e2e-aws-ovn failure is odd though. I've never seen this before: |
|
/test e2e-gcp-ovn |
|
/test e2e-aws-ovn |
|
@trozet: The specified target(s) for
Use
DetailsIn 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/test-infra repository. |
|
@trozet: The specified target(s) for
Use
DetailsIn 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/test-infra repository. |
|
/retest |
|
@wking: The following tests failed, say
Full PR test history. Your PR dashboard. DetailsInstructions 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. I understand the commands that are listed here. |
|
/test pj-rehearse |
|
/retest |
|
Covered by #12391. /close |
|
@wking: Closed this PR. DetailsIn 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/test-infra repository. |
4 participants
We're seeing errors like:
in CI jobs running on build02, and are wondering if these are related to the host cluster. Move some highly-impacted jobs over to build01 to see if that impacts the error rate.
Generated with:
$ sed -i 's/cluster: build02/cluster: build01/' ci-operator/jobs/openshift/ovn-kubernetes/openshift-ovn-kubernetes-master-presubmits.yaml