You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
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.
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
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:
helm -n pl uninstall pixie
operators.coreos.com/csv-cleanup
finalizerExpected behavior
Helm uninstall cleans up the
olm
,px-operator
andpl
namespaces.Logs
I don't have the logs handy, but I will attach them to this issue when I trigger the problem again.
The text was updated successfully, but these errors were encountered: