-
Notifications
You must be signed in to change notification settings - Fork 275
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
A pending workload that's deleted is still listed in the visibility API pendingworkloads
results
#1555
Comments
Interesting, because the visibility API serves on-demand the data directly from the in-memory cache used by scheduler, which suggests the cache itself is not updated. Did you have a chance to check if the
|
Right, that'd be my understanding as well. I had traced it down to: kueue/pkg/controller/core/workload_controller.go Lines 406 to 408 in 1adca15
For a pending workload, Naively, I'd think that if statement could / should be removed. But I wanted to understand why it's been added in the first place, and if it's correct / safe to remove it. |
/cc @alculquicondor |
oh shoot, this is a bug introduced here: 57c714d#diff-60dd240c20adbd6a189d018d1c216c2d296730f446c341d8bf449fa6657964ffR242 it went from I think removing the And please add an integration test. |
/assign |
What happened:
If a pending workload is deleted, querying the visibility API stills reports the workload.
What you expected to happen:
The workload should not be listed in the
pendingworkloads
sub-resource after it's deleted.How to reproduce it (as minimally and precisely as possible):
Anything else we need to know?:
Once the operator Pod is deleted / has restarted, the results are corrected.
Environment:
kubectl version
): v1.25.3git describe --tags --dirty --always
): v0.6.0-devel-146-ged81667f-dirtyThe text was updated successfully, but these errors were encountered: