-
Notifications
You must be signed in to change notification settings - Fork 2.6k
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
CAPI Operator: move jobs to EKS prow cluster #29743
CAPI Operator: move jobs to EKS prow cluster #29743
Conversation
713cac3
to
04912e8
Compare
config/jobs/kubernetes-sigs/cluster-api-operator/cluster-api-operator-periodics-main.yaml
Show resolved
Hide resolved
/cc @Fedosin @alexander-demicev @JoelSpeed |
/hold cancel |
/hold didn't notice #29743 (comment) |
@furkatgofurov7 Can you please rebase this PR ? |
Signed-off-by: Furkat Gofurov <furkat.gofurov@suse.com>
04912e8
to
19ae37f
Compare
I think we are good to go ahead with current resource quotas. I will be watching the jobs after this PR is merged and increase it if need arises. /hold cancel cc @Fedosin |
/cc @dims |
@furkatgofurov7 Please keep an eye of those jobs for a few days. /approve |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: ameukam, furkatgofurov7 The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
@furkatgofurov7: Updated the
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/test-infra repository. |
annotations: | ||
testgrid-dashboards: sig-cluster-lifecycle-cluster-api-operator | ||
testgrid-tab-name: capi-operator-pr-test-main | ||
- name: pull-cluster-api-operator-e2e-main | ||
cluster: eks-prow-build-cluster |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@ameukam After the merge, this job started failing in kubernetes-sigs/cluster-api-operator#143. Looking at the build logs in https://prow.k8s.io/view/gs/kubernetes-jenkins/pr-logs/pull/kubernetes-sigs_cluster-api-operator/143/pull-cluster-api-operator-e2e-main/1668941993025212416 I don't find anything useful and just:
Job execution failed: Pod pending timeout.
Failed to open /logs/process-log.txt: open /logs/process-log.txt: no such file or directory
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks like an issue with the build cluster. Let me ping folx on Slack.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks, please tag me in the thread if possible
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
+1 I'd love to follow along too. There have been a few merged jobs transitioning that have had issues so far.
Fixes: kubernetes-sigs/cluster-api-operator#152
Part of: kubernetes-sigs/cluster-api-operator#153
Related to: #29722
/hold