Skip to content

OPRUN-4392,OPRUN-4393: Add OLMv1 progress deadline QE tests#745

Open
bandrade wants to merge 3 commits into
openshift:mainfrom
bandrade:feature/ocp-88331-88332-automation
Open

OPRUN-4392,OPRUN-4393: Add OLMv1 progress deadline QE tests#745
bandrade wants to merge 3 commits into
openshift:mainfrom
bandrade:feature/ocp-88331-88332-automation

Conversation

@bandrade

@bandrade bandrade commented Jun 3, 2026

Copy link
Copy Markdown
Contributor

Summary

  • Automates OCP-88331 and OCP-88332 in the OpenShift OLMv1 QE suite.
  • Adds a focused ClusterExtension progress-deadline spec that builds in-cluster bundle and catalog images for successful and failing rollout versions.
  • Verifies ProgressDeadlineExceeded on an initial failed rollout and ProbeFailure while upgrading to a bad revision under the NewOLMBoxCutterRuntime feature gate.

Validation

  • go test -mod=vendor ./test/qe/specs
  • make build
  • ./bin/olmv1-tests-ext list -o names | rg '88331|88332'\n- make verify GO=/Users/bandrade/go/pkg/mod/golang.org/toolchain@v0.0.1-go1.25.7.darwin-arm64/bin/go

Summary by CodeRabbit

  • Tests
    • Added a new Ginkgo test covering ClusterExtension rollout behavior when persistent bundle/controller image errors occur, including progress-deadline timeouts and the expected status/reason propagation.
    • Added coverage for upgrade behavior from a healthy revision to a failing replacement revision, asserting correct rollout and readiness signals.
    • Updated the OLMv1 test payload ordering to run the new Boxcutter runtime progress-deadline scenarios earlier and adjust related scenario placement.

Automate the ClusterExtension rollout failure coverage for OCP-88331 and OCP-88332 by building in-cluster bundle and catalog images for successful and failing bundle versions.

The new QE specs verify ProgressDeadlineExceeded on an initial failed rollout and ProbeFailure while upgrading to a bad revision under the BoxCutter runtime.

Signed-off-by: Bruno Andrade <bruno.balint@gmail.com>
@coderabbitai

coderabbitai Bot commented Jun 3, 2026

Copy link
Copy Markdown

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info
⚙️ Run configuration

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

Review profile: CHILL

Plan: Enterprise

Run ID: 0927e05f-5891-4af8-9991-df313e5bb003

📥 Commits

Reviewing files that changed from the base of the PR and between 1266b54 and e0817e5.

📒 Files selected for processing (2)
  • openshift/tests-extension/.openshift-tests-extension/openshift_payload_olmv1.json
  • openshift/tests-extension/test/qe/specs/olmv1_ce_progress_deadline.go
🚧 Files skipped from review as they are similar to previous changes (1)
  • openshift/tests-extension/test/qe/specs/olmv1_ce_progress_deadline.go

Walkthrough

Adds a Ginkgo suite for ClusterExtension progress-deadline and rollout failure behavior. The tests build synthetic bundle and catalog images, validate install and upgrade status conditions, and register two Boxcutter runtime cases in the OLMv1 test payload.

Changes

ClusterExtension Progress-Deadline Coverage

Layer / File(s) Summary
Synthetic fixture generation
openshift/tests-extension/test/qe/specs/olmv1_ce_progress_deadline.go
Creates namespaces, RBAC, synthetic bundle/catalog images, and ClusterCatalog resources from generated archives and metadata.
ClusterExtension rollout scenarios
openshift/tests-extension/test/qe/specs/olmv1_ce_progress_deadline.go
Adds install and upgrade scenarios covering ProgressDeadlineExceeded, active revisions, RollingOut, and probe failures.
Status validation and cleanup
openshift/tests-extension/test/qe/specs/olmv1_ce_progress_deadline.go
Adds polling assertions for catalog, extension, and object-set conditions, active revisions, timeouts, and Kubernetes object cleanup.
OLMv1 payload registration
openshift/tests-extension/.openshift-tests-extension/openshift_payload_olmv1.json
Adds the two progress-deadline test cases and reorders related Boxcutter runtime, watchNamespace, API validation, and stress entries.

Estimated code review effort: 4 (Complex) | ~45 minutes

Sequence Diagram(s)

sequenceDiagram
  participant QE Spec
  participant BuildConfig
  participant ClusterCatalog
  participant ClusterExtension
  participant ClusterObjectSet
  QE Spec->>BuildConfig: Build synthetic bundle and catalog images
  QE Spec->>ClusterCatalog: Create catalog reference
  ClusterCatalog-->>QE Spec: Report Serving
  QE Spec->>ClusterExtension: Create or upgrade extension
  ClusterExtension->>ClusterObjectSet: Reconcile bundle revision
  ClusterObjectSet-->>ClusterExtension: Report rollout and probe conditions
  ClusterExtension-->>QE Spec: Report deadline and active revisions
Loading

Possibly related PRs

Suggested reviewers: pedjak, rashmigottipati

🚥 Pre-merge checks | ✅ 14 | ❌ 1

❌ Failed checks (1 warning)

Check name Status Explanation Resolution
Docstring Coverage ⚠️ Warning Docstring coverage is 0.00% which is insufficient. The required threshold is 80.00%. Write docstrings for the functions missing them to satisfy the coverage threshold.
✅ 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 matches the main change: adding OLMv1 progress deadline QE tests.
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 Test titles are static strings with fixed Polarion IDs; no timestamps, UUIDs, node/namespace/pod names, or other runtime values appear in titles.
Test Structure And Quality ✅ Passed Each It covers one rollout scenario; resources are cleaned via g.DeferCleanup, waits use explicit timeouts, assertions include messages, and patterns match repo style.
Microshift Test Compatibility ✅ Passed The new Ginkgo spec uses BuildConfig and OLMv1/FeatureGate APIs, but both tests are guarded by exutil.SkipMicroshift() in BeforeEach, so MicroShift skips them.
Single Node Openshift (Sno) Test Compatibility ✅ Passed The new spec uses OpenShift APIs/builds only, makes no multi-node or HA assumptions, and its bundle deploys a single replica.
Topology-Aware Scheduling Compatibility ✅ Passed The PR only adds QE test code and a test bundle CSV; it uses no node selectors, affinity, tolerations, spread constraints, or topology-based replica logic.
Ote Binary Stdout Contract ✅ Passed The new spec and metadata add no process-level stdout writes; main.go has no stdout/log setup, and test helpers only use GinkgoWriter or fmt.Sprintf.
Ipv6 And Disconnected Network Test Compatibility ✅ Passed The new Ginkgo spec only uses the cluster's internal image registry/builds and ShellImage maps to image-registry.svc; no IPv4 literals, ParseIP, or public hosts found.
No-Weak-Crypto ✅ Passed Touched changes are a QE test and payload JSON; scans found no MD5/SHA1/DES/RC4/3DES/Blowfish/ECB, custom crypto, or secret/token comparisons.
Container-Privileges ✅ Passed No privileged/host namespace/SYS_ADMIN settings were added; the embedded CSV uses runAsNonRoot:true and allowPrivilegeEscalation:false.
No-Sensitive-Data-In-Logs ✅ Passed PASS: The new spec has no log/print calls or sensitive-term matches; messages are generic and don’t emit secrets, PII, or internal hostnames.
✨ 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-ci openshift-ci Bot requested review from pedjak and rashmigottipati June 3, 2026 16:46
@openshift-ci

openshift-ci Bot commented Jun 3, 2026

Copy link
Copy Markdown
Contributor

[APPROVALNOTIFIER] This PR is NOT APPROVED

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

@coderabbitai coderabbitai Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

🧹 Nitpick comments (1)
openshift/tests-extension/test/qe/specs/olmv1_ce_progress_deadline.go (1)

34-36: 💤 Low value

Remove ineffective GinkgoRecover() call.

defer g.GinkgoRecover() at the Describe level is dead code. The Describe callback executes during test tree construction, not test execution, so this deferred call runs before any specs execute. GinkgoRecover is designed to catch panics within goroutines spawned from It blocks, not at the suite construction level.

🧹 Suggested fix
 var _ = g.Describe("[sig-olmv1][Jira:OLM][OCPFeatureGate:NewOLMBoxCutterRuntime] clusterextension progress deadline", g.Label("NonHyperShiftHOST"), func() {
-	defer g.GinkgoRecover()
-
 	var oc = exutil.NewCLIWithoutNamespace("default")
🤖 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 `@openshift/tests-extension/test/qe/specs/olmv1_ce_progress_deadline.go` around
lines 34 - 36, Remove the ineffective deferred call to g.GinkgoRecover() from
the Describe callback: locate the anonymous function passed to g.Describe (the
function literal in the declaration starting with var _ = g.Describe(..., func()
{ ... })) and delete the line containing defer g.GinkgoRecover(); if panic
recovery is needed for goroutines spawned during tests, move a g.GinkgoRecover()
call into the appropriate It/BeforeEach/AfterEach block or the goroutine
entrypoint instead.
🤖 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.

Nitpick comments:
In `@openshift/tests-extension/test/qe/specs/olmv1_ce_progress_deadline.go`:
- Around line 34-36: Remove the ineffective deferred call to g.GinkgoRecover()
from the Describe callback: locate the anonymous function passed to g.Describe
(the function literal in the declaration starting with var _ = g.Describe(...,
func() { ... })) and delete the line containing defer g.GinkgoRecover(); if
panic recovery is needed for goroutines spawned during tests, move a
g.GinkgoRecover() call into the appropriate It/BeforeEach/AfterEach block or the
goroutine entrypoint instead.

ℹ️ Review info
⚙️ Run configuration

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

Review profile: CHILL

Plan: Enterprise

Run ID: 9db03a8f-8565-4538-ba1f-c5d77f3957d3

📥 Commits

Reviewing files that changed from the base of the PR and between 402aee8 and 1266b54.

📒 Files selected for processing (1)
  • openshift/tests-extension/test/qe/specs/olmv1_ce_progress_deadline.go

Regenerate the tests-extension metadata after adding the ClusterExtension progress deadline QE coverage.

Signed-off-by: Bruno Andrade <bruno.balint@gmail.com>
@bandrade

bandrade commented Jun 4, 2026

Copy link
Copy Markdown
Contributor Author

/test openshift-e2e-aws
/test openshift-e2e-aws-techpreview

@bandrade

bandrade commented Jun 4, 2026

Copy link
Copy Markdown
Contributor Author

/test openshift-e2e-aws-techpreview

@openshift-ci

openshift-ci Bot commented Jun 4, 2026

Copy link
Copy Markdown
Contributor

@bandrade: all tests passed!

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.

@tmshort

tmshort commented Jun 4, 2026

Copy link
Copy Markdown
Contributor

Needs a Jira ticket or NO-ISSUE

@dtfranz

dtfranz commented Jun 5, 2026

Copy link
Copy Markdown
Contributor

/retitle OPRUN-4392,OPRUN-4393: Add OLMv1 progress deadline QE tests

@openshift-ci openshift-ci Bot changed the title 🌱 Add OLMv1 progress deadline QE tests OPRUN-4392,OPRUN-4393: Add OLMv1 progress deadline QE tests Jun 5, 2026
@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Jun 5, 2026
@openshift-ci-robot

openshift-ci-robot commented Jun 5, 2026

Copy link
Copy Markdown

@bandrade: This pull request references OPRUN-4392 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.

This pull request references OPRUN-4393 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

  • Automates OCP-88331 and OCP-88332 in the OpenShift OLMv1 QE suite.
  • Adds a focused ClusterExtension progress-deadline spec that builds in-cluster bundle and catalog images for successful and failing rollout versions.
  • Verifies ProgressDeadlineExceeded on an initial failed rollout and ProbeFailure while upgrading to a bad revision under the NewOLMBoxCutterRuntime feature gate.

Validation

  • go test -mod=vendor ./test/qe/specs
  • make build
  • ./bin/olmv1-tests-ext list -o names | rg '88331|88332'\n- make verify GO=/Users/bandrade/go/pkg/mod/golang.org/toolchain@v0.0.1-go1.25.7.darwin-arm64/bin/go

Summary by CodeRabbit

  • Tests
  • Added comprehensive test suite for ClusterExtension progress deadline and rollout scenarios, including validation of failure handling and upgrade behavior with persistent image errors.

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.

Comment thread openshift/tests-extension/test/qe/specs/olmv1_ce_progress_deadline.go Outdated
@perdasilva

Copy link
Copy Markdown
Contributor

/jira refresh

@openshift-ci-robot

openshift-ci-robot commented Jun 12, 2026

Copy link
Copy Markdown

@perdasilva: This pull request references OPRUN-4392 which is a valid jira issue.

This pull request references OPRUN-4393 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:

/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.

@dtfranz

dtfranz commented Jun 22, 2026

Copy link
Copy Markdown
Contributor

/test payload-job

@openshift-ci

openshift-ci Bot commented Jun 22, 2026

Copy link
Copy Markdown
Contributor

@dtfranz: The specified target(s) for /test were not found.
The following commands are available to trigger required jobs:

/test bindata-check
/test check-sync-pr-valid
/test default-catalog-consistency
/test e2e-aws-olmv1-ext
/test e2e-aws-techpreview-olmv1-ext
/test e2e-gcp-ovn-upgrade
/test images
/test okd-scos-images
/test openshift-e2e-aws
/test openshift-e2e-aws-techpreview
/test tests-extension
/test unit
/test verify
/test verify-commits
/test verify-deps

The following commands are available to trigger optional jobs:

/test e2e-aws-upgrade-ovn-single-node
/test okd-scos-e2e-aws-ovn

Use /test all to run the following jobs that were automatically triggered:

pull-ci-openshift-operator-framework-operator-controller-main-check-sync-pr-valid
pull-ci-openshift-operator-framework-operator-controller-main-e2e-aws-olmv1-ext
pull-ci-openshift-operator-framework-operator-controller-main-e2e-aws-techpreview-olmv1-ext
pull-ci-openshift-operator-framework-operator-controller-main-e2e-aws-upgrade-ovn-single-node
pull-ci-openshift-operator-framework-operator-controller-main-e2e-gcp-ovn-upgrade
pull-ci-openshift-operator-framework-operator-controller-main-images
pull-ci-openshift-operator-framework-operator-controller-main-okd-scos-images
pull-ci-openshift-operator-framework-operator-controller-main-openshift-e2e-aws
pull-ci-openshift-operator-framework-operator-controller-main-openshift-e2e-aws-techpreview
pull-ci-openshift-operator-framework-operator-controller-main-tests-extension
pull-ci-openshift-operator-framework-operator-controller-main-unit
pull-ci-openshift-operator-framework-operator-controller-main-verify
pull-ci-openshift-operator-framework-operator-controller-main-verify-commits
pull-ci-openshift-operator-framework-operator-controller-main-verify-deps
Details

In response to this:

/test payload-job

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.

@dtfranz

dtfranz commented Jun 22, 2026

Copy link
Copy Markdown
Contributor

Don't think this will work but...

/test e2e-aws-ovn-techpreview-extended-f1

@openshift-ci

openshift-ci Bot commented Jun 22, 2026

Copy link
Copy Markdown
Contributor

@dtfranz: The specified target(s) for /test were not found.
The following commands are available to trigger required jobs:

/test bindata-check
/test check-sync-pr-valid
/test default-catalog-consistency
/test e2e-aws-olmv1-ext
/test e2e-aws-techpreview-olmv1-ext
/test e2e-gcp-ovn-upgrade
/test images
/test okd-scos-images
/test openshift-e2e-aws
/test openshift-e2e-aws-techpreview
/test tests-extension
/test unit
/test verify
/test verify-commits
/test verify-deps

The following commands are available to trigger optional jobs:

/test e2e-aws-upgrade-ovn-single-node
/test okd-scos-e2e-aws-ovn

Use /test all to run the following jobs that were automatically triggered:

pull-ci-openshift-operator-framework-operator-controller-main-check-sync-pr-valid
pull-ci-openshift-operator-framework-operator-controller-main-e2e-aws-olmv1-ext
pull-ci-openshift-operator-framework-operator-controller-main-e2e-aws-techpreview-olmv1-ext
pull-ci-openshift-operator-framework-operator-controller-main-e2e-aws-upgrade-ovn-single-node
pull-ci-openshift-operator-framework-operator-controller-main-e2e-gcp-ovn-upgrade
pull-ci-openshift-operator-framework-operator-controller-main-images
pull-ci-openshift-operator-framework-operator-controller-main-okd-scos-images
pull-ci-openshift-operator-framework-operator-controller-main-openshift-e2e-aws
pull-ci-openshift-operator-framework-operator-controller-main-openshift-e2e-aws-techpreview
pull-ci-openshift-operator-framework-operator-controller-main-tests-extension
pull-ci-openshift-operator-framework-operator-controller-main-unit
pull-ci-openshift-operator-framework-operator-controller-main-verify
pull-ci-openshift-operator-framework-operator-controller-main-verify-commits
pull-ci-openshift-operator-framework-operator-controller-main-verify-deps
Details

In response to this:

Don't think this will work but...

/test e2e-aws-ovn-techpreview-extended-f1

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.

Signed-off-by: Bruno Andrade <bruno.balint@gmail.com>
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.

5 participants