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

act_gact kernel module missing for network packet control #6738

Closed
jyee opened this issue Feb 21, 2020 · 6 comments
Closed

act_gact kernel module missing for network packet control #6738

jyee opened this issue Feb 21, 2020 · 6 comments
Labels
kind/feature Categorizes issue or PR as related to a new feature. lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. priority/backlog Higher priority than priority/awaiting-more-evidence.

Comments

@jyee
Copy link

jyee commented Feb 21, 2020

The act_gact module is missing. Aside from general networking, act_gact is used by Chaos Engineering tools such as Gremlin to simulate network packet loss.. This is a similar use case to #6033 and #6271.

The full output of the command that failed:

$ modprobe -n act_gact
modprobe: FATAL: Module act_gact not found in directory /lib/modules/4.19.81

The operating system version:
minikube version: v1.7.2
commit: 50d543b

@priyawadhwa priyawadhwa added kind/support Categorizes issue or PR as a support question. kind/feature Categorizes issue or PR as related to a new feature. and removed kind/support Categorizes issue or PR as a support question. labels Feb 26, 2020
@medyagh
Copy link
Member

medyagh commented Mar 2, 2020

@jyee

if this a feature that others might use I would be happy to accept a PR that adds this kernel module, here is the documentation on how to add kernel modules to the minikube ISO

here is the link how to add kernel modules to our ISO
https://minikube.sigs.k8s.io/docs/contributing/iso/#adding-kernel-modules

https://minikube.sigs.k8s.io/docs/contributing/iso/#adding-kernel-modules

meanwhile, maybe you could use the docker-driver which uses ubuntu as base image?

@medyagh medyagh added the priority/backlog Higher priority than priority/awaiting-more-evidence. label Mar 2, 2020
@medyagh
Copy link
Member

medyagh commented Mar 2, 2020

CC: @afbjorklund

@fejta-bot
Copy link

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label May 31, 2020
@fejta-bot
Copy link

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle rotten

@k8s-ci-robot k8s-ci-robot added lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Jun 30, 2020
@fejta-bot
Copy link

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close

@k8s-ci-robot
Copy link
Contributor

@fejta-bot: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/feature Categorizes issue or PR as related to a new feature. lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. priority/backlog Higher priority than priority/awaiting-more-evidence.
Projects
None yet
Development

No branches or pull requests

5 participants