Snap Creator 3.4.1 fails to delete snapshots on the first storage defined in VOLUMES
Applies to
Snap Creator Framework (SCF) 4.3.1
Issue
When defining more than one SVM or Filer in the
VOLUMES
entry with each their own volumes, during the retention snapshot cleanup, it attempts to delete the snapshots on the volumes defined for the second (or later) storage, not finding the snapshot to delete:DEBUG: STORAGE-02015: Removing Snapshot copy [<CONFIG>_<DATETIME>] on [<VOLUME1>] failed with error [netapp.manage.NaAPIFailedException: Volume "<VOLUME1>" does not exist in Vserver "<STORAGE2>". Reason: entry doesn't exist. (errno=13040)]
INFO: SCF-00212: Snapshot copy [<CONFIG>_<DATETIME>] cannot be deleted for [<STORAGE2>]:[<VOLUME1>]. Retry attempt [1] after [5] seconds.
Snapshots on the first listed SVM/Filer with volumes will therefore remain behind unintentionally.