WIP check main branch state

[oshoval]

What this PR does / why we need it:

Special notes for your reviewer:

Release note:

[kubevirt-bot]

Adding the "do-not-merge/release-note-label-needed" label because no release-note block was detected, please follow our release note process to remove it.

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-sigs/prow repository.

[kubevirt-bot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[oshoval]

@RamLavi
KMP is broken on clean main can you please take a look ?
https://prow.ci.kubevirt.io/view/gs/kubevirt-prow/pr-logs/pull/kubevirt_cluster-network-addons-operator/1944/pull-cluster-network-addons-operator-unit-test/1868306825892335616

cc @ashokpariya0

[oshoval]

all the other lanes fails also due to that it seems

[RamLavi]

should work now
/retest

[ashokpariya0]

should work now /retest

No, It will not work, we need to merge this pr: #1945

[oshoval]

rest of the lanes might, just not ipam
step by step ;]

[oshoval]

first time i see this error seems it affect now (assuming this is the root error)

error applying manifest configmaps "grafana-dashboard-prometheus" already exists
maybe need to bump kubevirtci ? not sure what was changed
maybe there is somehow double deploy of that now

[ashokpariya0]

for multus func tests are also failing with below error:

/tmp/cnao//cluster-network-addons-operator/cluster/kubectl.sh apply -f -
selecting podman as container runtime
nmstate.nmstate.io/nmstate created

• sleep 30
• /tmp/cnao//cluster-network-addons-operator/cluster/kubectl.sh rollout status -w -n nmstate ds nmstate-handler
  selecting podman as container runtime
  Error from server (NotFound): daemonsets.apps "nmstate-handler" not found
• teardown
• rm -rf /tmp/deploy.multus.Xe5a/github.com/k8snetworkplumbingwg/multus-cni
• cd /tmp/cnao//cluster-network-addons-operator
• make cluster-down

[oshoval]

/test pull-e2e-cluster-network-addons-operator-multus-functests
lets see if it is gone, worth to try and update nmstate
https://prow.ci.kubevirt.io/view/gs/kubevirt-prow/pr-logs/pull/kubevirt_cluster-network-addons-operator/1944/pull-e2e-cluster-network-addons-operator-multus-functests/1868575389849227264

[oshoval]

/retest
lets give another chance for the others as some passed

[oshoval]

merged ipam fix
thanks
#1945

[oshoval]

ah need to rebase for git actions
will try soon, waiting to see the other lanes first

EDIT once they pass we can close this sanity check PR
and continue on the real ones

[oshoval]

kmp related passed
thx