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 fix: job canonicalization should set job priority to 50, not 0. into release/1.3.x #17350

Conversation

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

Backport

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

WARNING automatic cherry-pick of commits failed. Commits will require human attention.

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


Nomad API will reject jobs with priority set to 0.

        	* Job priority must be between [1, 100])

@hc-github-team-nomad-core hc-github-team-nomad-core force-pushed the backport/b-fix-job-priority-canonicalization/sincerely-saving-mole branch from 708d8f2 to d32aeb1 Compare May 30, 2023 07:05
@hashicorp-cla
Copy link

hashicorp-cla commented May 30, 2023

CLA assistant check
All committers have signed the CLA.

@vercel vercel bot temporarily deployed to Preview – nomad May 30, 2023 07:10 Inactive
Nomad API will reject jobs with priority set to 0.
@pkazmierczak pkazmierczak force-pushed the backport/b-fix-job-priority-canonicalization/sincerely-saving-mole branch from 13f8214 to ce4a5d2 Compare May 30, 2023 07:14
@pkazmierczak pkazmierczak merged commit 899898f into release/1.3.x May 30, 2023
@pkazmierczak pkazmierczak deleted the backport/b-fix-job-priority-canonicalization/sincerely-saving-mole branch May 30, 2023 13:01
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.

4 participants