e2e resource leak test for client restarts
Open
theme/client-restart
theme/e2e
theme/retrospective
theme/testing
- Dominant language
- Go
- Stars
- 17k
- Forks
- 2.1k
- Avg merge
- 1d 9h
- Merged PRs (30d)
- 105
Description
In addition to client upgrade testing ref https://github.com/hashicorp/nomad/issues/7063, we should specifically include a test that ensures we're not leaking resources (logmon processes, iptables, etc.) after task handles are restored on client restart.
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by reading issue #7063 and locating the existing client upgrade end-to-end tests. Trace how task handles are restored after a client restart, then define the test around checking for leftover logmon processes and iptables state; done means the restart completes without those resources leaking.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- infrastructure, testing-qa
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100