velero: Velero 1.5.1 error="backupstoragelocations.velero.io \"default\" not found"

What steps did you take and what happened:

Installed Velero 1.5.1 in a baremetal cluster with S3 hosted on Rook-ceph object storage

velero install  --provider aws  --plugins velero/velero-plugin-for-aws:v1.0.0  --bucket velero-bucket   --secret-file ./credentials-velero-k8sstorage  --use-volume-snapshots=true  --backup-location-config region=default,s3ForcePathStyle="true",s3Url=http://rook-s3.10.131.228.112.nip.io  --image velero/velero:v1.5.1   --snapshot-location-config region="default"  --use-restic

Getting this error logs

time="2021-01-13T14:04:49Z" level=error msg="Error patching backup location's last-synced time" backupLocation=default controller=backup-sync error="backupstoragelocations.velero.io \"default\" not found" error.file="/go/src/github.com/vmware-tanzu/velero/pkg/controller/backup_sync_controller.go:311" error.function="github.com/vmware-tanzu/velero/pkg/controller.(*backupSyncController).run" logSource="pkg/controller/backup_sync_controller.go:311"
time="2021-01-13T14:04:58Z" level=info msg="Checking for existing backup locations ready to be verified; there needs to be at least 1 backup location available" controller=backupstoragelocation logSource="pkg/controller/backupstoragelocation_controller.go:58"
time="2021-01-13T14:04:58Z" level=error msg="Error updating backup location phase" backupstoragelocation=default controller=backupstoragelocation error="backupstoragelocations.velero.io \"default\" not found" logSource="pkg/controller/backupstoragelocation_controller.go:115"
time="2021-01-13T14:05:20Z" level=error msg="Error patching backup location's last-synced time" backupLocation=default controller=backup-sync error="backupstoragelocations.velero.io \"default\" not found" error.file="/go/src/github.com/vmware-tanzu/velero/pkg/controller/backup_sync_controller.go:311" error.function="github.com/vmware-tanzu/velero/pkg/controller.(*backupSyncController).run" logSource="pkg/controller/backup_sync_controller.go:311

Try to take backup - It does not complete in time

 velero backup create nginx-test --include-namespaces test-nginx --wait
Backup request "nginx-test" submitted successfully.
Waiting for backup to complete. You may safely press ctrl-c to stop waiting - your backup will continue in the background.
............................................................................................................................................^C

 velero backup-location get
NAME      PROVIDER   BUCKET/PREFIX   PHASE     LAST VALIDATED   ACCESS MODE
default   aws        velero-bucket   Unknown   Unknown          ReadWrite

In the same testbed , deleted Velero namespace and installed v1.4.0 version

velero install  --provider aws  --plugins velero/velero-plugin-for-aws:v1.0.0  --bucket velero-bucket   --secret-file ./credentials-velero-k8sstorage  --use-volume-snapshots=true  --backup-location-config region=default,s3ForcePathStyle="true",s3Url=http://rook-s3.10.131.228.112.nip.io  --image velero/velero:v1.4.0   --snapshot-location-config region="default"  --use-restic

Took backup, everything works; No change between these two related to anything - S3 URL, access keys etc; Only version change

velero backup create nginx-test --include-namespaces test-nginx --wait
Backup request "nginx-test" submitted successfully.
Waiting for backup to complete. You may safely press ctrl-c to stop waiting - your backup will continue in the background.

Backup completed with status: Completed. You may check for more information using the commands velero backup describe nginx-test and velero backup logs nginx-test.

alex@N-20HEPF0ZU9PR:/mnt/c/Users/acp/Documents/certs3/ee$ velero backup-location get
NAME      PROVIDER   BUCKET/PREFIX   PHASE     LAST VALIDATED   ACCESS MODE
default   aws        velero-bucket   Unknown   Unknown          ReadWrite


velero get backup
NAME         STATUS      ERRORS   WARNINGS   CREATED                         EXPIRES   STORAGE LOCATION   SELECTOR
nginx-test   Completed   0        0          2021-01-15 15:36:17 +0530 DST   29d       default            <none>

Backup is proper in S3 
$ mc ls  k8sstorage/velero-bucket/backups
[2021-01-15 15:46:08 DST]     0B nginx-test/

**Expected behaviour **

Velero installation with v1.5.1 should work

About this issue

Original URL
State: closed
Created 3 years ago
Reactions: 6
Comments: 17 (5 by maintainers)

Most upvoted comments

Hey @zubron, yes we are using 1.5.2.

richardmatthewsdev on Jan 19, 2021

@supasteev0 Your logs don’t look like an error - those are expected log messages.

@giordyb Can you be more specific on which issue you’re having? I think folks are reporting multiple issues here.

@alexcpn and @rflorenc - can you provide the output of kubectl get crd/backupstoragelocation.velero.io -o yaml - we should see a Status.Phase field in it. Otherwise, the CRD needs to be upgraded.

See step 2 in https://velero.io/docs/v1.5/upgrade-to-1.5/#docs

nrb on Jan 25, 2021

Hey, we are experiencing the same issue. Downgrading to 1.4.3 fixes the problem. We have tried reinstalling the CRDs as described in the link but still no luck.

richardmatthewsdev on Jan 19, 2021