-
Notifications
You must be signed in to change notification settings - Fork 360
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
"unable to locate ObjectStore plugin named velero.io/aws" #608
Comments
It turned out that the solution was actually still a memory problem. In the release notes for v13.0.0:
This means we had to increase the memory limits of the pod to drastically above what we are used to, or manually set the disable-informer-cache option to false. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
What steps did you take and what happened:
After upgrading velero helm chart, restore of namespaces/resources from backups no longer functions. Rollback to previous version works as a temporary fix.
Velero helm chart was installed via helmfile. I upgraded the chart version from 5.2.1 (velero version 1.12.3) to 7.1.2 (velero version 1.14.0) and the velero-plugin-for-aws from 1.8.2 to 1.10.0. I also removed the initContainer for the velero-plugin-for-csi (this is built in for chart versions >= 7.0.0):
I created a backup of a namespace using velero:
velero create backup <backup name> --include-namespaces=<namespace name> --ttl 12h --wait
Attempting to restore the namespace from the backup, the velero pod would crash and the phase of the restore changed to "failed" (see output of following commands section):
kubectl delete namespace <namespace name>
velero restore create --from-backup <backup name>
Logs on the velero server show an error in getting the velero-plugin-for-aws:
velero server --log-level debug
ERRO[0007] Current BackupStorageLocations available/unavailable/unknown: 0/1/0, BackupStorageLocation "default" is unavailable: unable to locate ObjectStore plugin named velero.io/aws) controller=backup-storage-location logSource="pkg/controller/backup_storage_location_controller.go:178"
What did you expect to happen:
Expected the namespace to be recreated from the backup
The output of the following commands will help us better understand what's going on:
Following command is recommended after running a "velero restore create" to monitor progress
velero restore describe <restore name>
above command returns the following output:
Following command is also recommended after running a "velero restore create" to monitor progress:
velero restore logs <restore name>
This returns the following:
An error occurred: file not found
The aws plugin appears to have loaded to velero.
velero plugin get
returns a list of plugins including
Anything else you would like to add:
Increasing limits on the namespace/pods did not help the issue.
Environment:
helm version
): 3.15.3helm list -n <YOUR NAMESPACE>
): chart-version: velero-7.1.2, app-version: 1.14.0kubectl version
): v1.29.4-eks/etc/os-release
):The text was updated successfully, but these errors were encountered: