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

scheduler: correctly detect inplace update with wildcard datacenters #16362

Merged
merged 1 commit into from
Mar 7, 2023

Conversation

tgross
Copy link
Member

@tgross tgross commented Mar 7, 2023

Wildcard datacenters introduced a bug where a job with any wildcard datacenters will always be treated as a destructive update when we check whether a datacenter has been removed from the jobspec.

Includes updating the helper so that callers don't have to loop over the job's datacenters.

@tgross tgross force-pushed the scheduler-node-in-dc branch from cf1fa96 to 0870427 Compare March 7, 2023 14:23
@tgross tgross marked this pull request as ready for review March 7, 2023 14:23
@tgross tgross requested review from shoenig and jrasell March 7, 2023 14:23
@tgross tgross added this to the 1.5.1 milestone Mar 7, 2023
@tgross tgross added type/bug theme/scheduling backport/1.5.x backport to 1.5.x release line labels Mar 7, 2023
Copy link
Member

@jrasell jrasell left a comment

Choose a reason for hiding this comment

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

LGTM! Very minor comment, feel free to ignore.

scheduler/util_test.go Outdated Show resolved Hide resolved
Wildcard datacenters introduced a bug where a job with any wildcard datacenters
will always be treated as a destructive update when we check whether a
datacenter has been removed from the jobspec.

Includes updating the helper so that callers don't have to loop over the job's
datacenters.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants