A recent fix was introduced for "del backend" on 3.4 when deleting the
first proxy declared in the configuration. This issue does not affect
the current development tree.
To ensure this case is safe, complete backend deletion reg-test with a
deletion on the first declared proxy. This could prevent any future
regression for this particular case.
This should be backported up to 3.4.
timeout client "${HAPROXY_TEST_TIMEOUT-5s}"
timeout server "${HAPROXY_TEST_TIMEOUT-5s}"
+ backend be_first
+
frontend fe
bind "fd@${feS}"
use_backend be_ref
send "show stat be 2 -1"
expect !~ "be,BACKEND,"
+
+ # ensures freeing the first declared proxy is safe
+ send "unpublish backend be_first; del backend be_first"
+ expect ~ "Backend deleted."
}
haproxy h1 -cli {