Closed stefnats closed 2 years ago
Happened to other namespaces / helm charts as well, for example the bitnami mariadb & mongodb images. Same error messages.
I have seen PR #4686 in 1.9.0, so i installed Server version 1.9.0 but it still fails.
Client Version is 1.8.1, because on macOS homebrew, there is no newer version
I have now updated Client to 1.9.0, helm uninstalled everything, deleted CRDs from Velero and reinstalled it:
❯ velero version
Client:
Version: v1.9.0
Git commit: -
Server:
Version: v1.9.0
but still the same old error.
@stefnats
That log message means the plugin RemapCRDVersionAction
was skipped, which is expected behavior for the 1.22+ k8s cluster.
I have just met an error like @stefnats . The latest lines of velero logs are the same as you. Actually, my real issue is comes from the VolumeSnapshotClass
because it does not have the label velero.io/csi-volumesnapshot-class: "true"
@stefnats can you please run this command to check if it returns any error ?
velero backup logs rabbitmq-backup | grep error
This is my result
time="2022-07-08T17:31:59Z" level=info msg="1 errors encountered backup up item" backup=velero/k8s-jenkins-backup logSource="pkg/backup/backup.go:413" name=jenkins-0
time="2022-07-08T17:31:59Z" level=error msg="Error backing up item" backup=velero/k8s-jenkins-backup error="error executing custom action (groupResource=persistentvolumeclaims, namespace=jenkins, name=jenkins-home): rpc error: code = Unknown desc = failed to get volumesnapshotclass for storageclass ebs-sc: failed to get volumesnapshotclass for provisioner ebs.csi.aws.com, ensure that the desired volumesnapshot class has the velero.io/csi-volumesnapshot-class label" logSource="pkg/backup/backup.go:417" name=jenkins-0
Thanks @anhqqt so by adding the label to vsclass the problem's solved right?
@stefnats please confirm if you are seeing the same error, in a few days I may close this issue and the question regarding RemapCRDVersionAction
has been answered
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
Closing the stale issue.
Hey there,
i'm using the latest helm chart and the latest client:
I am also using Digitalocean (Kubernetes 1.22.8) and this helm chart yaml:
Now when backing up, for example with this command
It says:
Now my logs end with this:
What does this mean? I think it's a bug? Just FYI, i am using the RabbitMQ Kubernetes Operator to deploy that cluster.