flake, kubevirt, local, ipv4: Could not resolve host: kubernetes.default.svc.cluster.local

[qinqon]

After fixin the false possitive of kubevirt lane for local gateway and ipv4 the following error is poping up

Could not resolve host: kubernetes.default.svc.cluster.local

link: https://github.com/ovn-org/ovn-kubernetes/actions/runs/8322405794/job/22770782460?pr=4224

kind-logs-kv-live-migration-noHA-local-ipv4-SnatGW-1br-8322405794.zip

[qinqon]

/label ci-flake kubevirt e2e-testing

[maiqueb]

/cc

[qinqon]

@tssurya can you label the Issue ? I have no permissions

[maiqueb]

@tssurya can you label the Issue ? I have no permissions

What labels do you want in this ? I think I can set them.

[qinqon]

Running locally works fine.

Troubleshooting it here qinqon#13

[qinqon]

Just after live-migration the VM is not able to resolve kubernetes svc

At dual stack is working most of the time because is doing some extra check before arriving to the n/s traffic check, so this issue is independent of the kind of lane.

Using nslookup we see that just after live migration before it get settle we see the following

communications error to 10.96.0.10#53: timed out

[qinqon]

https://github.com/ovn-org/ovn-kubernetes/actions/runs/8478907825/job/23232584804?pr=4246

[oshoval]

Hi, happens here as well
https://github.com/ovn-org/ovn-kubernetes/actions/runs/8466885208/job/23197570025?pr=4153

Thanks

[flavio-fernandes]

Hit it here as well: https://github.com/ovn-org/ovn-kubernetes/actions/runs/8531334483/job/23371399130?pr=4103

[flavio-fernandes]

Hi it here as well: https://github.com/ovn-org/ovn-kubernetes/actions/runs/9003609653/job/24735895949?pr=4303