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

Remove PVC annotation openebs.io/created-through once restore completes #84

Closed
mynktl opened this issue May 12, 2020 · 1 comment
Closed
Labels
Bug issue/pr is a bug/fix to existing feature
Milestone

Comments

@mynktl
Copy link
Member

mynktl commented May 12, 2020

What steps did you take and what happened:
Refer openebs-archive/maya#1689

What did you expect to happen:
Plugin expects that CVR shouldn't have ip address set, to restore the snapshot in zfs dataset. To achieve that, plugin add the annotation in PVC. Once PVC is bound and CVR are created and updated, plugin should remove this annotation.

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 deployment/velero -n velero
  • kubectl logs deployment/maya-apiserver -n openebs
  • velero backup describe <backupname> or kubectl get backup/<backupname> -n velero -o yaml
  • velero backup logs <backupname>
  • velero restore describe <restorename> or kubectl get restore/<restorename> -n velero -o yaml
  • velero restore logs <restorename>

Anything else you would like to add:
[Miscellaneous information that will assist in solving the issue.]

Environment:

  • Velero version (use velero version):
  • Velero features (use velero client config get features):
  • Velero-plugin version
  • OpenEBS version
  • Kubernetes version (use kubectl version):
  • Kubernetes installer & version:
  • Cloud provider or hardware configuration:
  • OS (e.g. from /etc/os-release):
@mynktl
Copy link
Member Author

mynktl commented May 13, 2020

Fix is merged in #85 and release branch #86

@mynktl mynktl closed this as completed May 13, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug issue/pr is a bug/fix to existing feature
Projects
None yet
Development

No branches or pull requests

1 participant