Skip to content

[DNM]dualstack AWS debug cluster - #79562

Draft
jechen0648 wants to merge 1 commit into
openshift:mainfrom
jechen0648:dualstack-aws-debug-cluster
Draft

[DNM]dualstack AWS debug cluster#79562
jechen0648 wants to merge 1 commit into
openshift:mainfrom
jechen0648:dualstack-aws-debug-cluster

Conversation

@jechen0648

@jechen0648 jechen0648 commented May 20, 2026

Copy link
Copy Markdown
Contributor

Summary by CodeRabbit

This draft PR updates OpenShift AWS dual-stack E2E CI jobs for debugging:

  • Extends the AWS E2E workflow timeout by eight hours.
  • Adds a wait step before the main E2E test step.
  • Configures the AWS dual-stack IPv4-primary and IPv6-primary TechPreview jobs to use a custom release image override.

These changes support longer-running, manually debugged dual-stack AWS test clusters.

@openshift-ci

openshift-ci Bot commented May 20, 2026

Copy link
Copy Markdown
Contributor

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 openshift-ci Bot added the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label May 20, 2026
@coderabbitai

coderabbitai Bot commented May 20, 2026

Copy link
Copy Markdown
Contributor

Note

Reviews paused

It looks like this branch is under active development. To avoid overwhelming you with review comments due to an influx of new commits, CodeRabbit has automatically paused this review. You can configure this behavior by changing the reviews.auto_review.auto_pause_after_reviewed_commits setting.

Use the following commands to manage reviews:

  • @coderabbitai resume to resume automatic reviews.
  • @coderabbitai review to trigger a single review.

Use the checkboxes below for quick actions:

  • ▶️ Resume reviews
  • 🔍 Trigger review

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: Pro Plus

Run ID: 57d5214f-a69c-40e3-a5fb-8d41651117eb

📥 Commits

Reviewing files that changed from the base of the PR and between 78890a3 and 5677bdf.

📒 Files selected for processing (2)
  • ci-operator/config/openshift/installer/openshift-installer-main.yaml
  • ci-operator/step-registry/openshift/e2e/aws/openshift-e2e-aws-workflow.yaml
🚧 Files skipped from review as they are similar to previous changes (2)
  • ci-operator/step-registry/openshift/e2e/aws/openshift-e2e-aws-workflow.yaml
  • ci-operator/config/openshift/installer/openshift-installer-main.yaml

Walkthrough

AWS TechPreview jobs now use a custom release image. The AWS E2E workflow now sets an eight-hour timeout and runs wait before openshift-e2e-test.

Changes

AWS E2E configuration

Layer / File(s) Summary
TechPreview release image overrides
ci-operator/config/openshift/installer/openshift-installer-main.yaml
The AWS dual-stack IPv4-primary and IPv6-primary TechPreview jobs set the custom installer release image override.
E2E workflow timeout and wait
ci-operator/step-registry/openshift/e2e/aws/openshift-e2e-aws-workflow.yaml
The workflow sets TIMEOUT to +8 hours and runs wait before openshift-e2e-test.

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

Mergeability Score: ⚪ Minimal · up to 5677b

The current changes present no actionable merge-blocking risk based on the supplied evidence; normal checks and review remain appropriate.

Possibly related PRs


Important

Pre-merge checks failed

Please resolve all errors before merging. Addressing warnings is optional.

❌ Failed checks (1 error)

Check name Status Explanation Resolution
No-Sensitive-Data-In-Logs ❌ Error The PR adds an internal registry hostname to CUSTOM_OPENSHIFT_INSTALL_RELEASE_IMAGE_OVERRIDE; ipi-install echoes the custom payload and extraction image, exposing that hostname in affected job logs. Redact the custom image reference in ipi-install log messages, or use a non-sensitive reference while retaining the override for installation.
✅ Passed checks (14 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title clearly identifies the main change: debugging AWS dual-stack clusters and related E2E jobs.
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 The diff only adds YAML workflow steps and environment values; it changes no Ginkgo test titles or test source, so it introduces no unstable or overly specific test name.
Test Structure And Quality ✅ Passed The diff changes only two YAML files and adds no Ginkgo It blocks; the generic wait step also has a 72-hour timeout, so no stated Ginkgo quality failure is introduced.
Microshift Test Compatibility ✅ Passed The pull-request diff contains only two YAML configuration changes and adds no Ginkgo e2e tests or test declarations, so this check is not applicable.
Single Node Openshift (Sno) Test Compatibility ✅ Passed The diff changes only two YAML CI files. It adds no Ginkgo tests or test code with multi-node assumptions.
Topology-Aware Scheduling Compatibility ✅ Passed The diff changes only two ci-operator YAML files: CI environment values and a generic wait step. It adds no deployment, operator, controller, or scheduling constraint.
Ote Binary Stdout Contract ✅ Passed The PR changes only two CI YAML files, adding workflow settings and a wait step; it adds no OTE process code or process-level stdout writes.
Ipv6 And Disconnected Network Test Compatibility ✅ Passed The diff changes only two YAML CI configuration files and adds no Ginkgo It, Describe, Context, or When tests; the custom check is therefore inapplicable.
No-Weak-Crypto ✅ Passed The diff adds only workflow timing, a wait step, and a release-image override; it introduces no MD5, SHA1, DES, RC4, 3DES, Blowfish, ECB, custom crypto, or secret comparison.
Container-Privileges ✅ Passed The PR adds CI environment values and an existing wait reference only; no changed manifest declares privileged, hostPID, hostNetwork, hostIPC, SYS_ADMIN, root, or allowPrivilegeEscalation.
✨ 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.

@openshift-merge-bot

Copy link
Copy Markdown
Contributor

@jechen0648, pj-rehearse: unable to determine affected jobs. This could be due to a branch that needs to be rebased. ERROR:

could not determine changed registry steps: could not load step registry: failed to load registry file /var/tmp/gitrepo3376434838/ci-operator/step-registry/openshift/e2e/aws/openshift-e2e-aws-workflow.yaml: error unmarshaling JSON: while decoding JSON: json: unknown field "env"
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.

@coderabbitai coderabbitai Bot left a comment

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.

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/step-registry/openshift/e2e/aws/openshift-e2e-aws-workflow.yaml`:
- Around line 10-13: The YAML places the post block under env which breaks the
workflow; move the "post:" entry (including the "- chain: gather-core-dump"
item) out from under "env:" and place it under the job's "steps:" section as a
sibling of "pre"/"test" (so "post" is at the same level as those steps),
ensuring "TIMEOUT: +6 hours" remains under "env"; after the change run make
validate-step-registry to confirm correctness.
🪄 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: 8f39b93e-ab42-447b-841b-fe6a46808fc2

📥 Commits

Reviewing files that changed from the base of the PR and between d4371cb and 29a43d8.

📒 Files selected for processing (1)
  • ci-operator/step-registry/openshift/e2e/aws/openshift-e2e-aws-workflow.yaml

Comment thread ci-operator/step-registry/openshift/e2e/aws/openshift-e2e-aws-workflow.yaml Outdated
@jechen0648
jechen0648 force-pushed the dualstack-aws-debug-cluster branch from 29a43d8 to a9ee375 Compare May 20, 2026 19:28

@coderabbitai coderabbitai Bot left a comment

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.

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/step-registry/openshift/e2e/aws/openshift-e2e-aws-workflow.yaml`:
- Around line 5-6: The env block is incorrectly placed under steps; move the
env: TIMEOUT: +6 hours entry so that env: is a top-level sibling of steps: (not
nested under any step), preserving the TIMEOUT value and ensuring the
workflow-level environment variables are defined at the workflow root; after
relocating, run make validate-step-registry to confirm the schema is valid.
🪄 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: 1652d1b4-1624-4407-b8f3-2a0cbd4a0bb9

📥 Commits

Reviewing files that changed from the base of the PR and between 29a43d8 and a9ee375.

📒 Files selected for processing (1)
  • ci-operator/step-registry/openshift/e2e/aws/openshift-e2e-aws-workflow.yaml

Comment on lines +5 to +6
env:
TIMEOUT: +6 hours

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 | 🔴 Critical | ⚡ Quick win

Move env: out of steps:; it must be a sibling to steps:.

The env: block is currently nested under steps:, which violates the step registry workflow schema. Environment variables should be defined at the workflow level, not within the steps: block.

🔧 Corrected structure
 workflow:
   as: openshift-e2e-aws
   steps:
     allow_best_effort_post_steps: true
-    env:
-      TIMEOUT: +6 hours
     pre:
     - chain: ipi-aws-pre
     test:
     - ref: wait
     - ref: openshift-e2e-test
     post:
     - chain: gather-core-dump
     - chain: ipi-aws-post
+  env:
+    TIMEOUT: +6 hours
   documentation: |-

As per coding guidelines, "Validate step registry definitions for correctness by running make validate-step-registry".

🤖 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/step-registry/openshift/e2e/aws/openshift-e2e-aws-workflow.yaml`
around lines 5 - 6, The env block is incorrectly placed under steps; move the
env: TIMEOUT: +6 hours entry so that env: is a top-level sibling of steps: (not
nested under any step), preserving the TIMEOUT value and ensuring the
workflow-level environment variables are defined at the workflow root; after
relocating, run make validate-step-registry to confirm the schema is valid.

@jechen0648

Copy link
Copy Markdown
Contributor Author

/pj-rehearse e2e-aws-ovn-dualstack-ipv6-primary-techpreview

@openshift-merge-bot

Copy link
Copy Markdown
Contributor

@jechen0648: 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

@jechen0648: job(s): e2e-aws-ovn-dualstack-ipv6-primary-techpreview either don't exist or were not found to be affected, and cannot be rehearsed

@jechen0648

Copy link
Copy Markdown
Contributor Author

/pj-rehearse e2e-aws-ovn-installer-dualstack-ipv6-primary-techpreview

@openshift-merge-bot

Copy link
Copy Markdown
Contributor

@jechen0648: 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

@jechen0648: job(s): e2e-aws-ovn-installer-dualstack-ipv6-primary-techpreview either don't exist or were not found to be affected, and cannot be rehearsed

@jechen0648

Copy link
Copy Markdown
Contributor Author

/pj-rehearse pull-ci-openshift-installer-main-e2e-aws-ovn-dualstack-ipv4-primary-techpreview

@openshift-merge-bot

Copy link
Copy Markdown
Contributor

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

@sadasu

sadasu commented May 26, 2026

Copy link
Copy Markdown
Contributor

/pj-rehearse e2e-aws-ovn-installer-dualstack-ipv6-primary-techpreview

@openshift-merge-bot

Copy link
Copy Markdown
Contributor

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

@sadasu

sadasu commented May 26, 2026

Copy link
Copy Markdown
Contributor

/pj-rehearse pull-ci-openshift-installer-main-e2e-aws-ovn-dualstack-ipv4-primary-techpreview

@openshift-merge-bot

Copy link
Copy Markdown
Contributor

@sadasu: 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

@sadasu, pj-rehearse: unable prepare a candidate for rehearsal; rehearsals will not be run. This could be due to a branch that needs to be rebased. ERROR:

couldn't checkout base SHA 57f948e7dcb016c4e88118a48f92ae18d019ba2c: error checking out "57f948e7dcb016c4e88118a48f92ae18d019ba2c": exit status 128 fatal: unable to read tree (57f948e7dcb016c4e88118a48f92ae18d019ba2c)

@openshift-merge-bot

Copy link
Copy Markdown
Contributor

@sadasu: job(s): e2e-aws-ovn-installer-dualstack-ipv6-primary-techpreview either don't exist or were not found to be affected, and cannot be rehearsed

@jechen0648

Copy link
Copy Markdown
Contributor Author

/pj-rehearse pull-ci-openshift-installer-main-e2e-aws-ovn-dualstack-ipv4-primary-techpreview

@openshift-merge-bot

Copy link
Copy Markdown
Contributor

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

@jechen0648

Copy link
Copy Markdown
Contributor Author

/pj-rehearse pull-ci-openshift-installer-main-e2e-aws-ovn-dualstack-ipv4-primary-techpreview

@openshift-merge-bot

Copy link
Copy Markdown
Contributor

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

@jechen0648

Copy link
Copy Markdown
Contributor Author

/pj-rehearse pull-ci-openshift-installer-main-e2e-aws-ovn-dualstack-ipv4-primary-techpreview

@openshift-merge-bot

Copy link
Copy Markdown
Contributor

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

@jechen0648

Copy link
Copy Markdown
Contributor Author

/pj-rehearse pull-ci-openshift-installer-main-e2e-aws-ovn-dualstack-ipv6-primary-techpreview

@openshift-merge-bot

Copy link
Copy Markdown
Contributor

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

@jechen0648

Copy link
Copy Markdown
Contributor Author

/pj-rehearse pull-ci-openshift-installer-main-e2e-aws-ovn-dualstack-ipv6-primary-techpreview

@jechen0648
jechen0648 force-pushed the dualstack-aws-debug-cluster branch 2 times, most recently from efe8533 to 0194c79 Compare August 3, 2026 13:50
@openshift-merge-bot

Copy link
Copy Markdown
Contributor

@jechen0648: pj-rehearse could not automatically process this event because the request waited in queue for longer than 5 minutes. Use /pj-rehearse to trigger rehearsals manually.

@jechen0648

Copy link
Copy Markdown
Contributor Author

/pj-rehearse pull-ci-openshift-installer-main-e2e-aws-ovn-dualstack-ipv4-primary-techpreview

@openshift-merge-bot

Copy link
Copy Markdown
Contributor

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

@jechen0648

Copy link
Copy Markdown
Contributor Author

/pj-rehearse pull-ci-openshift-installer-main-e2e-aws-ovn-dualstack-ipv6-primary-techpreview

@openshift-merge-bot

Copy link
Copy Markdown
Contributor

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

@jechen0648

Copy link
Copy Markdown
Contributor Author

/pj-rehearse pull-ci-openshift-installer-main-e2e-aws-ovn-dualstack-ipv6-primary-techpreview

@openshift-merge-bot

Copy link
Copy Markdown
Contributor

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

@jechen0648

Copy link
Copy Markdown
Contributor Author

/pj-rehearse pull-ci-openshift-installer-main-e2e-aws-ovn-dualstack-ipv4-primary-techpreview

@openshift-merge-bot

Copy link
Copy Markdown
Contributor

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

@jechen0648
jechen0648 force-pushed the dualstack-aws-debug-cluster branch from 0194c79 to be20ca4 Compare August 5, 2026 22:09
@coderabbitai

coderabbitai Bot commented Aug 5, 2026

Copy link
Copy Markdown
Contributor

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.

@jechen0648

Copy link
Copy Markdown
Contributor Author

/pj-rehearse pull-ci-openshift-installer-main-e2e-aws-ovn-dualstack-ipv4-primary-techpreview

@openshift-merge-bot

Copy link
Copy Markdown
Contributor

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

@jechen0648
jechen0648 force-pushed the dualstack-aws-debug-cluster branch from be20ca4 to 5677bdf Compare August 13, 2026 21:50
@coderabbitai

coderabbitai Bot commented Aug 13, 2026

Copy link
Copy Markdown
Contributor

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.

@jechen0648

Copy link
Copy Markdown
Contributor Author

/pj-rehearse pull-ci-openshift-installer-main-e2e-aws-ovn-dualstack-ipv4-primary-techpreview

@openshift-merge-bot

Copy link
Copy Markdown
Contributor

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

@jechen0648
jechen0648 force-pushed the dualstack-aws-debug-cluster branch 2 times, most recently from f5a2a74 to 86ad04c Compare August 14, 2026 16:17
@openshift-ci

openshift-ci Bot commented Aug 14, 2026

Copy link
Copy Markdown
Contributor

[APPROVALNOTIFIER] This PR is NOT APPROVED

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

@openshift-merge-bot

Copy link
Copy Markdown
Contributor

[REHEARSALNOTIFIER]
@jechen0648: 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-aws-pod-identity-webhook-master-e2e-aws openshift/aws-pod-identity-webhook presubmit Registry content changed
pull-ci-openshift-aws-pod-identity-webhook-master-okd-scos-e2e-aws-ovn openshift/aws-pod-identity-webhook presubmit Registry content changed
pull-ci-openshift-aws-pod-identity-webhook-release-5.2-e2e-aws openshift/aws-pod-identity-webhook presubmit Registry content changed
pull-ci-openshift-aws-pod-identity-webhook-release-5.1-e2e-aws openshift/aws-pod-identity-webhook presubmit Registry content changed
pull-ci-openshift-aws-pod-identity-webhook-release-5.0-e2e-aws openshift/aws-pod-identity-webhook presubmit Registry content changed
pull-ci-openshift-aws-pod-identity-webhook-release-4.23-e2e-aws openshift/aws-pod-identity-webhook presubmit Registry content changed
pull-ci-openshift-aws-pod-identity-webhook-release-4.22-e2e-aws openshift/aws-pod-identity-webhook presubmit Registry content changed
pull-ci-openshift-aws-pod-identity-webhook-release-4.21-okd-scos-e2e-aws-ovn openshift/aws-pod-identity-webhook presubmit Registry content changed
pull-ci-openshift-aws-pod-identity-webhook-release-4.21-e2e-aws openshift/aws-pod-identity-webhook presubmit Registry content changed
pull-ci-openshift-aws-pod-identity-webhook-release-4.20-e2e-aws openshift/aws-pod-identity-webhook presubmit Registry content changed
pull-ci-openshift-aws-pod-identity-webhook-release-4.19-e2e-aws openshift/aws-pod-identity-webhook presubmit Registry content changed
pull-ci-openshift-aws-pod-identity-webhook-release-4.18-e2e-aws openshift/aws-pod-identity-webhook presubmit Registry content changed
pull-ci-openshift-aws-pod-identity-webhook-release-4.17-e2e-aws openshift/aws-pod-identity-webhook presubmit Registry content changed
pull-ci-openshift-aws-pod-identity-webhook-release-4.16-e2e-aws openshift/aws-pod-identity-webhook presubmit Registry content changed
pull-ci-openshift-aws-pod-identity-webhook-release-4.15-e2e-aws openshift/aws-pod-identity-webhook presubmit Registry content changed
pull-ci-openshift-aws-pod-identity-webhook-release-4.14-e2e-aws openshift/aws-pod-identity-webhook presubmit Registry content changed
pull-ci-openshift-aws-pod-identity-webhook-release-4.13-e2e-aws openshift/aws-pod-identity-webhook presubmit Registry content changed
pull-ci-openshift-aws-pod-identity-webhook-release-4.12-e2e-aws openshift/aws-pod-identity-webhook presubmit Registry content changed
pull-ci-openshift-aws-pod-identity-webhook-release-4.11-e2e-aws openshift/aws-pod-identity-webhook presubmit Registry content changed
pull-ci-openshift-aws-pod-identity-webhook-release-4.10-e2e-aws openshift/aws-pod-identity-webhook presubmit Registry content changed
pull-ci-openshift-aws-pod-identity-webhook-release-4.9-e2e-aws openshift/aws-pod-identity-webhook presubmit Registry content changed
pull-ci-openshift-aws-pod-identity-webhook-release-4.8-e2e-aws openshift/aws-pod-identity-webhook presubmit Registry content changed
pull-ci-openshift-aws-pod-identity-webhook-release-4.7-e2e-aws openshift/aws-pod-identity-webhook presubmit Registry content changed
pull-ci-openshift-aws-pod-identity-webhook-release-4.6-e2e-aws openshift/aws-pod-identity-webhook presubmit Registry content changed
pull-ci-openshift-aws-pod-identity-webhook-release-4.5-e2e-aws openshift/aws-pod-identity-webhook presubmit Registry content changed

A total of 3451 jobs have been affected by this change. The above listing is non-exhaustive and limited to 25 jobs.

A full list of affected jobs can be found here

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.

@openshift-merge-bot

Copy link
Copy Markdown
Contributor

[REHEARSALNOTIFIER]
@jechen0648: 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-machine-api-operator-main-okd-scos-e2e-aws-ovn openshift/machine-api-operator presubmit Registry content changed
pull-ci-openshift-machine-api-operator-main-e2e-aws-ovn openshift/machine-api-operator presubmit Registry content changed
pull-ci-openshift-machine-api-operator-release-5.2-e2e-aws-ovn openshift/machine-api-operator presubmit Registry content changed
pull-ci-openshift-machine-api-operator-release-5.1-e2e-aws-ovn openshift/machine-api-operator presubmit Registry content changed
pull-ci-openshift-machine-api-operator-release-5.0-e2e-aws-ovn openshift/machine-api-operator presubmit Registry content changed
pull-ci-openshift-machine-api-operator-release-4.23-e2e-aws-ovn openshift/machine-api-operator presubmit Registry content changed
pull-ci-openshift-machine-api-operator-release-4.22-e2e-aws-ovn openshift/machine-api-operator presubmit Registry content changed
pull-ci-openshift-machine-api-operator-release-4.21-e2e-aws-ovn openshift/machine-api-operator presubmit Registry content changed
pull-ci-openshift-machine-api-operator-release-4.21-okd-scos-e2e-aws-ovn openshift/machine-api-operator presubmit Registry content changed
pull-ci-openshift-machine-api-operator-release-4.20-e2e-aws-ovn openshift/machine-api-operator presubmit Registry content changed
pull-ci-openshift-machine-api-operator-release-4.19-e2e-aws-ovn openshift/machine-api-operator presubmit Registry content changed
pull-ci-openshift-machine-api-operator-release-4.18-e2e-aws-ovn openshift/machine-api-operator presubmit Registry content changed
pull-ci-openshift-machine-api-operator-release-4.17-e2e-aws-ovn openshift/machine-api-operator presubmit Registry content changed
pull-ci-openshift-machine-api-operator-release-4.16-e2e-aws-ovn openshift/machine-api-operator presubmit Registry content changed
pull-ci-openshift-machine-api-operator-release-4.15-e2e-aws-ovn openshift/machine-api-operator presubmit Registry content changed
pull-ci-openshift-machine-api-operator-release-4.14-e2e-aws-ovn openshift/machine-api-operator presubmit Registry content changed
pull-ci-openshift-machine-api-operator-release-4.13-e2e-aws-ovn openshift/machine-api-operator presubmit Registry content changed
pull-ci-openshift-machine-api-operator-release-4.12-e2e-aws-ovn openshift/machine-api-operator presubmit Registry content changed
pull-ci-openshift-machine-api-operator-release-4.11-e2e-aws openshift/machine-api-operator presubmit Registry content changed
pull-ci-openshift-machine-api-operator-release-4.10-e2e-aws openshift/machine-api-operator presubmit Registry content changed
pull-ci-openshift-machine-api-operator-release-4.9-e2e-aws openshift/machine-api-operator presubmit Registry content changed
pull-ci-openshift-machine-api-operator-release-4.8-e2e-aws openshift/machine-api-operator presubmit Registry content changed
pull-ci-openshift-machine-api-operator-release-4.7-e2e-aws openshift/machine-api-operator presubmit Registry content changed
pull-ci-openshift-machine-api-operator-release-4.6-e2e-aws openshift/machine-api-operator presubmit Registry content changed
pull-ci-openshift-kubernetes-metrics-server-main-okd-scos-e2e-aws-ovn openshift/kubernetes-metrics-server presubmit Registry content changed

A total of 3451 jobs have been affected by this change. The above listing is non-exhaustive and limited to 25 jobs.

A full list of affected jobs can be found here

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.

@jechen0648

Copy link
Copy Markdown
Contributor Author

/pj-rehearse pull-ci-openshift-installer-main-e2e-aws-ovn-dualstack-ipv4-primary-techpreview

@openshift-merge-bot

Copy link
Copy Markdown
Contributor

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

@openshift-ci

openshift-ci Bot commented Aug 15, 2026

Copy link
Copy Markdown
Contributor

@jechen0648: 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/installer/release-5.0/e2e-aws-ovn-dualstack-ipv6-primary-techpreview 219c3a5 link unknown /pj-rehearse pull-ci-openshift-installer-release-5.0-e2e-aws-ovn-dualstack-ipv6-primary-techpreview
ci/rehearse/openshift/installer/release-5.0/e2e-aws-ovn-dualstack-ipv4-primary-techpreview 219c3a5 link unknown /pj-rehearse pull-ci-openshift-installer-release-5.0-e2e-aws-ovn-dualstack-ipv4-primary-techpreview
ci/rehearse/openshift/installer/main/e2e-aws-ovn-dualstack-ipv6-primary-techpreview 0194c79 link unknown /pj-rehearse pull-ci-openshift-installer-main-e2e-aws-ovn-dualstack-ipv6-primary-techpreview
ci/rehearse/openshift/installer/main/e2e-aws-ovn-dualstack-ipv4-primary-techpreview 86ad04c link unknown /pj-rehearse pull-ci-openshift-installer-main-e2e-aws-ovn-dualstack-ipv4-primary-techpreview

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

do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants