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

Helm uninstall leaves px-operator namespace in (stuck) terminating state #1917

Open
ddelnano opened this issue May 24, 2024 · 2 comments
Open

Comments

@ddelnano
Copy link
Member

Describe the bug
The helm install process followed by a helm uninstall does not fully clean up all pixie resources in the v0.1.7 operator release. The OLM project added a csv-cleanup finalizer in v0.27.0 that causes the px-operator to get stuck in a terminating state.

To Reproduce
Steps to reproduce the behavior:

  1. Install pixie via the helm install instructions
  2. helm -n pl uninstall pixie
  3. Notice that the px-operator is stuck in a terminating state due to the operators.coreos.com/csv-cleanup finalizer

Expected behavior
Helm uninstall cleans up the olm, px-operator and pl namespaces.

Logs
I don't have the logs handy, but I will attach them to this issue when I trigger the problem again.

@ddelnano
Copy link
Member Author

As a short term workaround, if OLM is installed prior to using the Pixie helm chart, the issue does not occur. This is because OLM won't be a part of the helm installation, which allows the px-operator finalizers defined within OLM to run successfully on helm uninstall.

I'm evaluating options for addressing this finalizer issue in the meantime.

@danlhennessy
Copy link

Can confirm I am experiencing the same issue. Have also found that installing via helm, and when uninstalling, running:
px delete
against the specific cluster before helm uninstall has also worked without finalizers causing operator namespace to get stuck. But yes not ideal, preferable for helm to manage everything

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants