Sujeily Fonseca

/priority stopship

I don't have PFE logs since the workspace was also deleted.

I have tested this problem several times and also asked @DavidG1011 to reproduce the problem. We both notice that it tries to release the pods after removing the workspace, but...

FYI, I have been working to provide @GeekArthur with the information he requested. However, I currently have a problem with the master node of my cluster. I have opened a...

**Before workspace deletion:** ``` [root@sfonseca-okd-codewind ~]# oc get pod --selector=app=codewind-pfe -o jsonpath='{.items[*].status.containerStatuses[*].imageID}' docker-pullable://docker.io/eclipse/codewind-pfe-amd64@sha256:b834c33e11f85ad1e8e2203a11ce5653e831f3a7401c695d2de25c2604f761d9 ```` ``` [root@sfonseca-okd-codewind ~]# kubectl get pvc NAME STATUS VOLUME CAPACITY ACCESS MODES STORAGECLASS AGE claim-che-workspace-workspacesr88ly1bxvpjtzrc Bound...

@GeekArthur ``` [root@sfonseca-okd-codewind ~]# oc describe pv che-workspace3 Name: che-workspace3 Labels: Annotations: pv.kubernetes.io/bound-by-controller=yes Finalizers: [kubernetes.io/pv-protection] StorageClass: Status: Failed Claim: che/cw-cw-odo-perl-app-s2idata Reclaim Policy: Recycle Access Modes: RWO Capacity: 1Gi Node Affinity:...

/reopen /priority stopship **Codewind version:** 0.8.0 **OS:** Red Hat Enterprise Linux 7 (64 bit) **Che version:** 7.5.1 **Kubernetes cluster:** OKD/Openshift I'm reopening this issue and marking it as "stopship" since...