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

After reinstallation, I have a problem with new datasets #219

Open
nikitok opened this issue Feb 7, 2023 · 1 comment
Open

After reinstallation, I have a problem with new datasets #219

nikitok opened this issue Feb 7, 2023 · 1 comment
Labels
question Further information is requested

Comments

@nikitok
Copy link

nikitok commented Feb 7, 2023

Hi, after problem with my clusterm i reinstall datashim, and now, i can't create new pvc with this yaml

kind: Dataset
metadata:
  name: example-dataset
spec:
  local:
    type: "COS"
...

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?

@srikumar003 srikumar003 added the question Further information is requested label Feb 8, 2023
@srikumar003
Copy link
Collaborator

@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:

  1. Find if there any datasets and datasetinternals objects that are still lingering around:
    kubectl get datasets --all-namespaces
    kubectl get datasetsinternal --all-namespaces
  2. Ensure that any pods that are mounting these datasets have exited. The PVCs cannot be deleted while the volumes are still mounted
  3. Delete the objects you have found in step 1.
  4. 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
  5. Delete the entire datashim installation for good measure and reinstall again. Check the status of the CRDs before creating a dataset

Let us know how it goes.

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

No branches or pull requests

2 participants