Hello,
I’m running an Incus cluster with an OVN network setup using a bridge named incus-bridge as uplink. The load balancer IP 10.12.10.170/32 forwards to an nginx container at 10.6.31.5. Initially, I can curl the load balancer IP, but after some time it stops responding.
Using tcpdump on incus-bridge, I see continuous ARP requests for 10.12.10.170 with no replies. Restarting ovn-controller temporarily fixes connectivity. The IP 10.12.10.170 is not assigned to any host interface; I expect OVN to manage it via the physical interface ens160.
nginx container detail:
nginx-test | RUNNING | 10.6.31.5 (eth0) | CONTAINER (APP) | cluster-node-03
incus-bridge config manifest:
ipv4.address: 10.6.30.1/16
ipv4.dhcp: "true"
ipv4.dhcp.ranges: 10.6.30.1-10.6.30.254
ipv4.nat: "true"
ipv4.ovn.ranges: 10.6.31.1-10.6.31.254
ipv4.routes: 10.12.10.170/32, 10.12.10.171/32, 10.12.10.172/32
cluster-default-network config manifest:
bridge.mtu: "1442"
ipv4.address: 10.6.31.1/24
ipv4.nat: "true"
network: incus-bridge
volatile.network.ipv4.address: 10.6.31.1
Load balancer config for 10.12.10.170:
backends:
- name: nginx
target_port: "80"
target_address: 10.6.31.5
ports:
- protocol: tcp
listen_port: "80"
target_backend:
- nginx
listen_address: 10.12.10.170
Tcpdump outputs:
...
08:16:44.833221 ARP, Request who-has 10.12.10.170 tell ubuntu2204, length 28
08:16:45.857252 ARP, Request who-has 10.12.10.170 tell ubuntu2204, length 28
...
How should OVN handle this floating IP to answer ARP requests reliably and avoid intermittent failures? Is there a recommended way to bind or assign the IP on the physical interface or host side?
Thanks!