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

Migrate all allocs when draining a node #10411

Merged
merged 2 commits into from
Apr 21, 2021
Merged

Migrate all allocs when draining a node #10411

merged 2 commits into from
Apr 21, 2021

Conversation

notnoop
Copy link
Contributor

@notnoop notnoop commented Apr 20, 2021

This fixes a bug affecting drain nodes, where allocs may fail to be
migrated if they belong to different namespaces but share the same job
name.

The reason is that the helper function that creates the migration evals
indexed the allocs by job ID without accounting for the namespaces.
When job ids clash, only an eval is created for one and the rest of the
allocs remain intact.

I've added the test first, so the failure can be seen in https://app.circleci.com/pipelines/github/hashicorp/nomad/15799/workflows/383e0ec3-0803-4751-ba8f-862461d12741/jobs/151142 .

Fixes #10172

Mahmood Ali added 2 commits April 20, 2021 10:56
This fixes a bug affecting drain nodes, where allocs may fail to be
migrated if they belong to different namespaces but share the same job
name.

The reason is that the helper function that creates the migration evals
indexed the allocs by job ID without accounting for the namespaces.
When job ids clash, only an eval is created for one and the rest of the
allocs remain unmigrated.
Copy link
Member

@tgross tgross left a comment

Choose a reason for hiding this comment

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

LGTM 👍

@notnoop notnoop merged commit a94ac46 into main Apr 21, 2021
@notnoop notnoop deleted the b-drain-multiple-nses branch April 21, 2021 16:11
schmichael pushed a commit that referenced this pull request May 14, 2021
This fixes a bug affecting drain nodes, where allocs may fail to be
migrated if they belong to different namespaces but share the same job
name.

The reason is that the helper function that creates the migration evals
indexed the allocs by job ID without accounting for the namespaces.
When job ids clash, only an eval is created for one and the rest of the
allocs remain intact.

Fixes #10172
@tgross tgross added this to the 1.1.0 milestone May 17, 2021
@github-actions
Copy link

I'm going to lock this pull request because it has been closed for 120 days ⏳. This helps our maintainers find and focus on the active contributions.
If you have found a problem that seems related to this change, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Nov 21, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

jobs in non-default namespace can hang node drain
3 participants