Bug 1483579 - Create an haproxy-1.8 package
Summary: Create an haproxy-1.8 package
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Release
Version: 3.7.0
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
: 3.8.0
Assignee: Frantisek Kluknavsky
QA Contact: Johnny Liu
URL:
Whiteboard:
Depends On: 1482936
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-08-21 12:35 UTC by Scott Dodson
Modified: 2018-03-28 14:06 UTC (History)
13 users (show)

Fixed In Version:
Doc Type: Rebase: Bug Fixes and Enhancements
Doc Text:
Clone Of: 1482936
Environment:
Last Closed: 2018-03-28 14:06:20 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 1506866 0 high CLOSED [3.9] haproxy lb install failed when haproxy-1.7.9-1.el7.x86_64 is installed. 2021-02-22 00:41:40 UTC
Red Hat Product Errata RHBA-2018:0489 0 None None None 2018-03-28 14:06:48 UTC

Internal Links: 1506866

Comment 13 Scott Dodson 2018-01-12 15:57:05 UTC 
haproxy18 wasn't tagged into 3.9 until January 4th and the latest 3.9 puddle is from the 3rd, lets hope that the next puddle has the required package.

https://brewweb.engineering.redhat.com/brew/taskinfo?taskID=14875572

with this subsequent build

https://brewweb.engineering.redhat.com/brew/taskinfo?taskID=14915918

We'll need to make sure that we either switch to building them into the 3.9 target or continue tagging them in. I imagine we should switch to just building them in 3.9
Comment 14 Johnny Liu 2018-01-15 03:41:49 UTC 
Verified this bug with AtomicOpenShift-3.9-20180113.1, and PASS.

haproxy18-1.8.1-5.el7 rpm package is shown in AtomicOpenShift-3.9-20180113.1 puddle.
Comment 17 errata-xmlrpc 2018-03-28 14:06:20 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/RHBA-2018:0489
Note You need to log in before you can comment on or make changes to this bug.