Closed saurabhwani5 closed 7 months ago
one log improvement is required in case of volume expansion of shallow copy volume , I get following log error fileset [pvc-618bb79e-8edc-475f-a22e-a2bde8083bde] does not exist in filesystem [fs0]
Events:
Type Reason Age From Message
---- ------ ---- ---- -------
Normal Provisioning 10m spectrumscale.csi.ibm.com_ibm-spectrum-scale-csi-provisioner-5476667595-hwlc4_3498e9f8-283d-47db-b8b9-8786f15c2109 External provisioner is provisioning volume for claim "ibm-spectrum-scale-csi/ibm-spectrum-scale-pvc-from-snapshot-2"
Normal ExternalProvisioning 10m (x3 over 10m) persistentvolume-controller waiting for a volume to be created, either by external provisioner "spectrumscale.csi.ibm.com" or manually created by system administrator
Normal ProvisioningSucceeded 10m spectrumscale.csi.ibm.com_ibm-spectrum-scale-csi-provisioner-5476667595-hwlc4_3498e9f8-283d-47db-b8b9-8786f15c2109 Successfully provisioned volume pvc-618bb79e-8edc-475f-a22e-a2bde8083bde
Warning ExternalExpanding 9m35s volume_expand Ignoring the PVC: didn't find a plugin capable of expanding the volume; waiting for an external controller to process this PVC.
Normal Resizing 4m27s (x13 over 9m35s) external-resizer spectrumscale.csi.ibm.com External resizer is resizing volume pvc-618bb79e-8edc-475f-a22e-a2bde8083bde
Warning VolumeResizeFailed 4m23s (x13 over 9m26s) external-resizer spectrumscale.csi.ibm.com resize volume "pvc-618bb79e-8edc-475f-a22e-a2bde8083bde" by resizer "spectrumscale.csi.ibm.com" failed: rpc error: code = Internal desc = fileset [pvc-618bb79e-8edc-475f-a22e-a2bde8083bde] does not exist in filesystem [fs0]. Error [<nil>]
log improvement of shallow copy expansion is added in #1109 and verified , thanks @hemalathagajendran
Describe the bug
For not supported shallow copy volumes creation, we are giving only one error message as
CreateVolume ValidateShallowCopyVolume failed
, we can add more logs here to get detailed information about the exact issue in shallow copy creation.How to Reproduce?
Install CSI with shallow copy images #1083 :
Create source PVC of version 2 as following:
apiVersion: v1 kind: PersistentVolumeClaim metadata: name: scale-advance-pvc-1 spec: accessModes:
apiVersion: storage.k8s.io/v1 kind: StorageClass metadata: name: ibm-spectrum-scale-csi-advance provisioner: spectrumscale.csi.ibm.com parameters: volBackendFs: "fs0" version: "2" reclaimPolicy: Delete [OCP~ ]# oc get pvc NAME STATUS VOLUME CAPACITY ACCESS MODES STORAGECLASS AGE scale-advance-pvc-1 Bound pvc-01e37192-9fbd-457d-b526-406733250c1c 1Gi RWX ibm-spectrum-scale-csi-advance 21m
apiVersion: snapshot.storage.k8s.io/v1 kind: VolumeSnapshot metadata: name: ibm-spectrum-scale-snapshot spec: volumeSnapshotClassName: ibm-spectrum-scale-snapshotclass-advance source: persistentVolumeClaimName: scale-advance-pvc-1
apiVersion: snapshot.storage.k8s.io/v1 kind: VolumeSnapshotClass metadata: name: ibm-spectrum-scale-snapshotclass-advance driver: spectrumscale.csi.ibm.com parameters: snapWindow: "30" #Optional : Time in minutes (default=30) deletionPolicy: Delete [OCP~ ]# oc get vs NAME READYTOUSE SOURCEPVC SOURCESNAPSHOTCONTENT RESTORESIZE SNAPSHOTCLASS SNAPSHOTCONTENT CREATIONTIME AGE ibm-spectrum-scale-snapshot true scale-advance-pvc-1 1Gi ibm-spectrum-scale-snapshotclass-advance snapcontent-4e87919c-89f0-425a-bbbc-454bf33b94a5 18m 18m
[OCP~ ]# cat snapshot.yaml apiVersion: v1 kind: Pod metadata: name: csi-scale-fsetdemo-pod-snapshot labels: app: nginx spec: containers:
name: mypvc persistentVolumeClaim: claimName: ibm-spectrum-scale-pvc-from-snapshot readOnly: false
apiVersion: v1 kind: PersistentVolumeClaim metadata: name: ibm-spectrum-scale-pvc-from-snapshot spec: accessModes:
Expected behavior
Log improvement can be done here to know why validation is failed in shallow copy creation ,we have done log improvement in clone operation where we are giving errors such as
we can create same type of error logs in shallow copy