-
Bug
-
Resolution: Unresolved
-
Normal
-
None
-
None
-
2
-
False
-
-
False
-
?
-
No Docs Impact
-
?
-
?
-
None
-
-
-
Low
When creating a SINGLE load balancer with a UDP listener+pool, the Amphora doesn't send a GARP to notify its (potentially new) VIP address.
In ACTIVE_STANDBY load balancer, the keepalived vrrp instance sends the GARP. With SINGLE haproxy-based listeners, the amphora-agent sends the GARP (https://github.com/openstack/octavia/blob/fd071d3391e5695e50748f74af4529186d63e472/octavia/amphorae/backends/agent/api_server/loadbalancer.py#L279-L284)
Reproducer in devstack:
$ sudo tcpdump -nn -i br-ex
[..]
$ openstack loadbalancer create --vip-subnet public-subnet --name lb1 --wait
[..]
| vip_address | 172.24.4.130 |
[..]
$ openstack loadbalancer listener create --wait --protocol UDP --protocol-port 1234 --name listener1 lb1
$ openstack loadbalancer pool create --wait --listener listener1 --protocol UDP --lb-algorithm ROUND_ROBIN --name pool1
$ openstack loadbalancer amphora show c97ce3fc-9936-4f6c-bd21-f09a4fad5441
[..]
| lb_network_ip | 192.168.0.10 |
| vrrp_ip | 172.24.4.28 |
| ha_ip | 172.24.4.130 |
[..]
| role | STANDALONE |
[..]
tcpdump displays:
08:11:03.907933 ARP, Request who-has 172.24.4.28 tell 172.24.4.28, length 28
08:11:04.909282 ARP, Request who-has 172.24.4.28 tell 172.24.4.28, length 28
08:11:06.910983 ARP, Request who-has 172.24.4.28 tell 172.24.4.28, length 28
08:11:10.915855 ARP, Request who-has 172.24.4.28 tell 172.24.4.28, length 28
08:11:18.924114 ARP, Request who-has 172.24.4.28 tell 172.24.4.28, length 28
No GARPs for the VIP address
