ci-operator/jobs/openshift/release: Move 4.6 periodics to build02 #12383
Conversation
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 promotion informers over to build02 to see if they start experiencing the same symptoms. Generated with: $ sed -i 's/cluster: api.ci/cluster: build02/' ci-operator/jobs/openshift/release/openshift-release-release-4.6-periodics.yaml [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
|
[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 |
|
You need to update core-services/sanitize-prow-jobs/_config.yaml with the new location. Otherwise lgtm |
|
@deads2k wasn't excited about moving important promotion jobs onto the suspected cluster. That's fine, and #12386 goes the other way to move jobs off the suspected cluster. Looking ahead, it would be nice if we could shard the release promotion jobs in |
|
@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. |
|
/uncc |
|
@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. |
|
@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. |
|
Issues go stale after 90d of inactivity. Mark the issue as fresh by commenting If this issue is safe to close now please do so with /lifecycle stale |
openshift-ci
bot
added
the
lifecycle/stale
|
Stale issues rot after 30d of inactivity. Mark the issue as fresh by commenting If this issue is safe to close now please do so with /lifecycle rotten |
openshift-ci
bot
added
lifecycle/rotten
|
@wking: PR needs rebase. 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. |
openshift-ci
bot
added
the
needs-rebase
|
Rotten issues close after 30d of inactivity. Reopen the issue by commenting /close |
|
@openshift-bot: 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. |
5 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 promotion informers over to build02 to see if they start experiencing the same symptoms.
Generated with:
$ sed -i 's/cluster: api.ci/cluster: build02/' ci-operator/jobs/openshift/release/openshift-release-release-4.6-periodics.yaml