Skip to content

TestNodeAffinityScoring / scheduler integration flake #131515

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.

Sign up for GitHub

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

Jump to bottom
Open
BenTheElder opened this issue Apr 28, 2025 · 2 comments · May be fixed by #131710
Open

TestNodeAffinityScoring / scheduler integration flake #131515

BenTheElder opened this issue Apr 28, 2025 · 2 comments · May be fixed by #131710
Assignees
@saza-ku
Labels
kind/flake Categorizes issue or PR as related to a flaky test. needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. sig/scheduling Categorizes an issue or PR as relevant to SIG Scheduling.

Comments

@BenTheElder
Copy link
Member

Pod pod-with-node-affinity got scheduled on an unexpected node: testnode-3. Expected node: testnode-4.
--- FAIL: TestNodeAffinityScoring (7.08s)

https://prow.k8s.io/view/gs/kubernetes-ci-logs/pr-logs/pull/131511/pull-kubernetes-integration/1916851016070860800

spotted on #131511 which should not impact this test at all

/sig scheduling
/kind flake
@k8s-ci-robot k8s-ci-robot added sig/scheduling Categorizes an issue or PR as relevant to SIG Scheduling. kind/flake Categorizes issue or PR as related to a flaky test. needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. labels Apr 28, 2025
@k8s-ci-robot
Copy link
Contributor

This issue is currently awaiting triage.

If a SIG or subproject determines this is a relevant issue, they will accept it by applying the triage/accepted label and provide further guidance.

The triage/accepted label can be added by org members by writing /triage accepted in a comment.

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.

@saza-ku
Copy link
Contributor

saza-ku commented May 10, 2025

It looks like the pod was scheduled before testnode-4 is added to the scheduler's cache.

https://prow.k8s.io/view/gs/kubernetes-ci-logs/pr-logs/pull/131511/pull-kubernetes-integration/1916851016070860800#1:build-log.txt%3A4775
https://prow.k8s.io/view/gs/kubernetes-ci-logs/pr-logs/pull/131511/pull-kubernetes-integration/1916851016070860800#1:build-log.txt%3A4780

I'll make it wait for it to be synced.

/assign

@saza-ku saza-ku linked a pull request May 10, 2025 that will close this issue
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@saza-ku saza-ku

Labels
kind/flake Categorizes issue or PR as related to a flaky test. needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. sig/scheduling Categorizes an issue or PR as relevant to SIG Scheduling.
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

test: wait for nodes to be in scheduler's cache saza-ku/kubernetes
3 participants
@BenTheElder @k8s-ci-robot @saza-ku