RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 2212246 - haproxy stats still showing status as OPEN after disabling frontend
Summary: haproxy stats still showing status as OPEN after disabling frontend
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 9
Classification: Red Hat
Component: haproxy
Version: CentOS Stream
Hardware: Unspecified
OS: Linux
unspecified
high
Target Milestone: rc
: ---
Assignee: Ryan O'Hara
QA Contact: Juraj Hrdlica
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2023-06-05 02:51 UTC by Nghia Le
Modified: 2023-11-07 10:00 UTC (History)
3 users (show)

Fixed In Version: haproxy-2.4.22-1.el9
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2023-11-07 08:35:32 UTC
Type: Bug
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker CLUSTERQE-6790 0 None None None 2023-06-27 15:16:05 UTC
Red Hat Issue Tracker RHELPLAN-158942 0 None None None 2023-06-05 02:54:15 UTC
Red Hat Product Errata RHSA-2023:6496 0 None None None 2023-11-07 08:35:37 UTC

Description Nghia Le 2023-06-05 02:51:05 UTC 
Description of problem:

haproxy.17 - it still showing status as OPEN after disabling frontend


Version-Release number of selected component (if applicable): 2.4.17



How reproducible: it is reproducible in CentOS Stream 8, 9 with haproxy.17


Steps to Reproduce:

1. disable frontend
[root@haproxy:~] echo "disable frontend main-ssl" | sudo socat stdio /var/lib/haproxy/stats2

2. checking status
[root@haproxy:~] echo 'show stat -1 1 -1' | sudo socat stdio /var/lib/haproxy/stats2 | grep main-ssl,FRONTEND

Actual results:
main-ssl,FRONTEND,,,2,4,3000,15,249689726,395411913,0,0,0,,,,,OPEN,,,,,,,,,2,2,0,,,,0,0,0,1,,,,,,,,,,,0,0,0,,,0,0,0,0,,,,,,,,,,,,,,,,,,,,,tcp,,0,1,96,,0,0,0,,,,,,,,,,,0,,,,,,,-,2,13,81,0,0,0,0,0,0,0,0,0,0,0,0,0,


Expected results:
main-ssl,FRONTEND,,,2,4,3000,15,249689726,395411913,0,0,0,,,,,STOP,,,,,,,,,2,2,0,,,,0,0,0,1,,,,,,,,,,,0,0,0,,,0,0,0,0,,,,,,,,,,,,,,,,,,,,,tcp,,0,1,96,,0,0,0,,,,,,,,,,,0,,,,,,,-,2,13,81,0,0,0,0,0,0,0,0,0,0,0,0,0,


Additional info: This bug is reported in the github project of the component https://github.com/haproxy/haproxy/issues/1626, it's already fixed in newer version 2.4, 2.5, 2.6 and later. But it has not been rebuild rpm package to CentOS Stream 9 repository
Comment 1 Ryan O'Hara 2023-06-07 15:42:32 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.
Comment 2 Nghia Le 2023-06-12 08:02:08 UTC 
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.
Comment 4 Nghia Le 2023-07-04 04:13:56 UTC 
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
Comment 7 Juraj Hrdlica 2023-07-11 08:15:18 UTC 
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,
Comment 9 errata-xmlrpc 2023-11-07 08:35:32 UTC 
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
Note You need to log in before you can comment on or make changes to this bug.