OCPBUGS-111965: Remove unnecessary reqserving management cluster override

[PoornimaSingour]

Description:

Summary

Remove unnecessary OPENSHIFT_INSTALL_RELEASE_IMAGE_OVERRIDE from the reqserving-e2e-aws job across all branches (main, 4.21-5.2).

Problem

The override was pinning management clusters to outdated versions (4.20/4.21) without technical justification:

• Main branch pinned to 4.21 despite targeting 5.1
• Release branches pinned to wrong versions
• Added in PR CNTRLPLANE-1644: test(hypershift): add request-serving e2e test workflow #70989 without documented reason
• Propagated through config-brancher to all release branches
• No other AWS e2e jobs use this pattern (except kubevirt with documented ODF dependency)

Root Cause Analysis

Traced through git history:

1. Nov 2025: Added with release:latest-420 in CNTRLPLANE-1644: test(hypershift): add request-serving e2e test workflow #70989 (no justification)
2. Dec 2025: Mechanically bumped to 421 during version sync (hypershift: sync 4.22 presubs #72614)
3. 2026: config-brancher copied to all release branches (4.21-5.2)
4. Never validated or questioned

Solution

Remove the override to allow management clusters to use appropriate default versions:

• Main → uses default (5.1)
• Release branches → use their respective versions (4.21, 4.22, 4.23, 5.0, 5.1, 5.2)

Guest clusters are unaffected - they continue using release:latest.

Testing

• ✅ Local: make update passed
• ✅ Validation: ci-operator-checkconfig passed
• ✅ Job generation: ci-operator-prowgen completed
• ⏳ Rehearsal: Will validate after PR creation

Summary by CodeRabbit

• Removed OPENSHIFT_INSTALL_RELEASE_IMAGE_OVERRIDE from the reqserving-e2e-aws CI job for main and release branches 4.21–5.2.
• Management clusters now use each branch’s default release image instead of outdated pinned images.
• Guest clusters continue to use release:latest.
• Configuration validation and job generation completed successfully.

[openshift-ci-robot]

@PoornimaSingour: This pull request references Jira Issue OCPBUGS-111965, 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 (5.1.0) matches configured target version for branch (5.1.0)
• bug is in the state ASSIGNED, which is one of the valid states (NEW, ASSIGNED, POST)

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

Details

In response to this:

Description:

Summary

Remove unnecessary OPENSHIFT_INSTALL_RELEASE_IMAGE_OVERRIDE from the reqserving-e2e-aws job across all branches (main, 4.21-5.2).

Problem

The override was pinning management clusters to outdated versions (4.20/4.21) without technical justification:

• Main branch pinned to 4.21 despite targeting 5.1
• Release branches pinned to wrong versions
• Added in PR CNTRLPLANE-1644: test(hypershift): add request-serving e2e test workflow #70989 without documented reason
• Propagated through config-brancher to all release branches
• No other AWS e2e jobs use this pattern (except kubevirt with documented ODF dependency)

Root Cause Analysis

Traced through git history:

1. Nov 2025: Added with release:latest-420 in CNTRLPLANE-1644: test(hypershift): add request-serving e2e test workflow #70989 (no justification)
2. Dec 2025: Mechanically bumped to 421 during version sync (hypershift: sync 4.22 presubs #72614)
3. 2026: config-brancher copied to all release branches (4.21-5.2)
4. Never validated or questioned

Solution

Remove the override to allow management clusters to use appropriate default versions:

• Main → uses default (5.1)
• Release branches → use their respective versions (4.21, 4.22, 4.23, 5.0, 5.1, 5.2)

Guest clusters are unaffected - they continue using release:latest.

Testing

• ✅ Local: make update passed
• ✅ Validation: ci-operator-checkconfig passed
• ✅ Job generation: ci-operator-prowgen completed
• ⏳ Rehearsal: Will validate after PR creation

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), Central YAML (inherited)

Review profile: CHILL

Plan: Team

Run ID: 17094fca-379d-4cc0-bfe4-44d1570dd299

📥 Commits

Reviewing files that changed from the base of the PR and between 2a61d0d and 70c0a12.

📒 Files selected for processing (7)

• ci-operator/config/openshift/hypershift/openshift-hypershift-main.yaml
• ci-operator/config/openshift/hypershift/openshift-hypershift-release-4.21.yaml
• ci-operator/config/openshift/hypershift/openshift-hypershift-release-4.22.yaml
• ci-operator/config/openshift/hypershift/openshift-hypershift-release-5.0.yaml
• ci-operator/config/openshift/hypershift/openshift-hypershift-release-5.0__4-23.yaml
• ci-operator/config/openshift/hypershift/openshift-hypershift-release-5.1.yaml
• ci-operator/config/openshift/hypershift/openshift-hypershift-release-5.2.yaml

💤 Files with no reviewable changes (7)

• ci-operator/config/openshift/hypershift/openshift-hypershift-release-5.2.yaml
• ci-operator/config/openshift/hypershift/openshift-hypershift-release-4.22.yaml
• ci-operator/config/openshift/hypershift/openshift-hypershift-release-5.0.yaml
• ci-operator/config/openshift/hypershift/openshift-hypershift-release-5.0__4-23.yaml
• ci-operator/config/openshift/hypershift/openshift-hypershift-main.yaml
• ci-operator/config/openshift/hypershift/openshift-hypershift-release-5.1.yaml
• ci-operator/config/openshift/hypershift/openshift-hypershift-release-4.21.yaml

Included review availability: Your plan provides up to 2 included reviews per hour; 1 remains after this review.

---

Walkthrough

The reqserving-e2e-aws test removes explicit OPENSHIFT_INSTALL_RELEASE_IMAGE_OVERRIDE dependencies from seven Hypershift CI configurations. The test now uses each workflow’s default install release image.

Changes

Reqserving release selection

Layer / File(s)	Summary
Use default install release images ci-operator/config/openshift/hypershift/openshift-hypershift-main.yaml, ci-operator/config/openshift/hypershift/openshift-hypershift-release-4.21.yaml, ci-operator/config/openshift/hypershift/openshift-hypershift-release-4.22.yaml, ci-operator/config/openshift/hypershift/openshift-hypershift-release-5.*.yaml	The reqserving-e2e-aws jobs no longer define explicit release image dependencies. The jobs use their default install release images.

Estimated code review effort: 1 (Trivial) | ~2 minutes

Merge Risk: ⚪ Minimal · up to 70c0a

This localized configuration change removes outdated management-cluster version pinning while leaving guest-cluster behavior unchanged; no actionable merge-blocking risk remains beyond normal checks and review.

🚥 Pre-merge checks | ✅ 15

✅ Passed checks (15 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title clearly describes the main change: removing the unnecessary management cluster override from the reqserving job. It is specific and concise.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 0…
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Stable And Deterministic Test Names	✅ Passed	PASS. The PR delta is limited to 14 deletions in seven CI YAML files. It removes OPENSHIFT_INSTALL_RELEASE_IMAGE_OVERRIDE entries from the static reqserving-e2e-aws job definitions. No Ginkgo titl…
Test Structure And Quality	✅ Passed	PASS: The pull request changes only seven YAML CI configuration files. The exact diff removes two dependency lines from the reqserving-e2e-aws entries and adds no Ginkgo or test implementation code.…
Microshift Test Compatibility	✅ Passed	The check is not applicable. The pull-request commit changes only seven HyperShift CI YAML files and removes two dependency lines from the existing reqserving-e2e-aws jobs. It adds no Ginkgo tests o…
Single Node Openshift (Sno) Test Compatibility	✅ Passed	PASS. The PR adds no Ginkgo e2e tests. The PR-side diff contains only seven YAML files, with 14 deletions and no additions. The changes remove dependencies from existing CI job definitions; they do no…
Topology-Aware Scheduling Compatibility	✅ Passed	PASS — The pull request changes only seven ci-operator/config/openshift/hypershift/*.yaml CI job definitions. The exact diff removes OPENSHIFT_INSTALL_RELEASE_IMAGE_OVERRIDE from the `reqserving-e…
Ote Binary Stdout Contract	✅ Passed	PASS: The PR changes only seven Hypershift YAML configuration files. The diff removes OPENSHIFT_INSTALL_RELEASE_IMAGE_OVERRIDE from reqserving-e2e-aws; it changes no Go source, test binary, suite …
Ipv6 And Disconnected Network Test Compatibility	✅ Passed	PASS — The PR changes only seven CI YAML files. The exact PR diff removes OPENSHIFT_INSTALL_RELEASE_IMAGE_OVERRIDE from the existing reqserving-e2e-aws job and adds no Ginkgo tests or test code. T…
No-Weak-Crypto	✅ Passed	PASS: The pull-request diff changes only seven CI YAML files. It contains 14 deletions and no additions. The deletions remove release-image override settings from reqserving-e2e-aws; they add no MD5…
Container-Privileges	✅ Passed	PASS. The contributor patch contains only 14 deleted lines across seven Hypershift CI YAML files. It removes OPENSHIFT_INSTALL_RELEASE_IMAGE_OVERRIDE from reqserving-e2e-aws and adds no lines. The…
No-Sensitive-Data-In-Logs	✅ Passed	PASS — The PR-local commit changes only six CI YAML files and removes 12 lines containing the release-image override. The affected jobs retain only existing cluster and workflow configuration. No logg…

Full details: Docstring Coverage

Explanation

No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 0 files.

Full details: Stable And Deterministic Test Names

Explanation

PASS. The PR delta is limited to 14 deletions in seven CI YAML files. It removes OPENSHIFT_INSTALL_RELEASE_IMAGE_OVERRIDE entries from the static reqserving-e2e-aws job definitions. No Ginkgo title declarations (It, Describe, Context, or When) were added or changed, and no dynamic test-name value was introduced.

Full details: Test Structure And Quality

Explanation

PASS: The pull request changes only seven YAML CI configuration files. The exact diff removes two dependency lines from the reqserving-e2e-aws entries and adds no Ginkgo or test implementation code. Therefore, the single-responsibility, setup/cleanup, timeout, assertion-message, and test-pattern requirements are not applicable to this change.

Full details: Microshift Test Compatibility

Explanation

The check is not applicable. The pull-request commit changes only seven HyperShift CI YAML files and removes two dependency lines from the existing reqserving-e2e-aws jobs. It adds no Ginkgo tests or test bodies, so it introduces no MicroShift-incompatible API or feature usage.

Full details: Single Node Openshift (Sno) Test Compatibility

Explanation

PASS. The PR adds no Ginkgo e2e tests. The PR-side diff contains only seven YAML files, with 14 deletions and no additions. The changes remove dependencies from existing CI job definitions; they do not add or modify It(), Describe(), Context(), or When() test bodies. Therefore, the SNO compatibility check is not applicable.

Full details: Topology-Aware Scheduling Compatibility

Explanation

PASS — The pull request changes only seven ci-operator/config/openshift/hypershift/*.yaml CI job definitions. The exact diff removes OPENSHIFT_INSTALL_RELEASE_IMAGE_OVERRIDE from the reqserving-e2e-aws steps and does not add or modify deployment manifests, operator code, controllers, replicas, affinity, topology spread, node selectors, tolerations, or PDBs. The topology-aware scheduling check is therefore not applicable.

Full details: Ote Binary Stdout Contract

Explanation

PASS: The PR changes only seven Hypershift YAML configuration files. The diff removes OPENSHIFT_INSTALL_RELEASE_IMAGE_OVERRIDE from reqserving-e2e-aws; it changes no Go source, test binary, suite setup, or logging configuration. The referenced workflow runs the existing hypershift-tests step and hack/run-reqserving-e2e.sh. No changed file contains an OTE process-level stdout write, so the custom check's failure condition is not introduced.

Full details: Ipv6 And Disconnected Network Test Compatibility

Explanation

PASS — The PR changes only seven CI YAML files. The exact PR diff removes OPENSHIFT_INSTALL_RELEASE_IMAGE_OVERRIDE from the existing reqserving-e2e-aws job and adds no Ginkgo tests or test code. Therefore, it introduces no IPv4 assumption or external connectivity requirement covered by this check.

Full details: No-Weak-Crypto

Explanation

PASS: The pull-request diff changes only seven CI YAML files. It contains 14 deletions and no additions. The deletions remove release-image override settings from reqserving-e2e-aws; they add no MD5, SHA1, DES, RC4, 3DES, Blowfish, ECB, custom crypto, or secret-comparison logic.

Full details: Container-Privileges

Explanation

PASS. The contributor patch contains only 14 deleted lines across seven Hypershift CI YAML files. It removes OPENSHIFT_INSTALL_RELEASE_IMAGE_OVERRIDE from reqserving-e2e-aws and adds no lines. The changed-line scan found no privileged, hostPID, hostNetwork, hostIPC, SYS_ADMIN, allowPrivilegeEscalation, or root-setting declarations. The affected job blocks retain only CI capabilities scheduling entries and the unchanged workflow reference. No explicit container privilege condition is introduced.

Full details: No-Sensitive-Data-In-Logs

Explanation

PASS — The PR-local commit changes only six CI YAML files and removes 12 lines containing the release-image override. The affected jobs retain only existing cluster and workflow configuration. No logging calls, log commands, secrets, tokens, credentials, PII, hostnames, or customer data are added by the change.

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

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

[openshift-ci-robot]

@PoornimaSingour: This pull request references Jira Issue OCPBUGS-111965, which is valid.

3 validation(s) were run on this bug

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

Details

In response to this:

Description:

Summary

Remove unnecessary OPENSHIFT_INSTALL_RELEASE_IMAGE_OVERRIDE from the reqserving-e2e-aws job across all branches (main, 4.21-5.2).

Problem

The override was pinning management clusters to outdated versions (4.20/4.21) without technical justification:

• Main branch pinned to 4.21 despite targeting 5.1
• Release branches pinned to wrong versions
• Added in PR CNTRLPLANE-1644: test(hypershift): add request-serving e2e test workflow #70989 without documented reason
• Propagated through config-brancher to all release branches
• No other AWS e2e jobs use this pattern (except kubevirt with documented ODF dependency)

Root Cause Analysis

Traced through git history:

1. Nov 2025: Added with release:latest-420 in CNTRLPLANE-1644: test(hypershift): add request-serving e2e test workflow #70989 (no justification)
2. Dec 2025: Mechanically bumped to 421 during version sync (hypershift: sync 4.22 presubs #72614)
3. 2026: config-brancher copied to all release branches (4.21-5.2)
4. Never validated or questioned

Solution

Remove the override to allow management clusters to use appropriate default versions:

• Main → uses default (5.1)
• Release branches → use their respective versions (4.21, 4.22, 4.23, 5.0, 5.1, 5.2)

Guest clusters are unaffected - they continue using release:latest.

Testing

• ✅ Local: make update passed
• ✅ Validation: ci-operator-checkconfig passed
• ✅ Job generation: ci-operator-prowgen completed
• ⏳ Rehearsal: Will validate after PR creation

Summary by CodeRabbit

• Removed the outdated OPENSHIFT_INSTALL_RELEASE_IMAGE_OVERRIDE from the reqserving-e2e-aws job on main and release branches 4.21–5.2.
• Management clusters now use branch defaults. Guest clusters continue to use release:latest.
• Local updates, configuration validation, and job generation passed. Rehearsal validation remains pending.
• Related Jira issue: OCPBUGS-111965.

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.

[vismishr]

/approve

[PoornimaSingour]

/pj-rehearse pull-ci-openshift-hypershift-release-5.1-reqserving-e2e-aws pull-ci-openshift-hypershift-release-5.2-reqserving-e2e-aws pull-ci-openshift-hypershift-release-4.23-reqserving-e2e-aws pull-ci-openshift-hypershift-release-4.22-reqserving-e2e-aws

[openshift-merge-bot]

@PoornimaSingour: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel.

[vismishr]

/lgtm

[PoornimaSingour]

/pj-rehearse pull-ci-openshift-hypershift-main-reqserving-e2e-aws

[openshift-merge-bot]

@PoornimaSingour: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel.

[PoornimaSingour]

/retest

[PoornimaSingour]

/pj-rehearse pull-ci-openshift-hypershift-main-reqserving-e2e-aws

[openshift-merge-bot]

@PoornimaSingour: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel.

[PoornimaSingour]

Previously, OPENSHIFT_INSTALL_RELEASE_IMAGE_OVERRIDE was hardcoding the management cluster to an older version across all branches:

Branch             Was pinned to
main                 release:latest-421  (4.21)
release-4.21    release:latest-420  (4.20)
release-4.22    release:latest-421  (4.21)
release-4.23    release:latest-421  (4.21)
release-5.0     release:latest-421  (4.21)
release-5.1     release:latest-421  (4.21)
release-5.2     release:latest-421  (4.21)

So branches like main (which is 5.1) and release-5.0 were testing with a 4.21 management cluster — two major versions behind.

**After fix: 📊 Rehearsal Failure Analysis: **

1. ✅ Management cluster provisions successfully (IPI install passed)
2. ✅ Guest clusters create successfully (all create tests passed)
3. ✅ Request serving isolation works (all validation tests passed)
4. ✅ Teardown completes (clusters destroyed successfully)
5. ❌ Only failures: Post-test cleanup/validation issues

Every job successfully:

1. ✅ Provisioned management cluster via IPI (with default version - your change)
   Key Proof Points

✅ Main Branch: Management cluster using 5.1.0 (not 4.21)
Release payload version: 5.1.0-0.ci-2026-08-31-182936

✅ Release-4.22: Management cluster using 4.22.0 (not 4.21)
Release payload version: 4.22.0-0.ci-2026-08-31-121223

✅ Release-4.23: Management cluster using 4.23.0 (not 4.21)
Release payload version: 4.23.0-0.ci-2026-08-31-121930

3. ✅ Created guest hosted clusters
4. ✅ Ran request serving isolation tests
5. ✅ Validated hosted cluster
6. ✅ Cleaned up clusters (destroyed successfully)

Failures are ONLY in:

• Post-cleanup AWS resource verification (VPC endpoints not immediately deleted)
• Post-teardown metrics validation (trying to access deleted containers)

[PoornimaSingour]

/rebase

[coderabbitai]

Note

GitHub couldn't provide a complete incremental comparison for this pull request, so CodeRabbit is performing a full review instead. This review may take a little longer.

[openshift-merge-bot]

[REHEARSALNOTIFIER]
@PoornimaSingour: the pj-rehearse plugin accommodates running rehearsal tests for the changes in this PR. Expand 'Interacting with pj-rehearse' for usage details. The following rehearsable tests have been affected by this change:

Test name	Repo	Type	Reason
pull-ci-openshift-hypershift-release-4.22-reqserving-e2e-aws	openshift/hypershift	presubmit	Ci-operator config changed
pull-ci-openshift-hypershift-main-reqserving-e2e-aws	openshift/hypershift	presubmit	Ci-operator config changed
pull-ci-openshift-hypershift-release-5.2-reqserving-e2e-aws	openshift/hypershift	presubmit	Ci-operator config changed
pull-ci-openshift-hypershift-release-5.0-4-23-reqserving-e2e-aws	openshift/hypershift	presubmit	Ci-operator config changed
pull-ci-openshift-hypershift-release-5.0-reqserving-e2e-aws	openshift/hypershift	presubmit	Ci-operator config changed
pull-ci-openshift-hypershift-release-4.21-reqserving-e2e-aws	openshift/hypershift	presubmit	Ci-operator config changed
pull-ci-openshift-hypershift-release-5.1-reqserving-e2e-aws	openshift/hypershift	presubmit	Ci-operator config changed

Interacting with pj-rehearse

Comment: /pj-rehearse to run up to 5 rehearsals
Comment: /pj-rehearse skip to opt-out of rehearsals
Comment: /pj-rehearse {test-name}, with each test separated by a space, to run one or more specific rehearsals
Comment: /pj-rehearse more to run up to 10 rehearsals
Comment: /pj-rehearse max to run up to 25 rehearsals
Comment: /pj-rehearse auto-ack to run up to 5 rehearsals, and add the rehearsals-ack label on success
Comment: /pj-rehearse list to get an up-to-date list of affected jobs
Comment: /pj-rehearse abort to abort all active rehearsals
Comment: /pj-rehearse network-access-allowed to allow rehearsals of tests that have the restrict_network_access field set to false. This must be executed by an openshift org member who is not the PR author

Once you are satisfied with the results of the rehearsals, comment: /pj-rehearse ack to unblock merge. When the rehearsals-ack label is present on your PR, merge will no longer be blocked by rehearsals.
If you would like the rehearsals-ack label removed, comment: /pj-rehearse reject to re-block merging.

[PoornimaSingour]

/pj-rehearse pull-ci-openshift-hypershift-main-reqserving-e2e-aws

[openshift-merge-bot]

@PoornimaSingour: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel.

[vismishr]

/lgtm

[openshift-ci]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: PoornimaSingour, vismishr
Once this PR has been reviewed and has the lgtm label, please assign enxebre for approval. For more information see the Code Review Process.

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

Details

Needs approval from an approver in each of these files:

• ci-operator/config/openshift/hypershift/OWNERS

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

[openshift-ci]

@PoornimaSingour: The following tests 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/rehearse/openshift/hypershift/release-5.2/reqserving-e2e-aws	4486b46	link	unknown	/pj-rehearse pull-ci-openshift-hypershift-release-5.2-reqserving-e2e-aws
ci/rehearse/openshift/hypershift/release-4.22/reqserving-e2e-aws	4486b46	link	unknown	/pj-rehearse pull-ci-openshift-hypershift-release-4.22-reqserving-e2e-aws
ci/rehearse/openshift/hypershift/release-5.1/reqserving-e2e-aws	4486b46	link	unknown	/pj-rehearse pull-ci-openshift-hypershift-release-5.1-reqserving-e2e-aws
ci/rehearse/openshift/hypershift/release-4.23/reqserving-e2e-aws	4486b46	link	unknown	/pj-rehearse pull-ci-openshift-hypershift-release-4.23-reqserving-e2e-aws
ci/rehearse/openshift/hypershift/main/reqserving-e2e-aws	70c0a12	link	unknown	/pj-rehearse pull-ci-openshift-hypershift-main-reqserving-e2e-aws

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.

[PoornimaSingour]

/pj-rehearse pull-ci-openshift-hypershift-release-5.1-reqserving-e2e-aws pull-ci-openshift-hypershift-release-4.23-reqserving-e2e-aws pull-ci-openshift-hypershift-release-4.22-reqserving-e2e-aws pull-ci-openshift-hypershift-main-reqserving-e2e-aws

[openshift-merge-bot]

@PoornimaSingour: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel.

[openshift-merge-bot]

@PoornimaSingour: job(s): pull-ci-openshift-hypershift-release-4.23-reqserving-e2e-aws, either don't exist or were not found to be affected, and cannot be rehearsed