Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

An error occurred: backupstoragelocations.velero.io "default" not found #543

Open
SrideviPanyala opened this issue Feb 6, 2024 · 5 comments
Labels
bug Something isn't working velero

Comments

@SrideviPanyala
Copy link

I'm installing velero 1.13.1 using Helm chart and I getting error "An error occurred: backupstoragelocations.velero.io "default" not found". Also I don't see node agents are showing up.
Below is the command that I used to install in my AKS cluster.

helm install velero vmware-tanzu/velero
--namespace velero --create-namespace
--set-file credentials.secretContents.cloud=./credentials-velero-prod
--set configuration.backupStorageLocation[0].name=azure
--set configuration.backupStorageLocation[0].provider=azure
--set configuration.backupStorageLocation[0].bucket=storagebackupname
--set configuration.backupStorageLocation[0].config.region=westus
--set configuration.backupStorageLocation[0].config.resourceGroup=rgname
--set configuration.volumeSnapshotLocation[0].name=storageaccountname
--set configuration.volumeSnapshotLocation[0].provider=azure
--set configuration.volumeSnapshotLocation[0].provider=azure
--set configuration.volumeSnapshotLocation[0].config.region=westus
--set initContainers[0].name=velero-plugin-for-microsoft-azure
--set initContainers[0].image=velero/velero-plugin-for-microsoft-azure:master
--set initContainers[0].volumeMounts[0].mountPath=/target
--set initContainers[0].volumeMounts[0].name=plugins
--set snapshotsEnabled=true
--set use-node-agent=true

Can some one help me to fix the issue

@franznemeth
Copy link

Hi, we are facing the same issue.

There is an issue with velero 1.13 where velero crashes if there is no BSL called "default".
vmware-tanzu/velero#7359

Its also mentioned in the PR where the version was bumped to 1.13 but it seems the solution was to fix the tests: #535

We have downgraded to 5.2.2 again and will wait for a fix.

@jenting jenting added bug Something isn't working velero labels Feb 29, 2024
@mocdaniel
Copy link

Have you tried setting the following values? It works for me on 1.13 if I set those:

--set configuration.backupStorageLocation[0].default=true
--set configuration.defaultBackupStorageLocation=azure

@RobKenis
Copy link

RobKenis commented May 3, 2024

Have you tried setting the following values? It works for me on 1.13 if I set those:

--set configuration.backupStorageLocation[0].default=true
--set configuration.defaultBackupStorageLocation=azure

This won't work when you install Velero without a BSL in the helm values. We have a setup where we install Velero first and configure the BSL later. When upgrading to 6.0.0, Velero no longer starts because there's no BSL present in the cluster. Any workarounds?

@RobKenis
Copy link

RobKenis commented May 3, 2024

I have solved the issue by upgrading Velero to 0.13.2

@jenting
Copy link
Collaborator

jenting commented May 16, 2024

I have solved the issue by upgrading Velero to 0.13.2

v1.13.2?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working velero
Projects
None yet
Development

No branches or pull requests

5 participants