Bug 1838319

Summary:	HAProxy fails to reload when local peer name starts with "-x"
Product:	Red Hat Enterprise Linux 8	Reporter:	Michael Johnson <michjohn>
Component:	haproxy	Assignee:	Ryan O'Hara <rohara>
Status:	CLOSED ERRATA	QA Contact:	Brandon Perkins <bperkins>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	8.0	CC:	cgoncalves, rohara
Target Milestone:	rc	Keywords:	Triaged
Target Release:	8.0	Flags:	pm-rhel: mirror+
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:	haproxy-1.8.27-2.el8	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2021-05-18 16:10:29 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:
Bug Depends On:	1905663
Bug Blocks:

Description Michael Johnson 2020-05-20 21:27:33 UTC

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.

Comment 1 Ryan O'Hara 2020-05-20 21:33:51 UTC

(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.

Comment 2 Carlos Goncalves 2020-08-10 10:49:46 UTC

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

Comment 4 Ryan O'Hara 2020-11-09 20:13:21 UTC

(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).

Comment 16 errata-xmlrpc 2021-05-18 16:10:29 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 (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