Skip to content

[release-4.21] OCPBUGS-87008: Stabilize ocl 4.21#6138

Open
umohnani8 wants to merge 3 commits into
openshift:release-4.21from
umohnani8:stabilize-ocl-4.21
Open

[release-4.21] OCPBUGS-87008: Stabilize ocl 4.21#6138
umohnani8 wants to merge 3 commits into
openshift:release-4.21from
umohnani8:stabilize-ocl-4.21

Conversation

@umohnani8
Copy link
Copy Markdown
Contributor

This is a manual backport of #5652, #5613, and #5595 to stabilize the e2e-ocl test suite.

This also includes breaking the ocl test suite into 2 parts.

@openshift-merge-bot
Copy link
Copy Markdown
Contributor

Pipeline controller notification
This repo is configured to use the pipeline controller. Second-stage tests will be triggered either automatically or after lgtm label is added, depending on the repository configuration. The pipeline controller will automatically detect which contexts are required and will utilize /test Prow commands to trigger the second stage.

For optional jobs, comment /test ? to see a list of all defined jobs. To trigger manually all jobs from second stage use /pipeline required command.

This repository is configured in: LGTM mode

@coderabbitai
Copy link
Copy Markdown

coderabbitai Bot commented Jun 3, 2026

Important

Review skipped

Auto reviews are disabled on base/target branches other than the default branch.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Repository: openshift/coderabbit/.coderabbit.yaml

Review profile: CHILL

Plan: Enterprise

Run ID: 5d506835-c9b0-458d-bda8-b16af58c805c

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

  • 🔍 Trigger review
✨ 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.

@umohnani8 umohnani8 changed the title Stabilize ocl 4.21 [release-4.21] OCPBUGS-87008: Stabilize ocl 4.21 Jun 3, 2026
@openshift-ci-robot openshift-ci-robot added jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. labels Jun 3, 2026
@openshift-ci-robot
Copy link
Copy Markdown
Contributor

@umohnani8: This pull request references Jira Issue OCPBUGS-87008, which is invalid:

  • expected the bug to target either version "4.21." or "openshift-4.21.", but it targets "4.22.0" instead
  • expected dependent Jira Issue OCPBUGS-86865 to be in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but it is POST instead

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

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

Details

In response to this:

This is a manual backport of #5652, #5613, and #5595 to stabilize the e2e-ocl test suite.

This also includes breaking the ocl test suite into 2 parts.

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.

@umohnani8
Copy link
Copy Markdown
Contributor Author

/jira refresh

@openshift-ci-robot
Copy link
Copy Markdown
Contributor

@umohnani8: This pull request references Jira Issue OCPBUGS-87008, which is invalid:

  • expected dependent Jira Issue OCPBUGS-86865 to be in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but it is POST instead

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

Details

In response to this:

/jira refresh

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

@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci Bot commented Jun 3, 2026

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: umohnani8

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

The pull request process is described here

Details Needs approval from an approver in each of these files:

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

@openshift-ci openshift-ci Bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Jun 3, 2026
umohnani8 added 3 commits June 3, 2026 14:32
Replace the monolithic e2e-ocl test suite with two sharded suites
(e2e-ocl-1of2 and e2e-ocl-2of2) and a shared helper package
(e2e-ocl-shared) to reduce overall CI time by running in parallel.

The sharded tests incorporate all stabilization fixes from main:
- Fix cleanup verification timeouts with per-resource contexts
- Fix cleanup ordering to delete owners before dependents
- Increase poll intervals to avoid rate limiter exhaustion
- Make log streaming errors non-fatal
- Increase job completion timeout for CI environments
- Make TestImagePrunerErrors flexible to registry behavior changes

Adapt MachineOSBuild construction calls to use the
NewMachineOSBuildFromAPIOrDie API available on this branch.

Exclude TestStaleAnnotationClearedOnLayerOnlyChange as it requires
a corresponding production fix not present on this branch.

Makefile targets:
- Remove: test-e2e-ocl (190m)
- Add: test-e2e-ocl-1of2 (120m), test-e2e-ocl-2of2 (150m)

Signed-off-by: Urvashi <umohnani@redhat.com>
TestMachineOSConfigChangeRestartsBuild flakes because the build controller
(running 3 concurrent workers) races between deleteMachineOSConfig for the
previous test's MOSC and addMachineOSConfig for the new test's MOSC. Since
both MOSCs share the same name, deleteMachineOSConfig's label-based query
matches and deletes MOSBs created by the new MOSC.
Fix both the controller and test assertions.

Signed-off-by: Urvashi <umohnani@redhat.com>
1. Restore assertBuildJobIsAsExpected function and its call sites in
   both shards. This was present in the 4.21 monolithic suite and
   validates that build pods use the correct MCO container images.

2. Fix waitForMOSCToUpdateCurrentMOSB in 2of2 to include the empty
   annotation guard (currentMOSB != "") matching 1of2, so it handles
   temporarily cleared annotations correctly.

3. Restore strings.Contains in TestSSHKeyAndPasswordForOSBuilder
   instead of the custom contains() helper from main, matching the
   original 4.21 implementation.

Signed-off-by: Urvashi <umohnani@redhat.com>
@umohnani8 umohnani8 force-pushed the stabilize-ocl-4.21 branch from b57db55 to 49e33c4 Compare June 3, 2026 18:32
@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci Bot commented Jun 3, 2026

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

Test name Commit Details Required Rerun command
ci/prow/e2e-gcp-op-ocl b57db55 link false /test e2e-gcp-op-ocl

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

approved Indicates a PR has been approved by an approver from all required OWNERS files. jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. 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