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: set job on system stack for CSI feasibility check into release/1.3.x #15377

Conversation

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

Backport

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

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


Fixes #15094

When the scheduler checks feasibility of each node, it creates a "stack" which carries attributes of the job and task group it needs to check feasibility for. The system and sysbatch scheduler use a different stack than service and batch jobs. This stack was missing the call to set the job ID and namespace for the CSI check. This prevents CSI volumes from being scheduled for system jobs whenever the volume is in a non-default namespace.

Set the job ID and namespace to match the generic scheduler.

@hc-github-team-nomad-core hc-github-team-nomad-core force-pushed the backport/b-csi-set-namespace-and-job-id-system-stack/merely-hip-scorpion branch from 979f46e to f0c14bf Compare November 23, 2022 21:59
@hc-github-team-nomad-core hc-github-team-nomad-core merged commit 5afa9fe into release/1.3.x Nov 23, 2022
@hc-github-team-nomad-core hc-github-team-nomad-core deleted the backport/b-csi-set-namespace-and-job-id-system-stack/merely-hip-scorpion branch November 23, 2022 21:59
@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 Mar 24, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants