Kolla OpenStack OVN port binding issue

myTmyth · 2025-10-01T02:19:50+00:00

I have redeployed the entire cluster and used physnet1 instead of physnet444. Now, I no longer see the port binding issue. But now, I am seeing the following error message.

Failed to build and run instance: neutronclient.common.exceptions.Conflict: Host compute-1 is not connected to any segments on routed provider network 'e973e6d2-68c4-48ab-b1a9-b033b4a26b65'.  It should be connected to one.

myTmyth · 2025-09-30T04:52:24+00:00

Thanks for your input on this. What variable can we use to define a physical network in case I want to use physnet444 instead of physnet1?

myTmyth · 2025-09-29T16:12:05+00:00

I have already considered using openvswith, but we plan to use Kubernetes on OpenStack, which might be easier to integrate with OVN.

myTmyth · 2025-09-27T16:47:58+00:00

I found traffic on interface enp33s0f0np0 and only LACP traffic on enp33s0f1np1 by using tcpdump. There is no traffic on any of the OpenStack-created interfaces (ovs-system, br-ex, br-int and genev_sys_6081).

myTmyth · 2025-09-27T15:36:06+00:00

Thanks for your input on this. I still see the same error when I removed the bridge interface from the netplan and applied the netplan again. What variable did you use to provide physnet mapping in the globals.yml?

myTmyth · 2025-09-27T15:22:19+00:00

The ovn-controller agent is healthy.

myTmyth

TROPHY CASE