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:
=======================
OpenStack Octavia (network load balancing as a service) intends to make use of HAProxy 1.6+ external-check to fix an important functionality bug mentioned here: https://storyboard.openstack.org/#!/story/2001280
The fix itself: https://review.openstack.org/#/c/518632

P.S.
Will this eventually bump the version of haproxy in the CentOS guest image?

Hi Nir,
  If all you request is just to bump haproxy version to 1.6+ so CentOS cloud-image would get the updated haproxy package, we can change the component to haproxy because there is nothing rhel-guest-image could do.
  But if you also want to add haproxy to rhel-guest-image(currently rhel-guest-image don't have it), please open a new bug and move this bug to haproxy.

Hi Wei Shi,

Thank you for your response.
Indeed what I seek is to bump the version of haproxy itself, and not to add it to the rhel-guest-image. Thus changed the component to haproxy.

Thanks,
Nir

This can't happen in RHEL. There are backward compatibility issues that could cause existing haproxy-1.5 users experience problems if we rebased to a major release of haproxy.