Epic Goal

Update the rhaos-4.19-rhel-9 branch of the haproxy repository in dist-git to be up to date with the rhaos-4.18-rhel-9 branch.

Why is this important?

The rhaos-4.18-rhel-9 branch has HAProxy 2.8.10, but the rhaos-4.19-rhel-9 branch has HAProxy 2.8.5. We had a similar issue before with the rhaos-4.18-rhel-9 branch (see NE-1879). Long-term, we need to find out why dist-git is not automatically propagating updates from the older branch to the newer branch. In the meantime, we need to update the rhaos-4.19-rhel-9 branch manually.

Planning Done Checklist

The following items must be completed on the Epic prior to moving the Epic from Planning to ToDo status

• Priority is set by engineering
• Epic must be Linked to a Parent Feature
• Target version+ must be set
• Assignee+ must be set
• Enhancement Proposal is Implementable
• No outstanding questions about major work breakdown
• Are all Stakeholders known? Have they all been notified about this item?
• Does this epic affect SD? Have they been notified? (View plan definition for current suggested assignee)
  1. Please use the “Discussion Needed: Service Delivery Architecture Overview” checkbox to facilitate the conversation with SD Architects. The SD architecture team monitors this checkbox which should then spur the conversation between SD and epic stakeholders. Once the conversation has occurred, uncheck the “Discussion Needed: Service Delivery Architecture Overview” checkbox and record the outcome of the discussion in the epic description here.
  2. The guidance here is that unless it is very clear that your epic doesn’t have any managed services impact, default to use the Discussion Needed checkbox to facilitate that conversation.

Additional information on each of the above items can be found here: Networking Definition of Planned

Acceptance Criteria

• CI - MUST be running successfully with tests automated
• -Release Technical Enablement - Provide necessary release enablement
  details and documents.-

Dependencies (internal and external)

None.

Previous Work (Optional)

1. …

Open questions

1. Is this a one-off effort? In the past, automatic branch-propagation handled the dist-git update for us.

Done Checklist

• CI - CI is running, tests are automated and merged.
• Release Enablement <link to Feature Enablement Presentation>
• DEV - Upstream code and tests merged: <link to meaningful PR or GitHub Issue>
• DEV - Upstream documentation merged: <link to meaningful PR or GitHub Issue>
• DEV - Downstream build attached to advisory: <link to errata>
• QE - Test plans in Polarion: <link or reference to Polarion>
• QE - Automated tests merged: <link or reference to automated tests>
• DOC - Downstream documentation merged: <link to meaningful PR>