kubevirt
kubevirt copied to clipboard
kubevirt
[release-1.2] Improve the handling of ordinal pod interface name for upgrade
This is an automated cherry-pick of #11678
/assign EdDev
Improve the handling of ordinal pod interface name for upgrade
[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: AlonaKaplan
The full list of commands accepted by this bot can be found here.
The pull request process is described here
- ~~pkg/network/OWNERS~~ [AlonaKaplan]
Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment
/retest-required
This bot automatically retries required jobs that failed/flaked on approved PRs.
Silence the bot with an /lgtm cancel or /hold comment for consistent failures.
/retest-required
This bot automatically retries required jobs that failed/flaked on approved PRs.
Silence the bot with an /lgtm cancel or /hold comment for consistent failures.
/retest-required
This bot automatically retries required jobs that failed/flaked on approved PRs.
Silence the bot with an /lgtm cancel or /hold comment for consistent failures.
/retest-required
This bot automatically retries required jobs that failed/flaked on approved PRs.
Silence the bot with an /lgtm cancel or /hold comment for consistent failures.
✋🧢
/hold
Dear @kubevirt-commenter-bot
⚠️ this pull request exceeds the number of retests that are allowed per individual commit.
🔎 Please check that the changes you committed are fine and that there are no infrastructure issues present!
- [ ] your changes compile
- [ ] your tests succeed locally, i.e. for k/kubevirt see
- [ ] no linting errors
- [ ] no recurring e2e test errors, i.e. in the
pull-kubevirt-check-tests-for-flakeslane - [ ] no infrastructure issues, i.e.
- GitHub Status,
- quay.io status at status.redhat.com or
- KubeVirt prow status
💬 How we calculate the number of retests: The number of retest comments are the number of /test or /retest comments after the latest commit only.
👌 After all issues have been resolved, you can remove the hold on this pull request by commenting /unhold on it.
🙇 Thank you, your friendly referee automation, on behalf of the @sig-buildsystem and the KubeVirt community!
@kubevirt-bot: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:
| Test name | Commit | Details | Required | Rerun command |
|---|---|---|---|---|
| pull-kubevirt-unit-test-arm64 | 3d22893dda229cfd0793beb54cf64271f9b69a17 | link | false | /test pull-kubevirt-unit-test-arm64-1.2 |
| pull-kubevirt-goveralls | 3d22893dda229cfd0793beb54cf64271f9b69a17 | link | false | /test pull-kubevirt-goveralls-1.2 |
| pull-kubevirt-e2e-arm64 | 3d22893dda229cfd0793beb54cf64271f9b69a17 | link | false | /test pull-kubevirt-e2e-arm64-1.2 |
| pull-kubevirt-e2e-kind-1.27-vgpu | 3d22893dda229cfd0793beb54cf64271f9b69a17 | link | true | /test pull-kubevirt-e2e-kind-1.27-vgpu-1.2 |
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.