-
Notifications
You must be signed in to change notification settings - Fork 1.9k
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
network namespaces are not reconciled #11096
Comments
Hi @th0m and thanks for another detailed issue! Reconciliation is something we should certainly add into the client so the network namespaces are cleaned as expected. |
Hi @jrasell, I just noticed this was removed from "Needs Roadmapping", does this mean this will not be worked on internally? |
Hi @th0m! The issue was moved to our internal "unified backlog" (which unfortunately isn't public) so that it can be picked up by a Nomad engineer to do. That being said, it's not on the near-term roadmap either. |
Hi @tgross, sounds good, thanks for the quick response! |
Adding some color to this issue, this is especially problematic when using the CNI vlan plugin. |
I'm going to lock this issue because it has been closed for 120 days ⏳. This helps our maintainers find and focus on the active issues. |
Nomad version
Output from
nomad version
Operating system and Environment details
Linux
Issue
Network namespaces associated to allocations that complete or fail while Nomad is stopped do not get cleaned up when Nomad starts back up and recovers the task.
This is a similar issue to #6385 but for network namespaces.
I am assuming this is due to https://github.com/hashicorp/nomad/blob/main/client/allocrunner/network_hook.go#L131-L140 not running when Nomad is stopped and the allocation completes.
Job file
sleep.nomad
Reproduction steps
nomad job run sleep.nomad
systemctl stop nomad
sleep 60
task completesystemctl start nomad
Expected Result
I would expect the network namespaces from previous allocations to be regularly reconciled and garbage collected.
Actual Result
The network namespace associated to the now defunct
33a997ad
allocation is still present on the machineFeel free to let me know if you need any more information.
Thank you!
The text was updated successfully, but these errors were encountered: