User Story:
As an OpenShift Engineer I want [platform-external] investigate permanent failures in CI jobs caused by 'HA Proxy' tests on AWS provider so So we can get confidence in PExt deployments for partners.

As an OpenShift Engineer, I want to investigate permanent failures in our continuous integration (CI) jobs caused by HAProxy tests on the AWS provider so that we can gain confidence in partner external (PExt) deployments.

Description:
We've noticed recurring failures in our CI jobs that involve HAProxy testing on the AWS platform. These failures are causing delays and impacting our ability to deliver reliable PExt deployments to our partners. By investigating and resolving these issues, we aim to improve the stability of our CI/CD pipeline and boost confidence in our PExt deployment process.

Acceptance Criteria:
1. The investigation team has identified the root cause(s) of the permanent failures in the CI jobs.
2. A detailed report is created, outlining the findings and recommended solutions.
4. The impact of each solution/workaround on the CI/CD pipeline, performance, and resource usage is analyzed and documented.
5. A decision is made regarding the most suitable solution based on its feasibility, impact, and long-term benefits.
6. The selected solution or workaround has been successfully implemented and tested in our CI/CD environment without causing any new failures or degrading performance.
7. The team has verified that the permanent failures have been resolved, and HAProxy tests are now passing, or skipping, consistently on the AWS provider.
8. Documentation is updated to reflect the changes made and any new procedures or best practices related to HAProxy testing on AWS.
9. All stakeholders, including the development team, QA, DevOps, and partners, are informed about the investigation findings, implemented solution, and its expected benefits.

Other Information:

• Root cause(s) identified and documented
• Recommended solutions/workarounds proposed and analyzed
• Selected solution successfully implemented and tested
• Permanent failures resolved with consistent passing HAProxy tests on AWS
• Documentation updated
• Stakeholders informed