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:
OpenShift Container Platform intends to make use of HAProxy 1.6+ dns resolution at runtime and as such we're requesting a rebase to the latest version of haproxy.

Please see https://github.com/openshift/origin/pull/15409 for more discussion on the feature that OpenShift intends to leverage.

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

How reproducible:
n/a

We cannot simply rebase haproxy in RHEL7 to haprocy-1.7 due to backwards compatibility issues. For example, a valid haproxy.cfg configuration file for haproxy-1.5 may not be compatible with haproxy-1.7, so this is a non-starter.

Development Management has reviewed and declined this request. You may appeal this decision by reopening this request.