Closed kubevirt-bot closed 1 month ago
/approve /lgtm
[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: lyarwood
The full list of commands accepted by this bot can be found here.
The pull request process is described here
I'm not sure what caused the functional tests to fail, but I saw lots of timeouts. I'll retrigger it again.
/retest
I'll run functional tests myself. This is weird because it didn't fail in release-v0.19
after it was backported.
Timed out waiting for SSP to be in phase Deployed.
This looks suspicious.
I'll try to run the tests again, just to be sure that there is no infrastructure issue.
/retest
@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 |
---|---|---|---|---|
ci/prow/e2e-upgrade-functests | 18cfc90aee2425cd97278dfcb1b3ee2a7f208c84 | link | true | /test e2e-upgrade-functests |
ci/prow/e2e-single-node-functests | 18cfc90aee2425cd97278dfcb1b3ee2a7f208c84 | link | true | /test e2e-single-node-functests |
ci/prow/e2e-functests | 18cfc90aee2425cd97278dfcb1b3ee2a7f208c84 | link | true | /test e2e-functests |
Full PR test history. Your PR dashboard.
The reported bug mentioned only virt-template-validator
and this PR also changes vm-console-proxy
. I'll open a new PR to change only virt-template-validator
.
/close
@codingben: Closed this PR.
Why not fix the vm-console-proxy
resources too?
Why not fix the
vm-console-proxy
resources too?
It wasn't mentioned in the Jira issue that also vm-console-proxy
is missing required labels. I'd prefer to keep it purposed.
If the same issue is with the proxy, and it was fixed in one PR in main
, then why separate it for backports?
is it related to the failing CI?
This is an automated cherry-pick of #787
/assign codingben