velero: While Upgrading to chart version 6.0.0 getting default storage location error

What steps did you take and what happened: Upgraded chart for velero from 2.26.5 to 6.0.0

What did you expect to happen: Velero upgraded to new version and backup and restore to be working as before.

The following information will help us better understand what’s going on:

If you are using velero v1.7.0+:
Please use velero debug --backup <backupname> --restore <restorename> to generate the support bundle, and attach to this issue, more options please refer to velero debug --help Velero pod is in error state with the error:

time="2024-04-06T08:55:03Z" level=info msg="All Velero custom resource definitions exist" logSource="pkg/cmd/server/server.go:552"
An error occurred: backupstoragelocations.velero.io "default" not found

If you are using earlier versions:
Please provide the output of the following commands (Pasting long output into a GitHub gist or other pastebin is fine.)

  • kubectl logs deployment/velero -n velero
  • velero backup describe <backupname> or kubectl get backup/<backupname> -n velero -o yaml
  • velero backup logs <backupname>
  • velero restore describe <restorename> or kubectl get restore/<restorename> -n velero -o yaml
  • velero restore logs <restorename>

Anything else you would like to add:

Environment:

  • Velero version (use velero version): 1.13.0
  • Velero features (use velero client config get features):
  • Kubernetes version (use kubectl version):
  • Kubernetes installer & version: 1.26
  • Cloud provider or hardware configuration: AWS
  • OS (e.g. from /etc/os-release): Ubuntu

Vote on this issue!

This is an invitation to the Velero community to vote on issues, you can see the project’s top voted issues listed here.
Use the “reaction smiley face” up to the right of this comment to vote.

  • 👍 for “I would like to see this bug fixed as soon as possible”
  • 👎 for “There are more important bugs to focus on right now”

About this issue

  • Original URL
  • State: closed
  • Created 3 years ago
  • Reactions: 1
  • Comments: 22 (7 by maintainers)

Most upvoted comments

credentials with a ‘s’, so in plural 😃 You did use the singular

image

one related issue is https://github.com/vmware-tanzu/velero/issues/7359 @gravops please upgrade to velero v1.13.1