WINC-2016: Add TechPreview variant of WMCO aws-e2e-ote presubmit by redhat-chai-bot · Pull Request #84451 · openshift/release

redhat-chai-bot · 2026-09-02T12:33:37Z

Summary

Add a new optional presubmit job aws-e2e-ote-techpreview for the Windows Machine Config Operator (WMCO) that installs a cluster with TechPreviewNoUpgrade feature set enabled.

Motivation

The TLSAdherence feature gate (merged in openshift/api#2680) is only available when the TechPreviewNoUpgrade or DevPreviewNoUpgrade feature set is enabled. The existing aws-e2e-ote job uses the default feature set, so TLS profile adherence tests (WINC-2016) are always skipped with:

TLS adherence field not available on this cluster version (field not found in spec)

Changes

Added aws-e2e-ote-techpreview test entry to openshift-windows-machine-config-operator-master.yaml
Identical to aws-e2e-ote but with FEATURE_SET: TechPreviewNoUpgrade in env
always_run: false, optional: true — only triggers with /test aws-e2e-ote-techpreview
Regenerated prowjob definitions with make ci-operator-config and make jobs

Testing

After merge, trigger on WMCO PRs with /test aws-e2e-ote-techpreview to validate TLS adherence tests run correctly on a TechPreview cluster.

AI-generated. Review for accuracy.

@rrasouli requested in Slack thread

Summary by CodeRabbit

Adds an optional aws-e2e-ote-techpreview presubmit job to the Windows Machine Config Operator CI configuration for master and release-5.0.

The job enables TLSAdherence with CustomNoUpgrade, applies StrictAllComponents, waits for cluster stabilization, and verifies the configuration before running WMCO AWS e2e tests. This preserves Machine API support.

Contributors can trigger the job with /test aws-e2e-ote-techpreview.

openshift-ci-robot · 2026-09-02T12:33:42Z

@redhat-chai-bot: This pull request references WINC-2016 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.1.0" version, but no target version was set.

Details

In response to this:

Summary

Add a new optional presubmit job aws-e2e-ote-techpreview for the Windows Machine Config Operator (WMCO) that installs a cluster with TechPreviewNoUpgrade feature set enabled.

Motivation

The TLSAdherence feature gate (merged in openshift/api#2680) is only available when the TechPreviewNoUpgrade or DevPreviewNoUpgrade feature set is enabled. The existing aws-e2e-ote job uses the default feature set, so TLS profile adherence tests (WINC-2016) are always skipped with:
TLS adherence field not available on this cluster version (field not found in spec)
Changes

Added aws-e2e-ote-techpreview test entry to openshift-windows-machine-config-operator-master.yaml

Identical to aws-e2e-ote but with FEATURE_SET: TechPreviewNoUpgrade in env

always_run: false, optional: true — only triggers with /test aws-e2e-ote-techpreview

Regenerated prowjob definitions with make ci-operator-config and make jobs

Testing

After merge, trigger on WMCO PRs with /test aws-e2e-ote-techpreview to validate TLS adherence tests run correctly on a TechPreview cluster.

AI-generated. Review for accuracy.

@rrasouli requested in Slack thread

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 · 2026-09-02T12:34:16Z

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

Walkthrough

The master and release-5.0 configurations add an optional AWS end-to-end TechPreview job. The job enables TLS adherence, verifies the cluster settings, and runs the WMCO extension test flow.

Changes

AWS TLS adherence CI coverage

Layer / File(s)	Summary
Define the AWS job and TLS adherence setup `ci-operator/config/openshift/windows-machine-config-operator/openshift-windows-machine-config-operator-master.yaml`, `ci-operator/config/openshift/windows-machine-config-operator/openshift-windows-machine-config-operator-release-5.0.yaml`	Adds `aws-e2e-ote-techpreview` with the `ipi-aws-ovn-hybrid` workflow. The job enables `TLSAdherence` with `CustomNoUpgrade`, sets `tlsAdherence` to `StrictAllComponents`, waits for stabilization, and verifies the settings.
Run the WMCO extension test flow `ci-operator/config/openshift/windows-machine-config-operator/openshift-windows-machine-config-operator-master.yaml`, `ci-operator/config/openshift/windows-machine-config-operator/openshift-windows-machine-config-operator-release-5.0.yaml`	Runs `wmco-setup-and-test`, `openshift-tests-extension-setup-out-of-payload`, and `openshift-e2e-test`. The job excludes disruptive tests.

Priority: ⬇️ Low

Estimated code review effort: 2 (Simple) | ~10 minutes

Change: Feature

Sequence Diagram(s)

sequenceDiagram
  participant CIJob
  participant Cluster
  participant WMCOTests
  CIJob->>Cluster: Enable TLSAdherence and configure StrictAllComponents
  Cluster-->>CIJob: Report feature-gate and TLS adherence status
  CIJob->>Cluster: Wait for cluster stabilization
  CIJob->>WMCOTests: Run WMCO setup and extension e2e tests

Suggested reviewers: jrvaldes

Merge Risk: 🟡 Moderate · up to ca145

The new TLS adherence job can pass without actually exercising the enabled feature gate, so its result may provide false confidence and should be corrected before merge.

🚥 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 identifies the Jira issue and the main change: adding a TechPreview variant of the WMCO AWS end-to-end presubmit.
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	The pull request changes only four YAML CI configuration/generated presubmit files. The added lines define the static job name `aws-e2e-ote-techpreview`, CI steps, commands, and environment values. No…
Test Structure And Quality	✅ Passed	PASS: The pull request changes only four YAML CI configuration/job files. The reviewed patch contains no Go files or Ginkgo test blocks such as It, BeforeEach, AfterEach, Eventually, or Consistently. …
Microshift Test Compatibility	✅ Passed	PASS: The pull request adds CI YAML and generated presubmit job definitions only. The authoritative diff contains no new Ginkgo tests (`It`, `Describe`, `Context`, or `When`). The MicroShift Test Comp…
Single Node Openshift (Sno) Test Compatibility	✅ Passed	The pull request changes only four YAML CI configuration files. It adds the optional `aws-e2e-ote-techpreview` job and generated presubmit definitions. It does not add or modify Ginkgo e2e tests, so t…
Topology-Aware Scheduling Compatibility	✅ Passed	PASS. The pull request changes only CI operator configuration and generated Prow job files. It does not add or modify deployment manifests, operator code, or controllers. The new job contains no pod a…
Ote Binary Stdout Contract	✅ Passed	PASS. The authoritative diff changes only two CI configuration files and two generated Prow job files. It adds no OTE implementation code and no process-level Go code such as main(), TestMain(), suite…
Ipv6 And Disconnected Network Test Compatibility	✅ Passed	PASS: The pull request changes only CI YAML configuration and generated Prow job YAML. It adds no Ginkgo tests or test source files. The added lines contain no hardcoded IPv4 addresses, IPv4-only pars…
No-Weak-Crypto	✅ Passed	PASS: The pull request changes only CI YAML and generated Prow job definitions. The added commands configure `TLSAdherence`, patch cluster settings, wait for stabilization, and run tests. No added MD5…
Container-Privileges	✅ Passed	PASS. The pull request adds two CI test definitions and two generated presubmit jobs. The added YAML contains no `privileged: true`, `hostPID`, `hostNetwork`, `hostIPC`, `SYS_ADMIN`, or `allowPrivileg…
No-Sensitive-Data-In-Logs	✅ Passed	PASS: The pull request adds CI YAML commands that log only static TLSAdherence messages, loop progress, and the cluster version. FeatureGate JSON is redirected to `/dev/null`, and validation commands …

✨ Finishing Touches

🧪 Generate unit tests (beta)

Create PR with unit tests

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

rrasouli · 2026-09-02T12:55:01Z

/lgtm

rrasouli · 2026-09-02T12:57:32Z

/pj-rehearse pull-ci-openshift-windows-machine-config-operator-master-aws-e2e-ote-techpreview

openshift-ci · 2026-09-02T12:58:16Z

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: redhat-chai-bot, rrasouli
Once this PR has been reviewed and has the lgtm label, please assign jrvaldes 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 · 2026-09-02T13:00:16Z

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

rrasouli · 2026-09-02T13:07:52Z

/test ci-operator-config ci-operator-registry

redhat-chai-bot · 2026-09-02T15:24:45Z

/retest-required

AI-generated. Review for accuracy.

openshift-ci · 2026-09-02T17:23:01Z

New changes are detected. LGTM label has been removed.

rrasouli · 2026-09-02T17:53:33Z

/pj-rehearse pull-ci-openshift-windows-machine-config-operator-master-aws-e2e-ote-techpreview

openshift-merge-bot · 2026-09-02T17:54:36Z

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

rrasouli · 2026-09-03T03:40:07Z

/pj-rehearse pull-ci-openshift-windows-machine-config-operator-master-aws-e2e-ote-techpreview

openshift-merge-bot · 2026-09-03T03:40:09Z

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

rrasouli · 2026-09-03T11:52:52Z

/pj-rehearse pull-ci-openshift-windows-machine-config-operator-master-aws-e2e-ote-techpreview

openshift-merge-bot · 2026-09-03T11:55:31Z

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

rrasouli · 2026-09-03T15:21:30Z

@chai-bot https://prow.ci.openshift.org/view/gs/test-platform-results/pr-logs/pull/openshift_release/84451/rehearse-84451-pull-ci-openshift-windows-machine-config-operator-master-aws-e2e-ote-techpreview/2095481582998523904 failed job

redhat-chai-bot · 2026-09-03T15:49:39Z

/pj-rehearse pull-ci-openshift-windows-machine-config-operator-master-aws-e2e-ote-techpreview

AI-generated. Review for accuracy.

openshift-merge-bot · 2026-09-03T15:49:43Z

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

rrasouli · 2026-09-07T07:02:27Z

/pj-rehearse pull-ci-openshift-windows-machine-config-operator-master-aws-e2e-ote-techpreview

openshift-merge-bot · 2026-09-07T07:02:30Z

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

rrasouli · 2026-09-07T09:52:28Z

/pj-rehearse pull-ci-openshift-windows-machine-config-operator-release-5.0-aws-e2e-ote-techpreview

openshift-merge-bot · 2026-09-07T09:52:31Z

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

rrasouli · 2026-09-07T13:39:07Z

/test aws-e2e-ote-techpreview

rrasouli · 2026-09-07T13:39:22Z

/pj-rehearse pull-ci-openshift-windows-machine-config-operator-release-5.0-aws-e2e-ote-techpreview

dominikholler · 2026-09-12T00:46:31Z

/pj-rehearse pull-ci-openshift-windows-machine-config-operator-master-aws-e2e-ote-techpreview

openshift-ci · 2026-09-12T00:46:35Z

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

dominikholler · 2026-09-12T00:47:02Z

/pj-rehearse pull-ci-openshift-windows-machine-config-operator-release-5.0-aws-e2e-ote-techpreview

openshift-ci · 2026-09-12T00:47:05Z

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

dominikholler · 2026-09-12T04:51:19Z

Generated by Claude (Anthropic's Claude Code), reviewed and posted by @dominikholler.

@redhat-chai-bot Diagnosed both e80a5fd49 rehearsal FAILUREs — and the good news is this is not a test failure, not a flake, and not a TLS regression. Both jobs died in the enable-tls-adherence step, before the suite ever ran, so the [Disruptive] skip was never even exercised.

What actually happened (from both build logs)

The step enables the gate via CustomNoUpgrade, which rolls the kube-apiserver — you can see the API blip in both logs:
```
The connection to the server api.ci-op-...:6443 was refused - did you specify the right host or port?
```
(~4 min of connection-refused, master iterations 12–27, release-5.0 42+.)
The poll's jq check against featuregate/cluster .status.featureGates[].version never returns true, so the loop runs all 60 iterations.
a09089f9e's new fail-fast then exit 1s the step: ERROR: TLSAdherence gate did not become active after 15 minutes.

Why this is a regression, not a real problem

Against 8ab5a2e69 this same poll ran (via 419d65e12) but without the exit 1. There it simply fell through after 60 iterations, the step went on to patch apiserver.spec.tlsAdherence=StrictAllComponents, that verify passed, and the suite ran — master 18 pass, release-5.0 20 pass. So the gate does activate and StrictAllComponents is accepted; the featuregate-status jq poll is just an unreliable detector. a09089f9e turned a benign never-match into a hard kill switch — it regressed the working path.

Suggested fix — verify the real invariant, not the poll

Don't gate the step on the featuregate-status jq. The true success criterion is that apiserver.spec.tlsAdherence accepts and retains StrictAllComponents (that field only exists once the gate is live and the CRD schema re-renders). Retry the apiserver patch through the KAS rollout / connection-refused window, then assert:

echo "Enabling TLSAdherence feature gate via CustomNoUpgrade..."
oc patch featuregate cluster --type=merge \
  -p '{"spec":{"featureSet":"CustomNoUpgrade","customNoUpgrade":{"enabled":["TLSAdherence"]}}}'

echo "Setting tlsAdherence=StrictAllComponents (retry through the kube-apiserver rollout)..."
ok=false
for i in $(seq 1 60); do
  # tolerate the ~4 min API blip that CustomNoUpgrade triggers
  if oc patch apiserver cluster --type=merge \
       -p '{"spec":{"tlsAdherence":"StrictAllComponents"}}' >/dev/null 2>&1 \
     && [ "$(oc get apiserver cluster -o jsonpath='{.spec.tlsAdherence}' 2>/dev/null)" = "StrictAllComponents" ]; then
    ok=true; echo "tlsAdherence=StrictAllComponents accepted (iteration $i)"; break
  fi
  echo "  waiting for apiserver schema/gate (i=$i)..."; sleep 15
done
[ "$ok" = true ] || { echo "ERROR: tlsAdherence never accepted StrictAllComponents"; exit 1; }

echo "Waiting for cluster to stabilize..."
oc adm wait-for-stable-cluster --timeout=30m

oc get featuregate cluster -o jsonpath='{.spec.featureSet}' | grep -q CustomNoUpgrade
oc get apiserver cluster -o jsonpath='{.spec.tlsAdherence}' | grep -q StrictAllComponents
echo "TLSAdherence enabled and verified successfully."

This keeps your fail-fast intent (it still exit 1s if adherence genuinely never takes) but bases it on the field that actually matters and is robust to both the API-server blip and the flaky featuregate-status jq. The minimal alternative — just drop the exit 1 from a09089f9e and let the existing grep -q StrictAllComponents verify be the gate — would also restore the 8ab5a2e69 behavior, but the retry-on-the-real-field version above is sturdier.

Once the step is fixed, a fresh rehearsal on both jobs should go green: the 8ab5a2e69 evidence already showed the suite passing except the now-skipped [Disruptive] specs. I'm holding off on any retest until then, since a retrigger against this tip would just hit the same deterministic step failure. Happy to review the diff.

dominikholler · 2026-09-12T08:20:56Z

Generated by Claude (Anthropic's Claude Code), reviewed and posted by @dominikholler.

@redhat-chai-bot 914260f23 is exactly the right fix — and it's fully Option-A-consistent on both branches: still CustomNoUpgrade enabling only TLSAdherence, StrictAllComponents on the default (Intermediate) profile, no Modern. Crucially it now keys success on the real invariant — retrying oc patch apiserver ... tlsAdherence=StrictAllComponents through the kube-apiserver rollout and asserting the field sticks — instead of the flawed featuregate-status jq poll that a09089f9e had turned into a false-negative exit 1. set -euo pipefail and the final grep -q verifies are good hardening too.

generated-config is green, so the tip is ready to rehearse. The prior failure report is stale (it points at the old e80a5fd49 builds). Triggering fresh runs on the new tip now — master here, release-5.0 in the next comment:

/pj-rehearse pull-ci-openshift-windows-machine-config-operator-master-aws-e2e-ote-techpreview

openshift-ci · 2026-09-12T08:20:59Z

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

dominikholler · 2026-09-12T08:21:35Z

Generated by Claude (Anthropic's Claude Code), reviewed and posted by @dominikholler.

@redhat-chai-bot and the release-5.0 job on the same tip:

/pj-rehearse pull-ci-openshift-windows-machine-config-operator-release-5.0-aws-e2e-ote-techpreview

openshift-ci · 2026-09-12T08:21:38Z

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

rrasouli · 2026-09-14T15:00:53Z

/pj-rehearse pull-ci-openshift-windows-machine-config-operator-release-5.0-aws-e2e-ote-techpreview

openshift-ci · 2026-09-14T15:00:58Z

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

rrasouli · 2026-09-15T07:00:34Z

/pj-rehearse pull-ci-openshift-windows-machine-config-operator-release-5.0-aws-e2e-ote-techpreview

openshift-ci · 2026-09-15T07:00:38Z

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

Add a new presubmit test aws-e2e-ote-techpreview to both master and release-5.0 configs. The test copies the existing aws-e2e-ote test and adds an enable-tls-adherence step that enables TLSAdherence via CustomNoUpgrade post-install, allowing TLS profile adherence tests to run without switching to CAPI (which breaks MAPI-dependent WMCO e2e tests). The enable-tls-adherence step: - Patches featuregate cluster to CustomNoUpgrade with TLSAdherence - Waits for the gate to be observed in featuregate status - Sets apiserver tlsAdherence to StrictAllComponents - Waits for cluster stabilization - Verifies settings before proceeding The test is optional (always_run: false) and only runs when manually triggered with /test aws-e2e-ote-techpreview.

Add TEST_SKIPS: \[Disruptive\] to the aws-e2e-ote-techpreview env in both master and release-5.0 configs. This tells openshift-tests to skip any test spec tagged [Disruptive], avoiding unrelated timeout and node-wedge failures seen in rehearsals.

Add a post-loop check to the enable-tls-adherence step that exits 1 if the TLSAdherence feature gate never became active after 15 minutes of polling. Previously the loop would silently fall through, causing the apiserver patch to silently drop the tlsAdherence field.

Change TEST_SKIPS in aws-e2e-ote-techpreview from \[Disruptive\] to \[node-proxy\]|\[Disruptive\] to match the base aws-e2e-ote job's node-proxy skip while also excluding Disruptive tests.

The featuregate-status jq poll never actually matched TLSAdherence (it ran all 60 iterations even on the successful run). Replace with a retry loop on the apiserver patch itself — the true invariant is whether the apiserver accepts tlsAdherence=StrictAllComponents. The new loop retries the oc patch + read-back through the ~4 min kube-apiserver rollout that follows featuregate change, and exits 1 only if the apiserver never accepts StrictAllComponents.

Remove TEST_SKIPS env var from the techpreview variant in both master and release-5.0 configs to run the full test suite without skipping any tests.

The master aws-e2e-ote base job skips node-proxy tests via TEST_SKIPS: \[node-proxy\]. Add the same skip to the techpreview variant so it stays aligned with its base. The release-5.0 techpreview variant is already aligned (neither it nor its base have TEST_SKIPS), so no change needed there. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

Change aws-e2e-ote-techpreview TEST_ARGS from --disable-monitor=pod-network-avalibility,... (deny-list: 4 disabled, ~36 still run) to --monitor=e2e-test-analyzer (allow-list: only e2e-test-analyzer, ~40 suppressed) This aligns release-5.0 with the master config which already uses --monitor=e2e-test-analyzer, suppressing the Monitor test noise that obscures real TLS adherence results. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

openshift-ci · 2026-09-15T11:00:22Z

[REHEARSALNOTIFIER]
@redhat-chai-bot: 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-windows-machine-config-operator-master-aws-e2e-ote-techpreview	openshift/windows-machine-config-operator	presubmit	Presubmit changed
pull-ci-openshift-windows-machine-config-operator-release-5.0-aws-e2e-ote-techpreview	openshift/windows-machine-config-operator	presubmit	Presubmit 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.

rrasouli · 2026-09-15T11:05:46Z

/pj-rehearse pull-ci-openshift-windows-machine-config-operator-release-5.0-aws-e2e-ote-techpreview

openshift-ci · 2026-09-15T11:06:42Z

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

rrasouli · 2026-09-15T13:48:33Z

/retest

openshift-ci · 2026-09-15T15:03:33Z

@redhat-chai-bot: 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/windows-machine-config-operator/master/aws-e2e-ote-techpreview	`914260f`	link	unknown	`/pj-rehearse pull-ci-openshift-windows-machine-config-operator-master-aws-e2e-ote-techpreview`
ci/rehearse/openshift/windows-machine-config-operator/release-5.0/aws-e2e-ote-techpreview	`346e2c2`	link	unknown	`/pj-rehearse pull-ci-openshift-windows-machine-config-operator-release-5.0-aws-e2e-ote-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.

openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Sep 2, 2026

openshift-ci Bot requested review from mansikulkarni96 and wgahnagl September 2, 2026 12:34

openshift-ci Bot assigned rrasouli Sep 2, 2026

openshift-ci Bot added the lgtm Indicates that a PR is ready to be merged. label Sep 2, 2026

openshift-ci Bot removed the lgtm Indicates that a PR is ready to be merged. label Sep 2, 2026

dominikholler mentioned this pull request Sep 12, 2026

WINC-2016: Add OTE tests for TLS profile adherence openshift/windows-machine-config-operator#4550

Draft

redhat-chai-bot force-pushed the add-wmco-aws-e2e-ote-techpreview branch 2 times, most recently from 878b9a9 to 5597613 Compare September 15, 2026 05:49

redhat-chai-bot and others added 8 commits September 15, 2026 10:51

Combine node-proxy and Disruptive skip patterns in master config

fbe8cd6

Change TEST_SKIPS in aws-e2e-ote-techpreview from \[Disruptive\] to \[node-proxy\]|\[Disruptive\] to match the base aws-e2e-ote job's node-proxy skip while also excluding Disruptive tests.

Remove TEST_SKIPS from aws-e2e-ote-techpreview

0876627

Remove TEST_SKIPS env var from the techpreview variant in both master and release-5.0 configs to run the full test suite without skipping any tests.

redhat-chai-bot force-pushed the add-wmco-aws-e2e-ote-techpreview branch from 4f7d2a0 to 346e2c2 Compare September 15, 2026 10:56

Uh oh!

Conversation

redhat-chai-bot commented Sep 2, 2026 • edited by coderabbitai Bot Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Summary

Motivation

Changes

Testing

Summary by CodeRabbit

Uh oh!

openshift-ci-robot commented Sep 2, 2026 • edited by atlassian Bot Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Summary

Motivation

Changes

Testing

Uh oh!

coderabbitai Bot commented Sep 2, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Reviews paused

Walkthrough

Changes

Sequence Diagram(s)

Uh oh!

rrasouli commented Sep 2, 2026

Uh oh!

rrasouli commented Sep 2, 2026

Uh oh!

openshift-ci Bot commented Sep 2, 2026

Uh oh!

openshift-merge-bot Bot commented Sep 2, 2026

Uh oh!

rrasouli commented Sep 2, 2026

Uh oh!

redhat-chai-bot commented Sep 2, 2026

Uh oh!

openshift-ci Bot commented Sep 2, 2026

Uh oh!

rrasouli commented Sep 2, 2026

Uh oh!

openshift-merge-bot Bot commented Sep 2, 2026

Uh oh!

rrasouli commented Sep 3, 2026

Uh oh!

openshift-merge-bot Bot commented Sep 3, 2026

Uh oh!

rrasouli commented Sep 3, 2026

Uh oh!

openshift-merge-bot Bot commented Sep 3, 2026

Uh oh!

rrasouli commented Sep 3, 2026

Uh oh!

redhat-chai-bot commented Sep 3, 2026

Uh oh!

openshift-merge-bot Bot commented Sep 3, 2026

Uh oh!

rrasouli commented Sep 7, 2026

Uh oh!

openshift-merge-bot Bot commented Sep 7, 2026

Uh oh!

rrasouli commented Sep 7, 2026

Uh oh!

openshift-merge-bot Bot commented Sep 7, 2026

Uh oh!

rrasouli commented Sep 7, 2026

Uh oh!

rrasouli commented Sep 7, 2026

Uh oh!

dominikholler commented Sep 12, 2026

Uh oh!

openshift-ci Bot commented Sep 12, 2026

Uh oh!

dominikholler commented Sep 12, 2026

Uh oh!

openshift-ci Bot commented Sep 12, 2026

Uh oh!

dominikholler commented Sep 12, 2026

What actually happened (from both build logs)

Why this is a regression, not a real problem

Suggested fix — verify the real invariant, not the poll

redhat-chai-bot commented Sep 2, 2026 •

edited by coderabbitai Bot

Loading

openshift-ci-robot commented Sep 2, 2026 •

edited by atlassian Bot

Loading

coderabbitai Bot commented Sep 2, 2026 •

edited

Loading