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

Upgrade to 4.1.5 and higher failed with "SchemaError(io.velero.v1.Restore.spec.hooks.resources.postHooks.init.initContainers): array should have exactly one sub-item" #505

Open
bmalynovytch opened this issue Sep 28, 2023 · 2 comments
Labels
bug Something isn't working velero

Comments

@bmalynovytch
Copy link

bmalynovytch commented Sep 28, 2023

What steps did you take and what happened:
Upgrade step by step from chart v2.13.5 to 5.0.2, ended failing at 4.1.5 with

SchemaError(io.velero.v1.Restore.spec.hooks.resources.postHooks.init.initContainers): array should have exactly one sub-item

What did you expect to happen:
Shouldn't fail / break upgrade

Related to vmware-tanzu/velero#6382

@jenting jenting added the bug Something isn't working label Sep 29, 2023
@jenting jenting added the velero label Oct 11, 2023
@aiici
Copy link

aiici commented Dec 4, 2023

You can try to do it:

  1. kubectl delete customresourcedefinitions.apiextensions.k8s.io restores.velero.io
  2. kubectl delete customresourcedefinitions.apiextensions.k8s.io backuprepositories.velero.io
    If the first article is implemented and there is an error, the second article will be enforced

@jenting
Copy link
Collaborator

jenting commented Jan 10, 2024

Have you try the above solution?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working velero
Projects
None yet
Development

No branches or pull requests

4 participants
@bmalynovytch @jenting @aiici and others