-
Notifications
You must be signed in to change notification settings - Fork 4.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
Add tests, fallback properly if we can't init the cgroups #41189
Add tests, fallback properly if we can't init the cgroups #41189
Conversation
Pinging @elastic/sec-linux-platform (Team:Security-Linux Platform) |
This pull request does not have a backport label.
To fixup this pull request, you need to add the backport labels for the needed
|
|
Pinging @elastic/elastic-agent-data-plane (Team:Elastic-Agent-Data-Plane) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Does this need a changelog entry?
@leehinman I don't think so, since the original bug was never released. |
* add tests, fallback properly if we can't init the cgroups * linter * fix test (cherry picked from commit 648ec22) # Conflicts: # libbeat/processors/add_docker_metadata/add_docker_metadata.go # libbeat/processors/add_process_metadata/add_process_metadata.go # libbeat/processors/add_process_metadata/add_process_metadata_test.go # libbeat/processors/add_process_metadata/gosigar_cid_provider.go
* add tests, fallback properly if we can't init the cgroups * linter * fix test
Proposed commit message
Turns out that we don't have any tests that actually check to see if the default cgroups callback actually initializes properly, so #41108 broke the processors on non-linux systems.
This re-adds support for systems that don't have cgroups support, and also adds tests that makes sure the processors can startup and run with the default cgroups provider.
Checklist
CHANGELOG.next.asciidoc
orCHANGELOG-developer.next.asciidoc
.