last server is not being removed from backend after consul service is deleted about haproxy HOT 10 CLOSED

Hi,
I am able to reproduce this behavior.
Will now work on a fix.

from haproxy.

Here you go:
0001-BUG-MINOR-dns-new-callback-to-properly-handle-SRV-re.patch.txt

Note that it's not the definitive one, I need to validate some corner cases.

from haproxy.

This patch was not merged at all and I don't really know why. @bedis, what is the status of this patch ?

from haproxy.

FYI, I finally push the proposed patch. For now it was backported to 2.3

from haproxy.

Same issue here using FreeBSD 12.1 HA-Proxy version 2.0.14 2020/04/02

I am using unbound forwarding queries to consul, using a configuration similar to:

resolvers consul
    nameserver dns0 10.0.0.3:53
    nameserver dns1 10.0.0.4:53
    nameserver dns2 10.0.0.5:53
    nameserver dns3 10.0.0.6:53
    nameserver dns4 10.0.0.7:53
    accepted_payload_size 8192
    hold valid 5s

backend test-consul
    default-server check fastinter 1s fall 3 rise 2 maxconn 30
    server-template srv 3 _test-consul._tcp.service.consul resolvers consul resolve-opts allow-dup-ip resolve-prefer ipv4

from haproxy.

Quick update here: I have a patch for 2.2 and above, which I adapted to 2.0 and 2.1. That said, 1.8 and 1.9 are also affected and part of the patch must be rewritten for those versions.
@nbari since you're on HAProxy 2.0, I can send you the patch for your version and you can give it a try and confirm whether it helps or not :)
@ivoronin same for you.

from haproxy.

hi @bedis thanks for your time on this 👍, I upgraded to HA-Proxy version 2.2.5-34b2b10 so that should be fine from my side.

from haproxy.

Any chance to include this in 2.2.9?

from haproxy.

@bedis, ping ?

from haproxy.

Now backported as far as 2.0.

from haproxy.