Closed vrushch closed 7 months ago
Verified with the latest build 2.11.0, issue have been either fixed with the successive releases or not able to reproduce in the cluster.
@saurabhwani5 can you please verify this and close if not getting reproduced ?
issue is still reproducible
Message: Failed to create snapshot: failed to take snapshot of the volume 1;1;14016324136648177722;BB4A0B0A:65A5F92B;28b3ad9e-0358-48a2-9ba0-db57d885c621-ibm-spectrum-scale-csi-driver;pvc-365b9185-758e-4044-8496-94085eec80a7;/ibm/fs1/28b3ad9e-0358-48a2-9ba0-db57d885c621-ibm-spectrum-scale-csi-driver/pvc-365b9185-758e-4044-8496-94085eec80a7: "rpc error: code = Internal desc = snapshot for volume [pvc-365b9185-758e-4044-8496-94085eec80a7] in filesystem [fs1] is not taken. Wait till current snapWindow expires."
@saurabhwani5 do you see flooding of messages ?
closing as I don't see flooded logs
Describe the bug
When volumesnapshot is created and snapwindow is not expired, it is printing large number of logs messages in snapshotter and driver pod.
How to Reproduce?
Expected behavior
Logs should be manageable in number , even for one volumesnapshot pending in 10 minutes it shows
Data Collection and Debugging
Environmental output
Additional context
Message type in snapshooter logs
Message type in driver pods on node same as snapshotter pod