Bug 2116789

Description of problem:
After upgrading Openshift cluster from 4.8.45 to 4.9.43 upgrade was successful, but HAproxy pod in "openshift-vsphere-infra" namespace is having an issue.

Version-Release number of selected component (if applicable):
OCPv4.9.43

How reproducible:
Always in the customer environment 


Actual results:
- Event logs: 
Liveness probe error: Get "http://10.X.XX.XX:30936/haproxy_ready": dial tcp 10.X.X.XX:30936: connect: connection refused

- Pod logs: 
2022-08-05T07:30:22.227142409Z <133>Aug  5 07:30:22 haproxy[9]: Proxy masters started.
2022-08-05T07:30:22.227153811Z [NOTICE] 216/073022 (9) : haproxy version is 2.2.15-5e8f49d
2022-08-05T07:30:22.227153811Z [NOTICE] 216/073022 (9) : path to executable is /usr/sbin/haproxy
2022-08-05T07:30:22.227153811Z [ALERT] 216/073022 (9) : Starting proxy stats: cannot bind socket [::1:30000] 

- Port utilization from the affected node: 
tcp6       0      0 :::30000                :::*                    LISTEN      0          67764      6022/ovnkube         off (0.00/0/0)

- Pod Details:
$ omg get pods | grep haproxy-ocp4-fzcrc-master-0
haproxy-ocp4-fzcrc-master-0          1/2    Running  651       2d


Expected results:
The pod should run without any issue.

Additional info:

Infrastructure
--------------
Platform: VSphere
Install Type: IPI
CNI: OVN

[1] Version
NAME     VERSION  AVAILABLE  PROGRESSING  SINCE  STATUS
version  4.9.43   True       False        1d     Cluster version is 4.9.43

[2] Logs:
2022-08-05T07:30:22.204630055Z + declare -r haproxy_sock=/var/run/haproxy/haproxy-master.sock
2022-08-05T07:30:22.204834759Z + declare -r haproxy_log_sock=/var/run/haproxy/haproxy-log.sock
2022-08-05T07:30:22.204884780Z + export -f msg_handler
2022-08-05T07:30:22.204929603Z + export -f reload_haproxy
2022-08-05T07:30:22.204976092Z + export -f verify_old_haproxy_ps_being_deleted
2022-08-05T07:30:22.205032072Z + rm -f /var/run/haproxy/haproxy-master.sock /var/run/haproxy/haproxy-log.sock
2022-08-05T07:30:22.207401299Z + '[' -s /etc/haproxy/haproxy.cfg ']'
2022-08-05T07:30:22.207427223Z + socat UNIX-RECV:/var/run/haproxy/haproxy-log.sock STDOUT
2022-08-05T07:30:22.207660721Z + socat UNIX-LISTEN:/var/run/haproxy/haproxy-master.sock,fork 'system:bash -c msg_handler'
2022-08-05T07:30:22.207695876Z + /usr/sbin/haproxy -W -db -f /etc/haproxy/haproxy.cfg -p /var/lib/haproxy/run/haproxy.pid
2022-08-05T07:30:22.227090016Z <133>Aug  5 07:30:22 haproxy[9]: Proxy main started.
2022-08-05T07:30:22.227090016Z <133>Aug  5 07:30:22 haproxy[9]: Proxy health_check_http_url started.
2022-08-05T07:30:22.227142409Z <133>Aug  5 07:30:22 haproxy[9]: Proxy masters started.
2022-08-05T07:30:22.227153811Z [NOTICE] 216/073022 (9) : haproxy version is 2.2.15-5e8f49d
2022-08-05T07:30:22.227153811Z [NOTICE] 216/073022 (9) : path to executable is /usr/sbin/haproxy
2022-08-05T07:30:22.227153811Z [ALERT] 216/073022 (9) : Starting proxy stats: cannot bind socket [::1:30000]