Open ybrock opened 3 weeks ago
@ybrock: Thank you for submitting this issue!
The issue is currently awaiting triage. Please make sure you have given us as much context as possible.
If the maintainers determine this is a relevant issue, they will remove the needs-triage label and respond appropriately.
We want your feedback! If you have any questions or suggestions regarding our contributing process/workflow, please reach out to us at container.storage.modules@dell.com.
Hi @ybrock We don’t have a release for the 1.10.1 CSI driver and CSM 1.3.1, Could you please confirm the correct CSI driver and CSM versions? Thank you!
Hi @satyakonduri
The helm chart used to install Dell CSM is 1.3.1 The CSI driver provided with this is in version v2.10.0 (tag of the image : registry.k8s.io/sig-storage/csi-node-driver-registrar:v2.10.0 and registry.access.redhat.com/dellemc/csi-isilon:v2.10.0 )
Sorry for the unprecision
Bug Description
Hello,
We have CSM modules 1.3.1 with CSI drivers version 1.10.1 installed on Openshift 4.14.35 (K8s 1.27.16).
We have Dell PowerScale (Isilon) configured and running ok except for this issue.
When we try to restore a snapshot from a PVC containing a symlink, the new PVC is never created (pending) and these events are reported in the CSI driver :
The
provisioner
container is rising this message :If there is no symlink in the file system, the snapshot restore works.
Logs
Screenshots
No response
Additional Environment Information
No response
Steps to Reproduce
create a PVC on a powerscale storageClass mount the PVC in a pod write a file into PVC create a symlink in the PVC pointing to previous file take a snapshot create a new PVC from restoring from previous snapshot
Expected Behavior
new PVC is created from snapshot
CSM Driver(s)
CSI 1.10.1 CSM 1.3.1
Installation Type
helm
Container Storage Modules Enabled
isilon karavi
Container Orchestrator
openshift 4.14 (crio)
Operating System
redhat coreos