Skip to content
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

[multikueue] Reconcile the relevant ACs on cluster create. #2165

Merged

Conversation

trasc
Copy link
Contributor

@trasc trasc commented May 8, 2024

What type of PR is this?

/kind bug

What this PR does / why we need it:

[multikueue] Reconcile the relevant ACs on cluster create.

Which issue(s) this PR fixes:

Fixes #2117

Special notes for your reviewer:

Does this PR introduce a user-facing change?

MultiKueue: Fix a bug that could delay the joining clusters when it's MultiKueueCluster is created.

@k8s-ci-robot k8s-ci-robot added release-note-none Denotes a PR that doesn't merit a release note. kind/bug Categorizes issue or PR as related to a bug. cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. labels May 8, 2024
@k8s-ci-robot k8s-ci-robot added the size/XS Denotes a PR that changes 0-9 lines, ignoring generated files. label May 8, 2024
Copy link

netlify bot commented May 8, 2024

Deploy Preview for kubernetes-sigs-kueue ready!

Name Link
🔨 Latest commit f4e3faa
🔍 Latest deploy log https://app.netlify.com/sites/kubernetes-sigs-kueue/deploys/663bb035985025000855c63f
😎 Deploy Preview https://deploy-preview-2165--kubernetes-sigs-kueue.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify site configuration.

@@ -267,7 +267,7 @@ func (m *mkClusterHandler) Create(ctx context.Context, event event.CreateEvent,
return
}

if err := queueReconcileForConfigUsers(ctx, mkc.Name, m.client, q); err != nil {
if err := m.queue(ctx, mkc, q); err != nil {
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Doesn't the fact that we could not detect this bug in the test indicate that we don't have any cases to verify here?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The problem is that we don't test (and I don't think it's easy to do) the create only scenario, after the cluster is created one of the first things happening is for it's active condition to be set, triggering an Update which worked well.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Uhm, couldn't add a unit test for creation?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

That will be the first if it's king in the entire project.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

That will be the first if it's king in the entire project.

@trasc Alright. Could you create tracking issue?

/lgtm
/approve

@k8s-ci-robot k8s-ci-robot added the lgtm "Looks good to me", indicates that a PR is ready to be merged. label May 8, 2024
@k8s-ci-robot
Copy link
Contributor

LGTM label has been added.

Git tree hash: ccc0e7b426b56ee0ec334ebf0fb1f1eef03a0c0d

@k8s-ci-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: tenzen-y, trasc

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 /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@k8s-ci-robot k8s-ci-robot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label May 8, 2024
@tenzen-y
Copy link
Member

tenzen-y commented May 8, 2024

MultiKueue: Fix a bug that could potentially cause the failure of MultiKueue creation.

@tenzen-y
Copy link
Member

tenzen-y commented May 8, 2024

/release-note-edit

MultiKueue: Fix a bug that could potentially cause the failure of MultiKueue creation.

@k8s-ci-robot k8s-ci-robot added release-note Denotes a PR that will be considered when it comes time to generate release notes. and removed release-note-none Denotes a PR that doesn't merit a release note. labels May 8, 2024
@tenzen-y
Copy link
Member

tenzen-y commented May 8, 2024

/cherry-pick release-0.6

@k8s-infra-cherrypick-robot
Copy link
Contributor

@tenzen-y: once the present PR merges, I will cherry-pick it on top of release-0.6 in a new PR and assign it to you.

In response to this:

/cherry-pick release-0.6

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.

@k8s-ci-robot k8s-ci-robot merged commit 1e3055f into kubernetes-sigs:main May 8, 2024
15 checks passed
@k8s-ci-robot k8s-ci-robot added this to the v0.7 milestone May 8, 2024
@k8s-infra-cherrypick-robot
Copy link
Contributor

@tenzen-y: new pull request created: #2167

In response to this:

/cherry-pick release-0.6

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.

@trasc trasc deleted the multikueue-cluster-create-bug branch May 9, 2024 05:30
kannon92 pushed a commit to openshift-kannon92/kubernetes-sigs-kueue that referenced this pull request Nov 19, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. kind/bug Categorizes issue or PR as related to a bug. lgtm "Looks good to me", indicates that a PR is ready to be merged. release-note Denotes a PR that will be considered when it comes time to generate release notes. size/XS Denotes a PR that changes 0-9 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

It seems like the wrong function is being used when a multiKueueCluster is created
4 participants