Skip to content

OCPQE-31752: enhance qe test cases#1254

Merged
openshift-merge-bot[bot] merged 1 commit intoopenshift:mainfrom
Xia-Zhao-rh:enhance_qe_cases
Mar 12, 2026
Merged

OCPQE-31752: enhance qe test cases#1254
openshift-merge-bot[bot] merged 1 commit intoopenshift:mainfrom
Xia-Zhao-rh:enhance_qe_cases

Conversation

@Xia-Zhao-rh
Copy link
Copy Markdown
Contributor

@Xia-Zhao-rh Xia-Zhao-rh commented Mar 10, 2026

================================================
[1/8] Running test:
[sig-operator][Jira:OLM] OLMv0 within a namespace PolarionID:40529-[OTP][Skipped:Disconnected]OPERATOR_CONDITION_NAME should have correct value
================================================

✓ Test PASSED (320s)

================================================
[2/8] Running test:
[sig-operator][Jira:OLM] OLMv0 within a namespace PolarionID:47322-[OTP][Skipped:Disconnected]Arbitrary Constraints can be defined as bundle properties
================================================

✓ Test PASSED (349s)

================================================
[3/8] Running test:
[sig-operator][Jira:OLM] OLMv0 within a namespace PolarionID:47319-[OTP][Skipped:Disconnected]olm raised error when Arbitrary Compound Constraints is defined wrongly
================================================

✓ Test PASSED (255s)

================================================
[4/8] Running test:
[sig-operator][Jira:OLM] OLMv0 within a namespace PolarionID:47319-[OTP][Skipped:Disconnected]Arbitrary Compound Constraints with AND can be defined as bundle properties with less than
================================================

✓ Test PASSED (249s)

================================================
[5/8] Running test:
[sig-operator][Jira:OLM] OLMv0 within a namespace PolarionID:47319-[OTP][Skipped:Disconnected]Arbitrary Compound Constraints with AND can be defined as bundle properties with more than
================================================

✓ Test PASSED (247s)

================================================
[6/8] Running test:
[sig-operator][Jira:OLM] OLMv0 within a namespace PolarionID:47323-[OTP][Skipped:Disconnected]Arbitrary Compound Constraints with OR can be defined as bundle properties
================================================

✓ Test PASSED (300s)

================================================
[7/8] Running test:
[sig-operator][Jira:OLM] OLMv0 within a namespace PolarionID:47323-[OTP][Skipped:Disconnected]Arbitrary Compound Constraints with NOT can be defined as bundle properties
================================================

✓ Test PASSED (300s)

================================================
[8/8] Running test:
[sig-operator][Jira:OLM] OLMv0 within a namespace PolarionID:59380-PolarionID:68671-[OTP][Skipped:Disconnected]Upgrade should be success when there are multiple upgrade paths between channel entries
================================================

✓ Test PASSED (345s)

================================================
Test Execution Summary
================================================
Total Duration: 2367s
Tests Run:      8 / 8
Passed:         8
Failed:         0
Skipped:        0
================================================

@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Mar 10, 2026
@openshift-ci-robot
Copy link
Copy Markdown

openshift-ci-robot commented Mar 10, 2026

@Xia-Zhao-rh: This pull request references OCPQE-31752 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 sub-task to target the "4.22.0" version, but no target version was set.

Details

In response to this:

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

coderabbitai Bot commented Mar 10, 2026

Walkthrough

This PR updates OLMv0 non-all-namespaces tests to use a new CatalogSource image (catsrc-40529), reorders test steps to create OperatorGroup and CatalogSource before Subscription, and updates operator versions, channels, and CSV references consistently across multiple test cases.

Changes

Cohort / File(s) Summary
OLMv0 Test Updates
tests-extension/test/qe/specs/olmv0_nonallns.go
Introduces new CatalogSourceDescription, updates SubscriptionDescription fields with new operator packages and versions (nginx-operator versions), changes channel values, updates CSV-related assertions to match new operator versions, reorders resource creation steps, and adds deferred cleanup for the new catalog source.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~12 minutes

🚥 Pre-merge checks | ✅ 3 | ❌ 2

❌ Failed checks (1 warning, 1 inconclusive)

Check name Status Explanation Resolution
Test Structure And Quality ⚠️ Warning Test uses unsafe catsrc.Create() instead of catsrc.CreateWithCheck(), creating a race condition where subscription creation may execute before CatalogSource reaches READY state. Replace catsrc.Create(oc, itName, dr) with catsrc.CreateWithCheck(oc, itName, dr) at line 4153 to ensure CatalogSource readiness before subscription creation.
Title check ❓ Inconclusive The title 'OCPQE-31752: enhance qe test cases' is vague and generic, using non-descriptive language like 'enhance' that doesn't convey specific information about the changeset. Replace the generic 'enhance qe test cases' with a specific description of the main change, such as 'Update test fixtures for OLM catalog sources and subscriptions' or similar that reflects the actual modifications to test cases.
✅ Passed checks (3 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Stable And Deterministic Test Names ✅ Passed Test file analysis confirms all test declarations use static strings without dynamic content like generated names, timestamps, or UUIDs.

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

✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Post copyable unit tests in a comment

Tip

Try Coding Plans. Let us write the prompt for your AI agent so you can ship faster (with fewer bugs).
Share your feedback on Discord.


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

openshift-ci-robot commented Mar 10, 2026

@Xia-Zhao-rh: This pull request references OCPQE-31752 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 sub-task to target the "4.22.0" version, but no target version was set.

Details

In response to this:

Summary by CodeRabbit

  • Tests
  • Updated test specifications to validate operator deployment flows with new catalog source configurations and operator versions. Reworked test sequencing to ensure proper resource initialization order and updated validation checks to reflect current operator artifacts.

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 openshift-ci Bot requested review from dtfranz and thetechnick March 10, 2026 11:18
Copy link
Copy Markdown

@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

Caution

Some comments are outside the diff and can’t be posted inline due to platform limitations.

⚠️ Outside diff range comments (1)
tests-extension/test/qe/specs/olmv0_nonallns.go (1)

4826-4841: ⚠️ Potential issue | 🟠 Major

Don't treat Installing as a passing end state in these constraint tests.

These polls now return success while the expected CSVs are still Installing. That can turn stalled or failed installs into false greens and weakens what these cases are validating. Keep polling until the required CSVs reach Succeeded, or split “created” vs “installed” into separate assertions.

Also applies to: 4880-4894, 5023-5039, 5091-5107, 5159-5177, 5254-5270

🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.

In `@tests-extension/test/qe/specs/olmv0_nonallns.go` around lines 4826 - 4841,
The poll currently treats "Installing" as a passing end state causing false
positives; update the lambda(s) that call olmv0util.GetResource (variables
status1/status2) for the CSVs "etcdoperator.v0.9.2" and "ditto-operator.v0.1.1"
so they only consider "Succeeded" as success (remove the checks against
"Installing"), and fail/continue polling otherwise; apply the same change to the
other identical checks in this file (the other occurrences referenced) so
assertions that call exutil.AssertWaitPollNoErr wait until CSV status ==
"Succeeded" only.
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.

Inline comments:
In `@tests-extension/test/qe/specs/olmv0_nonallns.go`:
- Around line 4152-4160: The test races because CatalogSourceDescription.Create
(catsrc.Create) only applies the CatalogSource but doesn't wait for the catalog
pod/index to be READY before creating the Subscription; replace the unsafe
sub.Create(oc, itName, dr) call with the blocking variant
sub.CreateWithCheck(oc, itName, dr) (or otherwise wait for the CatalogSource to
be READY) so the subscription creation waits for the catalog to be usable and
won't miss the initial install plan; keep the existing defers (catsrc.Delete,
sub.Delete, sub.DeleteCSV, sub.Update) unchanged.

---

Outside diff comments:
In `@tests-extension/test/qe/specs/olmv0_nonallns.go`:
- Around line 4826-4841: The poll currently treats "Installing" as a passing end
state causing false positives; update the lambda(s) that call
olmv0util.GetResource (variables status1/status2) for the CSVs
"etcdoperator.v0.9.2" and "ditto-operator.v0.1.1" so they only consider
"Succeeded" as success (remove the checks against "Installing"), and
fail/continue polling otherwise; apply the same change to the other identical
checks in this file (the other occurrences referenced) so assertions that call
exutil.AssertWaitPollNoErr wait until CSV status == "Succeeded" only.

ℹ️ Review info
⚙️ Run configuration

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

Review profile: CHILL

Plan: Pro

Run ID: 056a2314-30e8-4b6e-b499-7d5c17f1e4e4

📥 Commits

Reviewing files that changed from the base of the PR and between bea777e and 604e4e1.

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

Comment thread tests-extension/test/qe/specs/olmv0_nonallns.go
@openshift-ci-robot
Copy link
Copy Markdown

openshift-ci-robot commented Mar 10, 2026

@Xia-Zhao-rh: This pull request references OCPQE-31752 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 sub-task to target the "4.22.0" version, but no target version was set.

Details

In response to this:

================================================
[1/8] Running test:
[sig-operator][Jira:OLM] OLMv0 within a namespace PolarionID:40529-[OTP][Skipped:Disconnected]OPERATOR_CONDITION_NAME should have correct value
================================================

✓ Test PASSED (320s)

================================================
[2/8] Running test:
[sig-operator][Jira:OLM] OLMv0 within a namespace PolarionID:47322-[OTP][Skipped:Disconnected]Arbitrary Constraints can be defined as bundle properties
================================================

✓ Test PASSED (349s)

================================================
[3/8] Running test:
[sig-operator][Jira:OLM] OLMv0 within a namespace PolarionID:47319-[OTP][Skipped:Disconnected]olm raised error when Arbitrary Compound Constraints is defined wrongly
================================================

✓ Test PASSED (255s)

================================================
[4/8] Running test:
[sig-operator][Jira:OLM] OLMv0 within a namespace PolarionID:47319-[OTP][Skipped:Disconnected]Arbitrary Compound Constraints with AND can be defined as bundle properties with less than
================================================

✓ Test PASSED (249s)

================================================
[5/8] Running test:
[sig-operator][Jira:OLM] OLMv0 within a namespace PolarionID:47319-[OTP][Skipped:Disconnected]Arbitrary Compound Constraints with AND can be defined as bundle properties with more than
================================================

✓ Test PASSED (247s)

================================================
[6/8] Running test:
[sig-operator][Jira:OLM] OLMv0 within a namespace PolarionID:47323-[OTP][Skipped:Disconnected]Arbitrary Compound Constraints with OR can be defined as bundle properties
================================================

✓ Test PASSED (300s)

================================================
[7/8] Running test:
[sig-operator][Jira:OLM] OLMv0 within a namespace PolarionID:47323-[OTP][Skipped:Disconnected]Arbitrary Compound Constraints with NOT can be defined as bundle properties
================================================

✓ Test PASSED (300s)

================================================
[8/8] Running test:
[sig-operator][Jira:OLM] OLMv0 within a namespace PolarionID:59380-PolarionID:68671-[OTP][Skipped:Disconnected]Upgrade should be success when there are multiple upgrade paths between channel entries
================================================

✓ Test PASSED (345s)

================================================
Test Execution Summary
================================================
Total Duration: 2367s
Tests Run:      8 / 8
Passed:         8
Failed:         0
Skipped:        0
================================================

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.

@Xia-Zhao-rh
Copy link
Copy Markdown
Contributor Author

/payload-job periodic-ci-openshift-operator-framework-olm-release-4.21-periodics-e2e-aws-ovn-extended-f1

@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci Bot commented Mar 10, 2026

@Xia-Zhao-rh: trigger 1 job(s) for the /payload-(with-prs|job|aggregate|job-with-prs|aggregate-with-prs) command

  • periodic-ci-openshift-operator-framework-olm-release-4.21-periodics-e2e-aws-ovn-extended-f1

See details on https://pr-payload-tests.ci.openshift.org/runs/ci/1f306db0-1c8d-11f1-8ae6-ee7b1d978cc0-0

@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci Bot commented Mar 10, 2026

@Xia-Zhao-rh: 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.

@Xia-Zhao-rh
Copy link
Copy Markdown
Contributor Author

/payload-job periodic-ci-openshift-operator-framework-olm-release-4.21-periodics-e2e-aws-ovn-extended-f1

@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci Bot commented Mar 11, 2026

@Xia-Zhao-rh: trigger 1 job(s) for the /payload-(with-prs|job|aggregate|job-with-prs|aggregate-with-prs) command

  • periodic-ci-openshift-operator-framework-olm-release-4.21-periodics-e2e-aws-ovn-extended-f1

See details on https://pr-payload-tests.ci.openshift.org/runs/ci/b594e320-1ce8-11f1-9800-7543fe8a665e-0

@Xia-Zhao-rh
Copy link
Copy Markdown
Contributor Author

/payload-job periodic-ci-openshift-operator-framework-olm-release-4.21-periodics-e2e-aws-ovn-extended-f1

@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci Bot commented Mar 11, 2026

@Xia-Zhao-rh: trigger 1 job(s) for the /payload-(with-prs|job|aggregate|job-with-prs|aggregate-with-prs) command

  • periodic-ci-openshift-operator-framework-olm-release-4.21-periodics-e2e-aws-ovn-extended-f1

See details on https://pr-payload-tests.ci.openshift.org/runs/ci/70c61e20-1d2a-11f1-9c31-03c5818acfbc-0

@Xia-Zhao-rh
Copy link
Copy Markdown
Contributor Author

Hi, @kuiwang02 @jianzhangbjz PTAL, thanks

@Xia-Zhao-rh
Copy link
Copy Markdown
Contributor Author

/verified by @Xia-Zhao-rh

@openshift-ci-robot openshift-ci-robot added the verified Signifies that the PR passed pre-merge verification criteria label Mar 12, 2026
@openshift-ci-robot
Copy link
Copy Markdown

@Xia-Zhao-rh: This PR has been marked as verified by @Xia-Zhao-rh.

Details

In response to this:

/verified by @Xia-Zhao-rh

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.

@kuiwang02
Copy link
Copy Markdown
Contributor

/lgtm

@openshift-ci openshift-ci Bot added the lgtm Indicates that a PR is ready to be merged. label Mar 12, 2026
@jianzhangbjz
Copy link
Copy Markdown
Contributor

/approve

@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci Bot commented Mar 12, 2026

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: jianzhangbjz, Xia-Zhao-rh

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 Mar 12, 2026
@openshift-merge-bot openshift-merge-bot Bot merged commit 5d5800c into openshift:main Mar 12, 2026
16 checks passed
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/valid-reference Indicates that this PR references a valid Jira ticket of any type. lgtm Indicates that a PR is ready to be merged. verified Signifies that the PR passed pre-merge verification criteria

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants