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
@nikitok It might be that you had datasets that were still present when you reinstalled datashim. Because of this, the CRD associated with your previous installation has not been deleted. This is how you can solve this issue:
Find if there any datasets and datasetinternals objects that are still lingering around: kubectl get datasets --all-namespaces kubectl get datasetsinternal --all-namespaces
Ensure that any pods that are mounting these datasets have exited. The PVCs cannot be deleted while the volumes are still mounted
Delete the objects you have found in step 1.
At this point, the CRD should've been terminated. You can check it by: kubectl get customresourcedefinitions.apiextensions.k8s.io -n dlf
If the CRDs are still around, try removing the finalisers like so: kubectl patch datasetsinternal.com.ie.ibm.hpsys -p '{"metadata":{"finalizers":[]}}' --type=merge
Delete the entire datashim installation for good measure and reinstall again. Check the status of the CRDs before creating a dataset
Hi, after problem with my clusterm i reinstall datashim, and now, i can't create new pvc with this yaml
Kuber doesnot create pvc, and i found logs:
"create not allowed while custom resource definition is terminating"
Do you know, what is happened and how it resolve?
The text was updated successfully, but these errors were encountered: