Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1647998

Summary: [RFE] Support new HAProxy 1.8 from RHEL8, in Director
Product: Red Hat OpenStack Reporter: Chris Jones <chjones>
Component: openstack-tripleo-heat-templatesAssignee: Michele Baldessari <michele>
Status: CLOSED ERRATA QA Contact: Marian Krcmarik <mkrcmari>
Severity: high Docs Contact:
Priority: high    
Version: 15.0 (Stein)CC: aherr, bperkins, cfernand, chjones, mburns, michele, oblaut, sclewis
Target Milestone: Upstream M2Keywords: FutureFeature, Triaged
Target Release: 15.0 (Stein)   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: openstack-tripleo-heat-templates-10.5.1-0.20190701110422.889d4d4.el8ost Doc Type: No Doc Update
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-09-21 11:19:23 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 Chris Jones 2018-11-08 17:13:53 UTC
RHEL8 brings HAProxy 1.8 which contains some incompatible changes from the RHEL7 version.

Comment 4 Cesar Fernandez 2019-07-11 08:39:04 UTC
Verified:

 - Undercloud:

[stack@undercloud-0 ~]$ rhos-release -L
Installed repositories (rhel-8.0):
  15
  ceph-4
  ceph-osd-4
  rhel-8.0

[stack@undercloud-0 ~]$ rpm -qa | grep openstack-tripleo-heat-templates-10.5.1-0.20190701110422.889d4d4.el8ost
openstack-tripleo-heat-templates-10.5.1-0.20190701110422.889d4d4.el8ost.noarch

- Overcloud:

()[root@controller-0 /]# haproxy -v
HA-Proxy version 1.8.15 2018/12/13
Copyright 2000-2018 Willy Tarreau <willy>

()[root@controller-1 /]# haproxy -v
HA-Proxy version 1.8.15 2018/12/13
Copyright 2000-2018 Willy Tarreau <willy>

()[root@controller-2 /]# haproxy -v
HA-Proxy version 1.8.15 2018/12/13
Copyright 2000-2018 Willy Tarreau <willy>

Comment 8 errata-xmlrpc 2019-09-21 11:19:23 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, 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/RHEA-2019:2811