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

Undeploying bpfman selinux example programs hang on OpenShift #331

Open
anfredette opened this issue Oct 24, 2024 · 1 comment
Open

Undeploying bpfman selinux example programs hang on OpenShift #331

anfredette opened this issue Oct 24, 2024 · 1 comment
Assignees
Milestone

Comments

@anfredette
Copy link
Contributor

Running make deploy-*-selinux to an OpenShift cluster seems to work, but make undeploy-*-selinux hangs.

On closer inspection, after deploying, the selinux profile stays in the “Pending” state which doesn’t seem right. Then, after running the undeploy command, the namespace is waiting on an selinux profile and a number of finalizers.

For more details search for the test case starting with "$ k apply -f go-tracepoint-counter-install-selinux.yaml" in bpfman Selinux Test.

@github-project-automation github-project-automation bot moved this to 🆕 New in bpfman Oct 24, 2024
@anfredette anfredette added this to the Q4-2024 milestone Oct 24, 2024
Billy99 added a commit to Billy99/bpfman-operator that referenced this issue Feb 11, 2025
After deploying the selinux profile, the status on the Selinux Profile
is “Pending”. security-profiles-operator is currently deployed in
OpenShift by making it a dependency of bpfman-operator. As a result, the
security-profiles-operator is deployed in the bpfman namespace.
security-profiles-operator encounters issues with this because there are
other daemonsets in the namespace. Short term, remove the dependency.
security-profiles-operator is still required, it just won't be
auto-installed.

Related: bpfman#331
Related: kubernetes-sigs/security-profiles-operator#2699

Signed-off-by: Billy McFall <22157057+Billy99@users.noreply.github.com>
@Billy99
Copy link
Contributor

Billy99 commented Feb 11, 2025

There are two issues here:

On closer inspection, after deploying, the selinux profile stays in the “Pending” state which doesn’t seem right.

This is because security-profiles-operator is currently deployed in OpenShift by making it a dependency of bpfman-operator via config/manifests/dependencies.yaml. As a result, the security-profiles-operator is deployed in the bpfman namespace. security-profiles-operator encounters issues with this because there are other daemonsets in the namespace.

See: kubernetes-sigs/security-profiles-operator#2699

Then, after running the undeploy command, the namespace is waiting on an selinux profile and a number of finalizers.

Upon further testing, if the application namespace is not deleted until after the SelinuxProfile is deleted, everything cleans up fine. This is a bug in security-profiles-operator.

See: kubernetes-sigs/security-profiles-operator#2684

Billy99 added a commit to Billy99/bpfman-operator that referenced this issue Feb 13, 2025
After deploying the selinux profile, the status on the Selinux Profile
is “Pending”. security-profiles-operator is currently deployed in
OpenShift by making it a dependency of bpfman-operator. As a result, the
security-profiles-operator is deployed in the bpfman namespace.
security-profiles-operator encounters issues with this because there are
other daemonsets in the namespace. Short term, remove the dependency.
security-profiles-operator is still required, it just won't be
auto-installed.

Related: bpfman#331
Related: kubernetes-sigs/security-profiles-operator#2699

Signed-off-by: Billy McFall <22157057+Billy99@users.noreply.github.com>
msherif1234 pushed a commit to msherif1234/bpfman-operator that referenced this issue Feb 24, 2025
…s/component-update-ocp-bpfman-operator-bundle

chore(deps): update ocp-bpfman-operator-bundle to 631d3da
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: 🆕 New
Development

No branches or pull requests

2 participants