We need to stay current with latest point releases of haproxy-2.0 in OCP v4. In 4.4 we are using 2.0.13 In 4.5 we are using 2.0.14 The goal here is to take 2.0.15 for 4.6 and stay current with upstream bug fixes and enhancements.
There is a corresponding PR that is soak testing haproxy-2.0.15 in CI: https://github.com/openshift/router/pull/148
Pkg updates: - rhaos-4.6-rhel-7 https://pkgs.devel.redhat.com/cgit/rpms/haproxy/commit/?h=rhaos-4.6-rhel-7&id=f58a39ef8796cbc667a3c2da15c9ba512ef5bc98 - rhaos-4.6-rhel-8 https://pkgs.devel.redhat.com/cgit/rpms/haproxy/commit/?h=rhaos-4.6-rhel-8&id=de897a7b330da5d7725ea3138ffebdb68bb75828
Builds candidates: - rhaos-4.6-rhel-7 https://brewweb.engineering.redhat.com/brew/taskinfo?taskID=30363185 - rhaos-4.6-rhel-8 https://brewweb.engineering.redhat.com/brew/taskinfo?taskID=30363172 These just need verifying that the 2.0.16 RPMS are in a puddle: http://download.eng.bos.redhat.com/rcm-guest/puddles/RHAOS/AtomicOpenShift/4.6/latest/x86_64/os/Packages/ And that the version of haproxy reports as 2.0.16 in a OCP installation. e.g., $ oc rsh -n openshift-ingress router-<pod> haproxy -vv
I stood up a cluster this morning and see haproxy 2.0.16: aim@spicy:~/clusters/4.6.0-0.ci-2020-07-29-045931 $ oc rsh -n openshift-ingress router-default-77bb794dbf-4c8sw rpm -q haproxy20 haproxy20-2.0.16-1.el7.x86_64 $ oc rsh -n openshift-ingress router-default-77bb794dbf-4c8sw haproxy -v HA-Proxy version 2.0.16 2020/07/17 - https://haproxy.org/
Checked 4.6.0-0.nightly-2020-08-03-200401 and haproxy is updated to 2.0.16. sh-4.2$ haproxy -v HA-Proxy version 2.0.16 2020/07/17 - https://haproxy.org/ sh-4.2$ rpm -qa | grep haproxy haproxy20-2.0.16-1.el7.x86_64 didn't find any issue so far and will move to verify when regression test is done.
no issue found during regression test, moving to verified
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory (OpenShift Container Platform 4.6 GA Images), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2020:4196