You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Created a backup, named A, of cstor volume, named V1, using velero-plugin
Created restore of backup A which creates volume V2
Created backup, named B, of volume V2 using restic instead of velero-plugin
Created restore of backup B, which creates volume V3.
After creating restore, 4th step, restic is not able to restore the data and CVR are in error state.
[A clear and concise description of what the bug is, and what commands you ran.)
What did you expect to happen:
Restic restore should pass.
The output of the following commands will help us better understand what's going on:
(Pasting long output into a GitHub gist or other pastebin is fine.)
kubectl logs <maya-apiserver pod name> -n openebs (Optional)
Anything else you would like to add:
[Miscellaneous information that will assist in solving the issue.]
This happened because of annotation openebs.io/created-through: restore in PVC. Plugin or Maya-apiserver should remove this annotation once the PVC is bound.
velero-plugin apply the PVC, so better to handle PVC related operations from velero-plugin . Created an issue in velero-plugin for this openebs/velero-plugin#84
What steps did you take and what happened:
After creating restore, 4th step, restic is not able to restore the data and CVR are in error state.
[A clear and concise description of what the bug is, and what commands you ran.)
What did you expect to happen:
Restic restore should pass.
The output of the following commands will help us better understand what's going on:
(Pasting long output into a GitHub gist or other pastebin is fine.)
kubectl logs <maya-apiserver pod name> -n openebs
(Optional)Anything else you would like to add:
[Miscellaneous information that will assist in solving the issue.]
Environment:
kubectl version
):/etc/os-release
):The text was updated successfully, but these errors were encountered: