Skip to content

CNTRLPLANE-772: Add request serving test to HCM periodics#79884

Open
jiezhao16 wants to merge 2 commits into
openshift:mainfrom
jiezhao16:add-reqserving-hcm-periodics
Open

CNTRLPLANE-772: Add request serving test to HCM periodics#79884
jiezhao16 wants to merge 2 commits into
openshift:mainfrom
jiezhao16:add-reqserving-hcm-periodics

Conversation

@jiezhao16
Copy link
Copy Markdown
Contributor

@jiezhao16 jiezhao16 commented May 29, 2026

Summary

  • Enable REQUEST_SERVING_COMPONENT_TEST in the HCM periodic e2e-aws job for 4.21
  • This validates request-serving topology against real ROSA management clusters
  • The run script already supports this flag; this change only sets the env var

Related

Test plan

  • Rehearse with /pj-rehearse to verify the job runs successfully

Summary by CodeRabbit

This PR updates the OpenShift CI configuration in the openshift/release repository to enable request-serving validation in the Hypershift Control Plane Manager (HCM) periodic jobs for the 4.21 branch.

What changed

  • Adds a new periodic test entry in ci-operator/config/openshift/hypershift/openshift-hypershift-release-4.21__periodics-hcm.yaml:
    • as: e2e-aws-request-serving
    • cron: 0 4 * * *
    • workflow: hypershift-aws-e2e-metrics
    • env: REQUEST_SERVING_COMPONENT_TEST: "true"
  • The existing e2e-aws periodic job is left unchanged.

Why it matters

  • Enables the REQUEST_SERVING_COMPONENT_TEST flag for the 4.21 HCM periodics so the CI will validate request-serving topology against real ROSA management clusters using the existing hypershift e2e workflow that already supports this flag.

Other notes

  • Author rehearsed the job with: /pj-rehearse periodic-ci-openshift-hypershift-release-4.21-periodics-hcm-e2e-aws.
  • CI bot confirmed the PR references CNTRLPLANE-772 but reported the Jira issue lacks an expected target version (robot warning).

Enable REQUEST_SERVING_COMPONENT_TEST in the HCM periodic e2e-aws job
to validate request-serving topology against real ROSA management clusters.
The hypershift-aws-run-e2e-external-commands.sh script already supports
this flag — this change only sets the env var in the job config.

Related: openshift/hypershift#7031 (test implementation)
Related: openshift#70989 (self-managed CI workflow)
@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label May 29, 2026
@openshift-ci-robot
Copy link
Copy Markdown
Contributor

openshift-ci-robot commented May 29, 2026

@jiezhao16: This pull request references CNTRLPLANE-772 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the story to target the "5.0.0" version, but no target version was set.

Details

In response to this:

Summary

  • Enable REQUEST_SERVING_COMPONENT_TEST in the HCM periodic e2e-aws job for 4.21
  • This validates request-serving topology against real ROSA management clusters
  • The run script already supports this flag; this change only sets the env var

Related

Test plan

  • Rehearse with /pj-rehearse to verify the job runs successfully

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
Copy link
Copy Markdown
Contributor

coderabbitai Bot commented May 29, 2026

Walkthrough

Adds a new periodic job e2e-aws-request-serving (cron 0 4 * * *) to Hypershift 4.21 periodics, selecting workflow: hypershift-aws-e2e-metrics and setting REQUEST_SERVING_COMPONENT_TEST: "true" in the job's environment.

Changes

HyperShift Release 4.21 Periodic Tests

Layer / File(s) Summary
Add periodic job for request-serving metrics
ci-operator/config/openshift/hypershift/openshift-hypershift-release-4.21__periodics-hcm.yaml
Introduces e2e-aws-request-serving periodic test with cron: "0 4 * * *", cluster_profile: hypershift-aws, workflow: hypershift-aws-e2e-metrics, and env.REQUEST_SERVING_COMPONENT_TEST: "true".

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

Suggested labels

area/pipelines, rehearsals-ack

🚥 Pre-merge checks | ✅ 15
✅ Passed checks (15 passed)
Check name Status Explanation
Title check ✅ Passed The title accurately describes the main change: adding a request serving test to HCM periodics for the 4.21 release configuration.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
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 PR only modifies CI/CD config YAML, adding a periodic job entry. No Ginkgo test code files are modified or added, so the "Stable and Deterministic Test Names" check does not apply.
Test Structure And Quality ✅ Passed PR modifies only CI/CD YAML configuration file, not Ginkgo test code, so the test structure and quality check is not applicable.
Microshift Test Compatibility ✅ Passed This PR adds CI/CD periodic job configuration only, not new Ginkgo test code. The check applies specifically to new Ginkgo e2e tests (It, Describe, Context, When), which are not added here.
Single Node Openshift (Sno) Test Compatibility ✅ Passed PR adds only a CI configuration file (YAML) to schedule existing e2e tests. No new Ginkgo test code is added, so SNO compatibility check does not apply.
Topology-Aware Scheduling Compatibility ✅ Passed The PR modifies CI/CD periodic configuration, not deployment manifests, operator code, or controllers. No scheduling constraints are introduced to cluster deployments.
Ote Binary Stdout Contract ✅ Passed PR modifies only CI/CD YAML configuration (periodic job definitions), not test binaries or code. Custom check for OTE Binary Stdout Contract is inapplicable to non-code configuration files.
Ipv6 And Disconnected Network Test Compatibility ✅ Passed PR adds a periodic job configuration with an existing test; no new Ginkgo e2e tests (It(), Describe(), etc.) are introduced, so IPv6/disconnected check does not apply.
No-Weak-Crypto ✅ Passed PR contains only CI/CD configuration changes (YAML job definitions), not code with cryptographic operations. No weak crypto usage found.
Container-Privileges ✅ Passed PR modifies CI operator job configuration, not K8s container manifests. No privileged security settings detected.
No-Sensitive-Data-In-Logs ✅ Passed PR adds e2e-aws-request-serving job setting REQUEST_SERVING_COMPONENT_TEST="true", passing non-sensitive test parameters to existing e2e workflow. No logging of sensitive data introduced.
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

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

@openshift-ci openshift-ci Bot requested review from csrwng and jparrill May 29, 2026 21:56
@jiezhao16
Copy link
Copy Markdown
Contributor Author

/pj-rehearse periodic-ci-openshift-hypershift-release-4.21-periodics-hcm-e2e-aws

@openshift-merge-bot
Copy link
Copy Markdown
Contributor

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

@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci Bot commented May 30, 2026

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: jiezhao16
Once this PR has been reviewed and has the lgtm label, please assign csrwng 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:

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

@jiezhao16
Copy link
Copy Markdown
Contributor Author

/pj-rehearse periodic-ci-openshift-hypershift-release-4.21-periodics-hcm-e2e-aws-request-serving

@openshift-merge-bot
Copy link
Copy Markdown
Contributor

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

@openshift-merge-bot
Copy link
Copy Markdown
Contributor

[REHEARSALNOTIFIER]
@jiezhao16: 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
periodic-ci-openshift-hypershift-release-4.21-periodics-hcm-e2e-aws-request-serving N/A periodic Periodic 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.

Copy link
Copy Markdown
Contributor

@coderabbitai coderabbitai Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In
`@ci-operator/config/openshift/hypershift/openshift-hypershift-release-4.21__periodics-hcm.yaml`:
- Around line 41-47: The new periodic job "e2e-aws-request-serving" was added to
ci-operator config but the generated Prow job artifacts under ci-operator/jobs
were not updated; run the repository's job generation (e.g., execute make update
or the project’s generation target) to regenerate Prow job configs, verify the
generated changes include the new periodic job, and commit those generated files
(or if generation intentionally yields no diffs, add a short note/evidence in
the PR describing why no generated changes occurred); ensure the job name
"e2e-aws-request-serving" appears in the regenerated artifacts before finalizing
the PR.
🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

  • Push a commit to this branch (recommended)
  • Create a new PR with the fixes

ℹ️ Review info
⚙️ Run configuration

Configuration used: Repository YAML (base), Central YAML (inherited)

Review profile: CHILL

Plan: Enterprise

Run ID: 3882d26e-43a1-4224-a023-259434eff010

📥 Commits

Reviewing files that changed from the base of the PR and between cfed648 and ca28fa2.

⛔ Files ignored due to path filters (1)
  • ci-operator/jobs/openshift/hypershift/openshift-hypershift-release-4.21-periodics.yaml is excluded by !ci-operator/jobs/**
📒 Files selected for processing (1)
  • ci-operator/config/openshift/hypershift/openshift-hypershift-release-4.21__periodics-hcm.yaml

Comment on lines +41 to +47
- as: e2e-aws-request-serving
cron: 0 4 * * *
steps:
cluster_profile: hypershift-aws
env:
REQUEST_SERVING_COMPONENT_TEST: "true"
workflow: hypershift-aws-e2e-metrics
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue | 🟠 Major | ⚡ Quick win

🧩 Analysis chain

🏁 Script executed:

#!/bin/bash
# Verify whether this PR includes generated ci-operator/jobs changes for the new periodic test.
# Expected: at least one changed file under ci-operator/jobs/ for structural test additions.

git diff --name-only -- ci-operator/config ci-operator/jobs | sed 's#^`#-` #'
echo
echo "Changed generated job files:"
git diff --name-only -- ci-operator/jobs | sed 's#^`#-` #'

Repository: openshift/release

Length of output: 91


Regenerate and include Prow job configs for e2e-aws-request-serving.
The new periodic test entry (e2e-aws-request-serving, lines 41-47) was added to ci-operator/config, but no regenerated changes under ci-operator/jobs/** are included—please run make update and commit the generated artifacts, or provide evidence that regeneration intentionally produced no diffs.

🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In
`@ci-operator/config/openshift/hypershift/openshift-hypershift-release-4.21__periodics-hcm.yaml`
around lines 41 - 47, The new periodic job "e2e-aws-request-serving" was added
to ci-operator config but the generated Prow job artifacts under
ci-operator/jobs were not updated; run the repository's job generation (e.g.,
execute make update or the project’s generation target) to regenerate Prow job
configs, verify the generated changes include the new periodic job, and commit
those generated files (or if generation intentionally yields no diffs, add a
short note/evidence in the PR describing why no generated changes occurred);
ensure the job name "e2e-aws-request-serving" appears in the regenerated
artifacts before finalizing the PR.

@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci Bot commented May 30, 2026

@jiezhao16: 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/rehearse/periodic-ci-openshift-hypershift-release-4.21-periodics-hcm-e2e-aws cfed648 link unknown /pj-rehearse periodic-ci-openshift-hypershift-release-4.21-periodics-hcm-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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

jira/valid-reference Indicates that this PR references a valid Jira ticket of any type.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants