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 qemu: pass task resources into driver for cgroup setup into release/1.8.x #23478

Merged
merged 1 commit into from
Jul 1, 2024

Conversation

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

Backport

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

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


As part of the work for 1.7.0 we moved portions of the task cgroup setup down into the executor. This requires that the executor constructor get the TaskConfig.Resources struct, and this was missing from the qemu driver. We fixed a panic caused by this change in #19089 before we shipped, but this fix was effectively undone after we added plumbing for custom cgroups for raw_exec in 1.8.0. As a result, running qemu tasks always fail on Linux.

This was undetected in testing because our CI environment doesn't have QEMU installed. I've got all the unit tests running locally again and have added QEMU installation when we're running the drivers tests, so that'll catch future regressions.

Fixes: #23250


Overview of commits

@tgross tgross merged commit 9083333 into release/1.8.x Jul 1, 2024
20 checks passed
@tgross tgross deleted the backport/qemu-cgroup/immensely-legal-halibut branch July 1, 2024 15:59
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 Dec 31, 2024
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.

2 participants