Empty volume causes restic mover to get stuck

[JohnStrunk]

Describe the bug

• Restic generates an error if it's told to backup an empty directory. This causes the mover pod to error and get repeatedly restarted.
• Once some data is placed into the volume, this error condition should resolve, but it does not because the initial snapped/cloned volume is not recreated until a sync completes.
• Since a sync never completes, the temporary data volume is never recreated

Steps to reproduce Create a replicationsource using the restic mover w/ a copyMethod of Snapshot or Clone, and provide a source volume that is empty (a PVC w/ no data in it)

Expected behavior Once data is placed in the volume, backups should start being created correctly

Actual results Restic/scribe gets stuck indefinitely

Additional context Workaround:

• Delete the temporary data volume (and snapshot, if applicable) that Scribe is using
• Delete the mover job

[JohnStrunk]

Mover pod log:

$ kubectl -n test logs pod/scribe-restic-src-datavol-source-6bwcw
Scribe restic container version: helm-v0.1.0-76-g586ca46-dirty
backup
Testing mandatory env variables
== Initialize Dir =======
=== Starting backup ===
/data /
no parent snapshot found, will read all files
[0:00] 0 files, 0 B, 0 errors
Fatal: unable to save snapshot: snapshot is empty