-
Notifications
You must be signed in to change notification settings - Fork 276
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
[kueue] Wait for webhooks setup before ready. #1674
Conversation
Skipping CI for Draft Pull Request. |
Adding the "do-not-merge/release-note-label-needed" label because no release-note block was detected, please follow our release note process to remove it. 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. |
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: trasc The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
✅ Deploy Preview for kubernetes-sigs-kueue canceled.
|
/test pull-kueue-test-e2e-main-1-27 |
try 2. /test pull-kueue-test-e2e-main-1-27 |
/test pull-kueue-test-e2e-main-1-27 |
1 similar comment
/test pull-kueue-test-e2e-main-1-27 |
/test pull-kueue-test-e2e-main-1-27 |
a0454ba
to
387a10b
Compare
/test pull-kueue-test-e2e-main-1-26 |
1 similar comment
/test pull-kueue-test-e2e-main-1-26 |
@@ -65,11 +65,19 @@ func CreateVisibilityClient(user string) visibilityv1alpha1.VisibilityV1alpha1In | |||
return visibilityClient | |||
} | |||
|
|||
func KueueReadyForTesting(ctx context.Context, client client.Client) { | |||
func KueueReadyForTesting(ctx context.Context, c client.Client) { |
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.
Can we delete this function if we are waiting for the "webooks setup before ready"?
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.
no, this is running in the test binary
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.
but should not the test binary wait until Kueue is healthy / ready, rather than trying to periodically create the items? If we still periodically need to create items I don't seem much gain of delaying the healthy status.
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.
It's just another way of checking the same thing.
I theory you can check if all the kueue-controller-manager pods are ready instead.
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.
I see, but this involves creating / deleting objects, something which users may not want to do in prod. I think it is better if e2e tests correspond better to production use. Also, the creation / deletion takes more time some may cover some user issues. If we go with this approach I would suggest to wait as for ready deployment, this can be done as here:
kubectl wait --for=condition=available --timeout=3m deployment/kueue-controller-manager -n kueue-system
/test pull-kueue-test-e2e-main-1-26 |
/test pull-kueue-test-e2e-main-1-26 |
387a10b
to
1031a49
Compare
/test pull-kueue-test-e2e-main-1-26 |
/test pull-kueue-test-e2e-main-1-26 |
/test pull-kueue-test-e2e-main-1-26 |
/test pull-kueue-test-e2e-main-1-26 |
1 similar comment
/test pull-kueue-test-e2e-main-1-26 |
/test pull-kueue-test-e2e-main-1-26 |
1 similar comment
/test pull-kueue-test-e2e-main-1-26 |
/assign @astefanutti |
@alculquicondor: GitHub didn't allow me to assign the following users: astefanutti. Note that only kubernetes-sigs members with read permissions, repo collaborators and people who have commented on this issue/PR can be assigned. Additionally, issues/PRs can only have 10 assignees at the same time. 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. |
A failure happened https://prow.k8s.io/view/gs/kubernetes-jenkins/pr-logs/pull/kubernetes-sigs_kueue/1674/pull-kueue-test-e2e-main-1-28/1752369431784198144 :( The webhook never became available. |
}, StartUpTimeout, Interval).Should(gomega.Succeed()) | ||
ExpectResourceFlavorToBeDeleted(ctx, client, resourceKueue, true) |
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.
why change this?
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.
the reporting is hard to follow with that, in case of multikueue you don't know which of the clusters is not ready.
1031a49
to
b10f549
Compare
/test pull-kueue-test-e2e-main-1-26 |
1 similar comment
/test pull-kueue-test-e2e-main-1-26 |
974b886
to
7f66d18
Compare
/test pull-kueue-test-e2e-main-1-26 |
/test pull-kueue-test-e2e-main-1-26 |
1 similar comment
/test pull-kueue-test-e2e-main-1-26 |
@trasc: The following test failed, say
Full PR test history. Your PR dashboard. Please help us cut down on flakes by linking to an open issue when you hit one in your PR. 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. I understand the commands that are listed here. |
/close |
@trasc: Closed this PR. 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. |
What type of PR is this?
What this PR does / why we need it:
Which issue(s) this PR fixes:
Fixes #
Special notes for your reviewer:
Does this PR introduce a user-facing change?