We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Hello Team, Getting following error in the logs when using openebs velero plugin for taking volume snapshots.
-------------------------- time="2023-05-16T07:49:13Z" level=info msg="Initializing velero plugin for CStor" backup=velero/backuptwo-16052023 cmd=/plugins/velero-blockstore-openebs logSource="/go/src/github.com/openebs/velero-plugin/pkg/snapshot/snap.go:36" pluginName=velero-blockstore-openebs time="2023-05-16T07:49:13Z" level=error msg="Error getting volume snapshotter for volume snapshot location" backup=velero/backuptwo-16052023 error="rpc error: code = Unknown desc = failed to get address for maya-apiserver/cvc-server service" error.file="/go/src/github.com/openebs/velero-plugin/pkg/cstor/cstor.go:259" error.function="github.com/openebs/velero-plugin/pkg/cstor.(*Plugin).Init" logSource="pkg/backup/item_backupper.go:524" name=pvc-xxxx-xxxx-xxxx namespace= persistentVolume=pvc-xxxx-xxxx-xxxx resource=persistentvolumes volumeSnapshotLocation=cstor-sp-velero time="2023-05-16T07:49:13Z" level=info msg="Persistent volume is not a supported volume type for snapshots, skipping." backup=velero/backuptwo-16052023 logSource="pkg/backup/item_backupper.go:544" name=pvc-xxxx-xxxx-xxxx namespace= persistentVolume=pvc-xxxx-xxxx-xxxx resource=persistentvolumes ------------------------
Any idea how to fix this is much appreciated.
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Hello Team,
Getting following error in the logs when using openebs velero plugin for taking volume snapshots.
Any idea how to fix this is much appreciated.
The text was updated successfully, but these errors were encountered: