Closed kubevirt-bot closed 1 month ago
Issues
0 New issues
0 Accepted issues
Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code
/hold until https://github.com/kubevirt/project-infra/pull/3585 is merged
/approve
/hold cancel lanes are here
[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: RamLavi
The full list of commands accepted by this bot can be found here.
The pull request process is described here
2x failures on same (maybe a retest will work if it is transient) https://prow.ci.kubevirt.io/view/gs/kubevirt-prow/pr-logs/pull/kubevirt_cluster-network-addons-operator/1862/pull-e2e-cnao-ovs-cni-functests-release-0.95/1824053772339384320 https://prow.ci.kubevirt.io/view/gs/kubevirt-prow/pr-logs/pull/kubevirt_cluster-network-addons-operator/1862/pull-e2e-cnao-br-marker-functests-release-0.95/1824053771521495040
selecting podman as container runtime
Created symlink /etc/systemd/system/multi-user.target.wants/openvswitch.service → /usr/lib/systemd/system/openvswitch.service.
make: *** [Makefile:132: cluster-up] Error 1
+ EXIT_VALUE=2
/retest
(snapshotted failures above just in case)
/hold
we miss ipam lane here please maybe the git action manifest just need to not filter main if you want just remove hold, a follow-up PR can fix that ipam, but we must not forget it please
/hold cancel
https://github.com/kubevirt/cluster-network-addons-operator/pull/1866 lets see lane pass first there
What this PR does / why we need it: This PR updates components.yaml on the release branch release-0.95.