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

change storage class restore item action #177

Open
jr0dd opened this issue Oct 6, 2021 · 0 comments
Open

change storage class restore item action #177

jr0dd opened this issue Oct 6, 2021 · 0 comments
Labels
Bug issue/pr is a bug/fix to existing feature

Comments

@jr0dd
Copy link

jr0dd commented Oct 6, 2021

I just wanted to report that your plugin does not like the change storage class restore item action. The restored datasets never zfs send|receive to the new sc location, but the pvc's and pv's reflect the new sc. This is on the same node. Was just trying to restore a backup from spinning drive zfs pool to a ssd pool. I had to manually run zfs send|receive and edit the zfsvolumes afterwards.

Using velero/velero-plugin-for-aws:v1.3.0 openebs/velero-plugin:3.0.0 on velero v1.7.0.

---
apiVersion: v1
kind: ConfigMap
metadata:
  # any name can be used; Velero uses the labels (below)
  # to identify it rather than the name
  name: change-storage-class-config
  # must be in the velero namespace
  namespace: velero
  # the below labels should be used verbatim in your
  # ConfigMap.
  labels:
    # this value-less label identifies the ConfigMap as
    # config for a plugin (i.e. the built-in restore item action plugin)
    velero.io/plugin-config: ""
    # this label identifies the name and kind of plugin
    # that this ConfigMap is for.
    velero.io/change-storage-class: RestoreItemAction
data:
  # add 1+ key-value pairs here, where the key is the old
  # storage class name and the value is the new storage
  # class name.
  openebs-zfspv-rust: openebs-zfspv-ssd
@jr0dd jr0dd added the Bug issue/pr is a bug/fix to existing feature label Oct 6, 2021
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