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

Backport of scheduler: correctly detect inplace update with wildcard datacenters into release/1.5.x #16364

Conversation

hc-github-team-nomad-core
Copy link
Contributor

Backport

This PR is auto-generated from #16362 to be assessed for backporting due to the inclusion of the label backport/1.5.x.

The below text is copied from the body of the original PR.


Wildcard datacenters introduced a bug where a system 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.

@hc-github-team-nomad-core hc-github-team-nomad-core force-pushed the backport/scheduler-node-in-dc/adversely-driving-fish branch from 493721f to e1b1e2c Compare March 7, 2023 15:06
@hc-github-team-nomad-core hc-github-team-nomad-core merged commit b363292 into release/1.5.x Mar 7, 2023
@hc-github-team-nomad-core hc-github-team-nomad-core deleted the backport/scheduler-node-in-dc/adversely-driving-fish branch March 7, 2023 15:06
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants