Description of problem:

this section:

https://docs.openshift.com/container-platform/4.10/backup_and_restore/application_backup_and_restore/troubleshooting.html#restic-backup-cannot-be-recreated-after-s3-bucket-emptied_oadp-troubleshooting

refers a wrong error message. Reads: "The velero pod log displays the error message, msg="Error checking repository for stale locks"."

That is not the error message one should look for when hitting this problem, but:
stderr=Fatal: unable to open config file: Stat: The specified key does not exist.\nIs there a repository at the following location?
 

also, would rephrase the `cause` as follows:

"Velero does not re-create/update the Restic repository from the ResticRepository manifest if the Restic directories are deleted on object storage. See (Velero issue 4421) for details."

Also, I think it worth mentioning the work around for this so the user would know how to escape this situation; that would be, by removing the related resitc repository on the namespace, i.e: `oc delete resticrepository openshift-adp <name-of-the-restic-repository>`. The name can be inferred from the error log, e.g:

for this error log:

time="2021-12-29T18:29:14Z" level=info msg="1 errors encountered backup up item" backup=velero/backup65 logSource="pkg/backup/backup.go:431" name=mysql-7d99fc949-qbkds time="2021-12-29T18:29:14Z" level=error msg="Error backing up item" backup=velero/backup65 error="pod volume backup failed: error running restic backup, stderr=Fatal: unable to open config file: Stat: The specified key does not exist.\nIs there a repository at the following location?\ns3:http://minio-minio.apps.mayap-oadp-veleo-1234.qe.devcluster.openshift.com/mayapvelerooadp2/velero1/restic/mysql-persistent\n: exit status 1" error.file="/remote-source/src/github.com/vmware-tanzu/velero/pkg/restic/backupper.go:184" error.function="github.com/vmware-tanzu/velero/pkg/restic.(*backupper).BackupPodVolumes" logSource="pkg/backup/backup.go:435" name=mysql-7d99fc949-qbkds 

it could be inferred that the "problematic" resticrepository would be called mysql-persistent:

Version-Release number of selected component (if applicable): 

OADP 1.0.z (any z-stream) and OADP 1.1.0

How reproducible: 100%

Steps to Reproduce:
1. Create a restic backup of a namespace
2. After the backup completes, empty the bucket and create another backup of the same namespace
3. check the status and the error logs

Actual results:

Expected results:

Additional info: