OCPBUGS-78541: Move TestIngressControllerCustomEndpoints to run last

[alebedev87]

Modifying Infrastructure.spec.platformSpec.aws.serviceEndpoints triggers MachineConfig re-rendering, causing a full cluster node rollout. Running this test last avoids disrupting other tests.

[openshift-ci]

Skipping CI for Draft Pull Request.
If you want CI signal for your change, please convert it to an actual PR.
You can still manually trigger a test run with /test all

[openshift-ci-robot]

@alebedev87: This pull request references Jira Issue OCPBUGS-78541, which is invalid:

• expected the bug to target either version "4.22." or "openshift-4.22.", but it targets "4.20" instead

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

The bug has been updated to refer to the pull request using the external bug tracker.

Details

In response to this:

This PR aims at reducing the flakiness of e2e-aws-operator test related to failed LB provisioning. It's likely to be caused by side effects of TestIngressControllerCustomEndpoints.

• Skip TestIngressControllerCustomEndpoints on external control plane topology

On HyperShift/ROSA clusters the Cloud Controller Manager runs on the
hosting cluster, so the guest cluster cannot track its rollout after an
Infrastructure config change. Running the test anyway risks LB provision
errors in subsequent tests caused by CCM leader re-election during a
machine config update.

• Move TestIngressControllerCustomEndpoints to run last

Modifying Infrastructure.spec.platformSpec.aws.serviceEndpoints
triggers MachineConfig re-rendering, causing a full cluster node
rollout. Running this test last avoids disrupting other tests.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Repository YAML (base), Organization UI (inherited)

Review profile: CHILL

Plan: Pro

Run ID: 0eaf8bca-8a75-454f-b98e-902dfa5848a6

📥 Commits

Reviewing files that changed from the base of the PR and between a5290f4 and 7e92761.

📒 Files selected for processing (1)

• test/e2e/all_test.go

🚧 Files skipped from review as they are similar to previous changes (1)

• test/e2e/all_test.go

---

📝 Walkthrough

Walkthrough

The change reorganizes test execution in the e2e test suite by relocating TestIngressControllerCustomEndpoints from parallel test execution to serial test execution. Explanatory comments are added noting that this test must run last because it modifies Infrastructure.spec.aws.serviceEndpoints, which triggers a cluster-wide rollout. No exported or public declarations were modified in the change.

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment

📝 Coding Plan

• Generate coding plan for human review comments

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[alebedev87]

/jira refresh

[openshift-ci-robot]

@alebedev87: This pull request references Jira Issue OCPBUGS-78541, which is valid. The bug has been moved to the POST state.

3 validation(s) were run on this bug

• bug is open, matching expected state (open)
• bug target version (4.22.0) matches configured target version for branch (4.22.0)
• bug is in the state New, which is one of the valid states (NEW, ASSIGNED, POST)

No GitHub users were found matching the public email listed for the QA contact in Jira (iamin@redhat.com), skipping review request.

Details

In response to this:

/jira refresh

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

[openshift-ci-robot]

@alebedev87: This pull request references Jira Issue OCPBUGS-78541, which is valid.

3 validation(s) were run on this bug

• bug is open, matching expected state (open)
• bug target version (4.22.0) matches configured target version for branch (4.22.0)
• bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, POST)

No GitHub users were found matching the public email listed for the QA contact in Jira (iamin@redhat.com), skipping review request.

The bug has been updated to refer to the pull request using the external bug tracker.

Details

In response to this:

Modifying Infrastructure.spec.platformSpec.aws.serviceEndpoints triggers MachineConfig re-rendering, causing a full cluster node rollout. Running this test last avoids disrupting other tests.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

[alebedev87]

e2e-aws-operator test passed second time in a row, trying again to get more data

/test e2e-aws-operator

[alebedev87]

/test e2e-hypershift

[rikatz]

/retest-required

[rikatz]

/lgtm
/approve
the failing tests are being caused by something else.

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: rikatz

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details

Needs approval from an approver in each of these files:

• OWNERS [rikatz]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[openshift-ci]

@alebedev87: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name	Commit	Details	Required	Rerun command
ci/prow/e2e-aws-ovn-hypershift-conformance	7e92761	link	true	/test e2e-aws-ovn-hypershift-conformance

Full PR test history. Your PR dashboard.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.