Hi Reinhard, On Mon, Sep 21, 2020 at 03:29:17PM +0200, Reinhard Vicinus wrote: > Hi, > > the following haproxy configuration produces different results with > haproxy 2.0.16 (and 1.8.20) vs 2.2.3 running with "haproxy -f > haproxy.conf -d": > > global > stats socket /tmp/haproxy.sock mode 660 user haproxy group haproxy > level admin > > defaults > mode http > > frontend fe-a > bind :10001 > http-request track-sc0 src table be-a > http-request track-sc0 src table be-b > > backend be-b > stick-table type ip size 100k expire 30s store > gpc0,http_req_rate(10s),http_err_rate(10s) > > backend be-a > stick-table type ip size 100k expire 30s store > gpc0,http_req_rate(10s),http_err_rate(10s) > > With haproxy 2.0.16 (and 1.8.20) only the table be-a gets updated. With > haproxy 2.2.3 both table gets updated.
Oh this is weird. I don't even know how this is possible, because the principle of the action is that once we have the tracker enabled, it cannot change. Thus I suspect we possibly broke something at the low level in the action processing maybe. Definitely something we need to have a look at! Thanks, Willy
