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.

Description of problem:
HAProxy will fail to reload if the local peer name is prefixed by "-x".

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

How reproducible:

Always

Steps to Reproduce:
1. Modify you systemd unit file to include a "-L set local peer name" setting that includes "-x" as the prefix of the peer name. Example: "ExecStart=/usr/sbin/haproxy -Ws -f $CONFIG -p $PIDFILE -L -xfoo"
2. sudo systemctl daemon-reload
3. sudo systemctl start haproxy
4. sudo systemctl reload haproxy


Actual results:
The HAProxy usage statement will be output and the reload will fail.

Expected results:
HAProxy should complete the reload without error as it does with other local peer name prefixes.

Additional info:
This has been filed as an upstream bug in HAProxy and the link to that bug is included in this BZ.

(In reply to Michael Johnson from comment #0)
> Description of problem:
> HAProxy will fail to reload if the local peer name is prefixed by "-x".

[snip]

> Expected results:
> HAProxy should complete the reload without error as it does with other local
> peer name prefixes.

If upstream agrees this is a bug and agrees to fix it, fine. I'm not sure they will. Using "-" as the first character in a peer name seems insane to me. Just asking for trouble. Anyway, point here is that I will follow upstream on this.

Are there any updates on the RHEL side?
Bug fix committed upstream on June 5.

(In reply to Carlos Goncalves from comment #2)
> Are there any updates on the RHEL side?
> Bug fix committed upstream on June 5.

This will be in the next RHEL release (8.4).

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 (haproxy bug fix and enhancement 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/RHBA-2021:1926