velero: restic-wait container never terminates with some storage backends

What steps did you take and what happened: I have found that with some storage backends (for example Longhorn, Linstor or direct CSI use of Hetzner Cloud volumes) , restic restores complete just fine but the restic-wait container waits for ever because a file or directory it expects in the path /restores/export/.velero/<uuid> is never created. This works fine with some storage backends but not with others. As a workaround, I can either delete the pods and recreate them, or mount the volume to a directory on the host and create manually the directory restic-wait is expecting. Done that restic-wait terminates and the pod(s) can start as expected.

What did you expect to happen: I would expect restic-wait to terminate successfully upon completion of the restore with any storage backend.

Environment:

• Velero version (use velero version): v1.0.0
• Kubernetes version (use kubectl version): v1.14.3
• Kubernetes installer & version: Rancher 2.2.6
• Cloud provider or hardware configuration: Hetzner Cloud
• OS (e.g. from /etc/os-release): CentOS 7