#26.02.01.

1 messages · Page 1 of 1 (latest)

gleaming gorge
#

After Upgrading to 26.02.01. we run into an issue that i dont understand . We created a backup with velero. We has 2 Backends a san and a nas backend.
The nasbackend worked but the sanbackend i got an error :

time="2026-05-21T17:12:55Z" level=warning msg="Snapshot not found." backend=<BACKEND> logLayer=core requestID=<REQ-ID-1> requestSource=CSI snapshotName=<SNAPSHOT-ID-1> volumeName=<PVC-ID-1> workflow="snapshot=delete"

time="2026-05-21T17:13:03Z" level=error msg="Could not expand snapshot config." error="snapshot content <SNAPSHOT-ID-2> not found; volumesnapshotcontents.snapshot.storage.k8s.io "<SNAPSHOT-ID-2>" not found" logLayer=csi_frontend requestID=<REQ-ID-2> requestSource=CSI snapName=<SNAPSHOT-ID-2> snapshotID=<PVC-ID-2>/<SNAPSHOT-ID-2> volumeName=<PVC-ID-2> workflow="snapshot=list"

time="2026-05-21T17:13:03Z" level=error msg="GRPC error: rpc error: code = NotFound desc = snapshot content <SNAPSHOT-ID-2> not found; volumesnapshotcontents.snapshot.storage.k8s.io "<SNAPSHOT-ID-2>" not found" logLayer=csi_frontend requestID=<REQ-ID-2> requestSource=CSI

time="2026-05-21T17:13:07Z" level=warning msg="Snapshot not found." backend=<BACKEND> logLayer=core requestID=<REQ-ID-3> requestSource=CSI snapshotName=<SNAPSHOT-ID-3> volumeName=<PVC-ID-3> workflow="snapshot=delete"

time="2026-05-21T17:13:42Z" level=info msg=">>>> CreateSnapshot" Method=CreateSnapshot Type=<DRIVER> requestID=<REQ-ID-4> requestSource=CSI snapConfig="&{1 <SNAPSHOT-ID-4> <SNAPSHOT-ID-4> <PVC-ID-3> <VOLUME-NAME-1> [] false }" snapshotName=<SNAPSHOT-ID-4> volumeName=<VOLUME-NAME-1>

time="2026-05-21T17:13:45Z" level=info msg="<<<< CreateSnapshot" Method=CreateSnapshot Type=<DRIVER> requestID=<REQ-ID-4> requestSource=CSI snapConfig="&{1 <SNAPSHOT-ID-4> <SNAPSHOT-ID-4> <PVC-ID-3> <VOLUME-NAME-1> [] false }" snapshotName=<SNAPSHOT-ID-4> volumeName=<VOLUME-NAME-1>

Is see luns on the netapp there are unmapped and has _snapshot_snapshot in the name.

gleaming gorge
trail wave
#

Currently, the only way around this is not to use custom names with the ontap-san-economy driver. It is slated to be fixed, but engineering hasn't committed it to a version yet.

gleaming gorge
#

Thanks for the information , so than we has to wait for a fix.. So i created the ticket 2010704752

trail wave
#

I'll make sure the case gets attached to the bug in hope that it helps the engineering manager speed the process.