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

Unsupported value: "RestoreVolumeInfo" #8326

Open
amrap030 opened this issue Oct 21, 2024 · 2 comments
Open

Unsupported value: "RestoreVolumeInfo" #8326

amrap030 opened this issue Oct 21, 2024 · 2 comments
Assignees
Labels
Area/CLI related to the command-line interface Needs info Waiting for information

Comments

@amrap030
Copy link

What steps did you take and what happened:

I just tried to restore a backupt with the following command: velero restore create restore01 --include-namespaces cert-manager --from-backup velero-daily-20241017030011

When I then run velero restore describe restore01 I can see the following error:

Restore PVs:  auto
              <error getting restore volume info: DownloadRequest.velero.io "restore01-1fe601c7-105a-4cf3-8a56-81f74fc0f4e2" is invalid: spec.target.kind: Unsupported value: "RestoreVolumeInfo": supported values: "BackupLog", "BackupContents", "BackupVolumeSnapshots", "BackupItemOperations", "BackupResourceList", "BackupResults", "RestoreLog", "RestoreResults", "RestoreResourceList", "RestoreItemOperations", "CSIBackupVolumeSnapshots", "CSIBackupVolumeSnapshotContents", "BackupVolumeInfos">

I made sure that all latest crds are installed but I still get the error.

What did you expect to happen:

I expect to restore the backup without errors.

The following information will help us better understand what's going on:

If you are using velero v1.7.0+:
Please use velero debug --backup <backupname> --restore <restorename> to generate the support bundle, and attach to this issue, more options please refer to velero debug --help

If you are using earlier versions:
Please provide the output of the following commands (Pasting long output into a GitHub gist or other pastebin is fine.)

  • kubectl logs deployment/velero -n velero
  • 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:

Environment:

  • Velero version (use velero version): 1.14.1
  • Velero features (use velero client config get features):
  • Kubernetes version (use kubectl version): v1.31.1
  • Kubernetes installer & version: juju charms
  • Cloud provider or hardware configuration: Openstack
  • OS (e.g. from /etc/os-release):

Vote on this issue!

This is an invitation to the Velero community to vote on issues, you can see the project's top voted issues listed here.
Use the "reaction smiley face" up to the right of this comment to vote.

  • 👍 for "I would like to see this bug fixed as soon as possible"
  • 👎 for "There are more important bugs to focus on right now"
@reasonerjt
Copy link
Contributor

For an error like this

spec.target.kind: Unsupported value: "RestoreVolumeInfo": supported values: "BackupLog", "BackupContents", "BackupVolumeSnapshots", "BackupItemOperations", "BackupResourceList", "BackupResults", "RestoreLog", "RestoreResults", "RestoreResourceList", "RestoreItemOperations", "CSIBackupVolumeSnapshots", "CSIBackupVolumeSnapshotContents", "BackupVolumeInfos">

I honestly think it is b/c the CRD for "DownloadRequest" is not updated.

@kaovilai
Copy link
Contributor

reinstalling velero (or just the CRDs that matches the version in the current velero deployment) should work.

@Lyndon-Li Lyndon-Li added the Area/CLI related to the command-line interface label Oct 24, 2024
@reasonerjt reasonerjt added the Needs info Waiting for information label Oct 25, 2024
@reasonerjt reasonerjt self-assigned this Oct 28, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Area/CLI related to the command-line interface Needs info Waiting for information
Projects
None yet
Development

No branches or pull requests

4 participants