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 cli: fix return code when job deployment succeeds into release/1.6.x #19880

Merged

Conversation

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

Backport

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

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


When a job eval is blocked due to missing capacity, the nomad job run command will monitor the deployment, which may succeed once additional capacity is made available.

But the current implementation would return 2 even when the deployment succeeded because it only took the first eval status into account.

This commit updates the eval monitoring logic to reset the scheduling error state if the deployment eventually succeeds.

Closes #19780
Closes #12784


Overview of commits

@hc-github-team-nomad-core hc-github-team-nomad-core force-pushed the backport/b-fix-rc-job-run/externally-factual-magpie branch from c2323c8 to f1d41da Compare February 5, 2024 23:32
@vercel vercel bot temporarily deployed to Preview – nomad February 5, 2024 23:34 Inactive
@vercel vercel bot temporarily deployed to Preview – nomad-storybook-and-ui February 5, 2024 23:43 Inactive
@lgfa29 lgfa29 merged commit efd0b98 into release/1.6.x Feb 5, 2024
24 of 26 checks passed
@lgfa29 lgfa29 deleted the backport/b-fix-rc-job-run/externally-factual-magpie branch February 5, 2024 23:52
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.

None yet

2 participants