tridentctl import renames and deletes volume in Netapp

[Ujkugri]

Describe the bug
We are in a kubernetes environment and when using the following command

cat <<EOF | kubectl exec -n trident -it trident-csi-xxx -- tridentctl import volume ontap-san trident_pvc_23c1a0aa_61a4_439a_bfa6_5f992d013935_5646 -f -
apiVersion: v1
kind: PersistentVolumeClaim
metadata:
  annotations:
    meta.helm.sh/release-name: xxx
    meta.helm.sh/release-namespace: xxx
  labels:
    app.kubernetes.io/component: xxx
    app.kubernetes.io/instance: xxx
    app.kubernetes.io/managed-by: Helm
    app.kubernetes.io/name: xxx
    helm.sh/chart: xxx
  name: xxx
  namespace: xxx
spec:
  accessModes:
  - ReadWriteOnce
  resources:
    requests:
      storage: 10Gi
  storageClassName: netapp-san
EOF

it is not importing the volume, but renaming and deleting it. If we look in the ONTAP System Manager, we see that a Volume was delete, but with a different name.

Environment

• Trident version: 22.07.0
• Trident installation flags used: via helmchart operator
• Container runtime: docker://20.10.17
• Kubernetes version: 1.22.9
• Kubernetes orchestrator: Rancher v2.6.6
• OS: Ubuntu 20.04.4 LTS]
• NetApp backend types: ONTAP SAN

Expected behavior
It should just import it, so when you do

kubectl exec -n trident -it trident-csi-xxx -- tridentctl get volume

you the volume you imported.

[gnarl]

Hi @GentianRrafshi,

Trident doesn't delete volumes when they are imported. Trident does rename the volume during import as it is taking over lifecycle management of the volume. If you don't want Trident to manage the lifecycle of the volume or rename the volume then use the "unmanaged" option when importing the volume.

If you need additional assistance in root causing the issue you are reporting please open a NetApp support case.

[Ujkugri]

Hi,

so we found out, what the Problem was. We didn't delete the PV, but removed the Claimref and set it to deletionPolicy: Retain. After we deleted the PV, the volume was imported properly.

Although we now have the problem, that, as far as we understand, there is no supported way to migrate trident from one Namespace to another. Am I correct?

[gnarl]

@GentianRrafshi,

That is correct, we don't currently have a supported way to migrate Trident to another Namespace or another Kubernetes cluster.