Bug 2212246
| Summary: | haproxy stats still showing status as OPEN after disabling frontend | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 9 | Reporter: | Nghia Le <trongnghia203> |
| Component: | haproxy | Assignee: | Ryan O'Hara <rohara> |
| Status: | CLOSED ERRATA | QA Contact: | Juraj Hrdlica <jhrdlica> |
| Severity: | high | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | CentOS Stream | CC: | bstinson, jhrdlica, jwboyer |
| Target Milestone: | rc | Keywords: | Bugfix, Triaged, Upgrades, Upstream |
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | haproxy-2.4.22-1.el9 | Doc Type: | If docs needed, set a value |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2023-11-07 08:35:32 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
Nghia Le
2023-06-05 02:51:05 UTC
I rebased haproxy for RHEL 9.3 (rhbz#2196530), so this will be fixed in the next release. I have not had time to test it yet, but I did confirm that all code changes required for the fix are present. I was able to download haproxy-2.4.22-1.el9 from https://kojihub.stream.centos.org/koji/buildinfo?buildID=33526 and test it. ### [root@jbalancer01:~] echo "disable frontend main-ssl" | sudo socat stdio /var/lib/haproxy/stats2 [root@jbalancer01:~] echo 'show stat -1 1 -1' | sudo socat stdio /var/lib/haproxy/stats2 | grep main-ssl,FRONTEND main-ssl,FRONTEND,,,0,0,3000,0,0,0,0,0,0,,,,,PAUSED,,,,,,,,,2,2,0,,,,0,0,0,0,,,,,,,,,,,0,0,0,,,0,0,0,0,,,,,,,,,,,,,,,,,,,,,tcp,,0,0,0,,0,0,0,,,,,,,,,,,0,,,,,,,,,-,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0, ### As the result, haproxy stats now showing status "PAUSED" after disabling, instead of "STOP" as before, but it would be the new behavior changed in haproxy repository, and it's acceptable. Thanks Ryan O'Hara for the fix. Hi Ryan, may I ask when package haproxy.22 released to upstream repo, please? I've observed the https://pkgs.org/search/?q=haproxy, but it doesn't seem like the new version released there. Thanks Verified for haproxy-2.4.22-1.el9.x86_64 # cat /etc/haproxy/haproxy.cfg global stats socket /var/lib/haproxy/stats2 mode 660 level admin expose-fd listeners frontend my_frontend timeout connect 300 timeout client 300 timeout server 300 bind *:80 mode tcp # systemctl start haproxy # echo "show stat" | socat stdio /var/lib/haproxy/stats2 | grep my_frontend my_frontend,FRONTEND,,,0,0,262129,0,0,0,0,0,0,,,,,OPEN,,,,,,,,,1,2,0,,,,0,0,0,0,,,,,,,,,,,0,0,0,,,0,0,0,0,,,,,,,,,,,,,,,,,,,,,tcp,,0,0,0,,0,0,0,,,,,,,,,,,0,,,,,,,,,-,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0, # echo "disable frontend my_frontend" | socat stdio /var/lib/haproxy/stats2 # echo "show stat" | socat stdio /var/lib/haproxy/stats2 | grep my_frontend my_frontend,FRONTEND,,,0,0,262129,0,0,0,0,0,0,,,,,PAUSED,,,,,,,,,1,2,0,,,,0,0,0,0,,,,,,,,,,,0,0,0,,,0,0,0,0,,,,,,,,,,,,,,,,,,,,,tcp,,0,0,0,,0,0,0,,,,,,,,,,,0,,,,,,,,,-,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0, 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 (Moderate: haproxy security and bug fix update), 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/RHSA-2023:6496 |