Closed oshoval closed 1 month ago
@brianmcarey why we still have check-up-kind-1.27-vgpu if we have check-up-kind-1.30-vgpu can we drop 1.27 lane / provider ?
otoh kubevirt itself still use pull-kubevirt-e2e-kind-1.27-vgpu maybe the whole effort is still wip
Thanks
/test check-provision-k8s-1.28
@oshoval: The following test failed, say /retest
to rerun all failed tests or /retest-required
to rerun all mandatory failed tests:
Test name | Commit | Details | Required | Rerun command |
---|---|---|---|---|
check-up-kind-1.27-vgpu | dfb72de0d804e225388118f865fcff858793db9b | link | false | /test check-up-kind-1.27-vgpu |
Hi @brianmcarey can you review please?
/lgtm /approve
[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: qinqon
The full list of commands accepted by this bot can be found here.
The pull request process is described here
What this PR does / why we need it: Also fix bump script to not deploy OVS and kubevirt ipam controller, as they are not required when using vm based providers.
Which issue(s) this PR fixes (optional, in
fixes #<issue number>(, fixes #<issue_number>, ...)
format, will close the issue(s) when PR gets merged): Fixes #Special notes for your reviewer:
Checklist
This checklist is not enforcing, but it's a reminder of items that could be relevant to every PR. Approvers are expected to review this list.
Release note: