Unable to uninstall OLM

[camilamacedo86]

WHAT:

How to uninstall OLM?

Expected

• Script to uninstall and make command
• Documentation over it

[jmazzitelli]

+1 !!

I tried oc delete -f deploy/okd/manifests/latest/

and now my namespaces are blocked in the terminating state and not going away.

$ oc get namespace openshift-operators
NAME                  STATUS        AGE
openshift-operators   Terminating   20h
$ oc get namespace openshift-operator-lifecycle-manager 
NAME                                   STATUS        AGE
openshift-operator-lifecycle-manager   Terminating   20h

There are finalizers listed - so I assume a finalizer failed and now the namespaces are blocked:

$ oc get namespace openshift-operators -o yaml
apiVersion: v1
kind: Namespace
metadata:
  annotations:
    kubectl.kubernetes.io/last-applied-configuration: |
      {"apiVersion":"v1","kind":"Namespace","metadata":{"annotations":{},"name":"openshift-operators","namespace":""},"spec":{"finalizers":[]}}
    openshift.io/sa.scc.mcs: s0:c22,c14
    openshift.io/sa.scc.supplemental-groups: 1000490000/10000
    openshift.io/sa.scc.uid-range: 1000490000/10000
  creationTimestamp: 2019-04-11T17:45:09Z
  deletionTimestamp: 2019-04-12T13:35:44Z
  name: openshift-operators
  resourceVersion: "1048433"
  selfLink: /api/v1/namespaces/openshift-operators
  uid: 8d16cc01-5c81-11e9-81da-54e1addf59b3
spec:
  finalizers:
  - kubernetes
status:
  phase: Terminating

$ oc get namespace openshift-operator-lifecycle-manager -o yaml
apiVersion: v1
kind: Namespace
metadata:
  annotations:
    kubectl.kubernetes.io/last-applied-configuration: |
      {"apiVersion":"v1","kind":"Namespace","metadata":{"annotations":{},"name":"openshift-operator-lifecycle-manager","namespace":""}}
    openshift.io/sa.scc.mcs: s0:c22,c9
    openshift.io/sa.scc.supplemental-groups: 1000480000/10000
    openshift.io/sa.scc.uid-range: 1000480000/10000
  creationTimestamp: 2019-04-11T17:45:09Z
  deletionTimestamp: 2019-04-12T13:35:44Z
  name: openshift-operator-lifecycle-manager
  resourceVersion: "1043578"
  selfLink: /api/v1/namespaces/openshift-operator-lifecycle-manager
  uid: 8d161d42-5c81-11e9-81da-54e1addf59b3
spec:
  finalizers:
  - kubernetes
status:
  phase: Terminating

[ecordell]

This is an ordering issue -

If you delete the apiservice first (packagemanifests), then the crds, and then the other resources, you should be in the clear.

We should have a tool to do this for you so I'll leave this open to track that.

[gerrit8143]

deleting the packagemanifests doesn't seem to work

$ kubectl delete packagemanifests.packages.operators.coreos.com -n olm --all                                                                                                                                                              
Error from server (MethodNotAllowed): the server does not allow this method on the requested resource
Error from server (MethodNotAllowed): the server does not allow this method on the requested resource
Error from server (MethodNotAllowed): the server does not allow this method on the requested resource
Error from server (MethodNotAllowed): the server does not allow this method on the requested resource
Error from server (MethodNotAllowed): the server does not allow this method on the requested resource
Error from server (MethodNotAllowed): the server does not allow this method on the requested resource
Error from server (MethodNotAllowed): the server does not allow this method on the requested resource
Error from server (MethodNotAllowed): the server does not allow this method on the requested resource
Error from server (MethodNotAllowed): the server does not allow this method on the requested resource

[gerrit8143]

The following worked for me:

kubectl delete crd catalogsources.operators.coreos.com clusterserviceversions.operators.coreos.com installplans.operators.coreos.com operatorgroups.operators.coreos.com subscriptions.operators.coreos.com

followed by

kubectl delete ns olm

[camilamacedo86]

Hi folks,
In the following PR the make command make uninstall was added and it shows working fine 100% for me. Please, feel free to review.

#898

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[camilamacedo86]

The PR to address it is : #1438