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

E2E test in v1.32.1 KinD environment action failed #8648

Open
blackpiglet opened this issue Jan 24, 2025 · 1 comment
Open

E2E test in v1.32.1 KinD environment action failed #8648

blackpiglet opened this issue Jan 24, 2025 · 1 comment
Assignees

Comments

@blackpiglet
Copy link
Contributor

What steps did you take and what happened:

https://github.com/vmware-tanzu/velero/actions/runs/12942675000/job/36100887919?pr=8647
Create a new PR. All E2E test actions in the v1.32.1 environment will fail.

What did you expect to happen:
The GitHub actions in v1.32.1 KinD environment should pass as before.

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

KinD bumped the containerd version to v2 in the v1.32.1 image, which was released recently, but there is no released KinD CLI to match it yet.

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):
  • Velero features (use velero client config get features):
  • Kubernetes version (use kubectl version):
  • Kubernetes installer & version:
  • Cloud provider or hardware configuration:
  • 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"
@blackpiglet
Copy link
Contributor Author

@kaovilai
Please also take a look. The KinD action ran in v1.32.0 k8s environment, and it worked.
After the action adopting fetching the latest patch version of each k8s minor version way, it's not easy to rollback to v1.32.0.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants