Skip to content

OCPQE-31108: add disconnected support with custom prow job for migrated qe cases #1155

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Merged
merged 1 commit into from
Nov 18, 2025
Merged

OCPQE-31108: add disconnected support with custom prow job for migrated qe cases #1155

merged 1 commit into from
Nov 18, 2025
+228 −30

Conversation

@kuiwang02
Copy link
Contributor

@kuiwang02 kuiwang02 commented Nov 17, 2025 •
edited by openshift-ci bot
Loading

/cc @jianzhangbjz @Xia-Zhao-rh @bandrade

if you expect your migrated case to support disc, follow this PR. thanks

Summary

Add disconnected environment support for migrated OLMv0 test cases

This PR implements the test-side changes for OCPQE-31108, enabling migrated QE test cases to run in both connected and disconnected OpenShift environments.

Related Issues

  • OCPQE-31108: Support OLMv0 Migrated test cases on Disconnected env (Test Cases)
  • OCPQE-31109: Support OLMv0 Migrated test cases on Disconnected env (CI Infrastructure)
  • OCPQE-31104: Parent epic for disconnected environment support

Testing

INFO[0193] Found 0 must-gather tests                    
started: 0/1/12 "[sig-operator][Jira:OLM] OLMv0 within a namespace PolarionID:25760-[OTP]Operator upgrades does not fail after change the channel"

started: 0/2/12 "[sig-operator][Jira:OLM] OLMv0 within a namespace PolarionID:27683-[OTP]InstallPlans can install from extracted bundles"

started: 0/3/12 "[sig-operator][Jira:OLM] OLMv0 within a namespace PolarionID:30762-[OTP]installs bundles with v1 CRDs"

started: 0/4/12 "[sig-operator][Jira:OLM] OLMv0 within a namespace PolarionID:23170-[OTP]API labels should be hash"

started: 0/5/12 "[sig-operator][Jira:OLM] OLMv0 within all namespace PolarionID:21484-PolarionID:21532-[OTP]watch special or all namespace by operator group"

started: 0/6/12 "[sig-operator][Jira:OLM] OLMv0 within a namespace PolarionID:29723-[OTP]As cluster admin find abnormal status condition via components of operator resource"

started: 0/7/12 "[sig-operator][Jira:OLM] OLMv0 within a namespace PolarionID:20979-[OTP]only one IP is generated"

started: 0/8/12 "[sig-operator][Jira:OLM] OLMv0 within a namespace PolarionID:24513-[OTP]Operator config support env only"


passed: (2m49s) 2025-11-17T06:32:37 "[sig-operator][Jira:OLM] OLMv0 within a namespace PolarionID:25760-[OTP]Operator upgrades does not fail after change the channel"


passed: (2m58s) 2025-11-17T06:32:46 "[sig-operator][Jira:OLM] OLMv0 within a namespace PolarionID:29723-[OTP]As cluster admin find abnormal status condition via components of operator resource"


passed: (2m59s) 2025-11-17T06:32:47 "[sig-operator][Jira:OLM] OLMv0 within a namespace PolarionID:30762-[OTP]installs bundles with v1 CRDs"


passed: (3m5s) 2025-11-17T06:32:53 "[sig-operator][Jira:OLM] OLMv0 within all namespace PolarionID:21484-PolarionID:21532-[OTP]watch special or all namespace by operator group"


passed: (3m21s) 2025-11-17T06:33:09 "[sig-operator][Jira:OLM] OLMv0 within a namespace PolarionID:23170-[OTP]API labels should be hash"


passed: (3m29s) 2025-11-17T06:33:17 "[sig-operator][Jira:OLM] OLMv0 within a namespace PolarionID:24513-[OTP]Operator config support env only"


passed: (3m29s) 2025-11-17T06:33:17 "[sig-operator][Jira:OLM] OLMv0 within a namespace PolarionID:27683-[OTP]InstallPlans can install from extracted bundles"


passed: (3m39s) 2025-11-17T06:33:27 "[sig-operator][Jira:OLM] OLMv0 within a namespace PolarionID:20979-[OTP]only one IP is generated"

started: 0/9/12 "[sig-operator][Jira:OLM] OLMv0 within all namespace PolarionID:21418-PolarionID:25679-[OTP]Cluster resource created and deleted correctly [Serial]"


passed: (2m16s) 2025-11-17T06:35:46 "[sig-operator][Jira:OLM] OLMv0 within all namespace PolarionID:21418-PolarionID:25679-[OTP]Cluster resource created and deleted correctly [Serial]"

started: 0/10/12 "[sig-operator][Jira:OLM] OLMv0 with multi ns PolarionID:71119-[OTP]pod does not start for installing operator of multi-ns mode when og is in one of the ns[Serial]"


passed: (4m58s) 2025-11-17T06:40:47 "[sig-operator][Jira:OLM] OLMv0 with multi ns PolarionID:71119-[OTP]pod does not start for installing operator of multi-ns mode when og is in one of the ns[Serial]"

started: 0/11/12 "[sig-operator][Jira:OLM] OLMv0 within a namespace PolarionID:39897-[OTP]operator objects should not be recreated after all other associated resources have been deleted[Serial]"


passed: (2m44s) 2025-11-17T06:43:34 "[sig-operator][Jira:OLM] OLMv0 within a namespace PolarionID:39897-[OTP]operator objects should not be recreated after all other associated resources have been deleted[Serial]"

started: 0/12/12 "[sig-operator][Jira:OLM] OLMv0 within all namespace PolarionID:24906-[OTP]Operators requesting cluster-scoped permission can trigger kube GC bug[Serial]"


passed: (2m19s) 2025-11-17T06:45:55 "[sig-operator][Jira:OLM] OLMv0 within all namespace PolarionID:24906-[OTP]Operators requesting cluster-scoped permission can trigger kube GC bug[Serial]"

Shutting down the monitor
Collecting data.
INFO[1164] Starting CollectData for all monitor tests   
INFO[1164]   Starting CollectData for [Monitor:watch-namespaces][Jira:"Test Framework"] monitor test watch-namespaces collection 
INFO[1164]   Finished CollectData for [Monitor:watch-namespaces][Jira:"Test Framework"] monitor test watch-namespaces collection 
INFO[1164] Finished CollectData for all monitor tests   
Computing intervals.
Evaluating tests.
Cleaning up.
INFO[1164] beginning cleanup                             monitorTest=watch-namespaces
Serializing results.
Writing to storage.
  m.startTime = 2025-11-17 14:29:44.700623 +0800 CST m=+193.427571209
  m.stopTime  = 2025-11-17 14:45:55.902426 +0800 CST m=+1164.584075709
Processing monitorTest: watch-namespaces
  finalIntervals size = 24
  first interval time: From = 2025-11-17 14:29:44.708813 +0800 CST m=+193.435760917; To = 2025-11-17 14:29:44.708813 +0800 CST m=+193.435760917
  last interval time: From = 2025-11-17 14:45:55.901903 +0800 CST m=+1164.583552459; To = 2025-11-17 14:45:55.901903 +0800 CST m=+1164.583552459
Writing junits.
Writing JUnit report to e2e-monitor-tests__20251117-062643.xml
12 pass, 0 flaky, 0 skip (19m12s)

Assisted-by: Claude Code

@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Nov 17, 2025
@openshift-ci-robot
Copy link

openshift-ci-robot commented Nov 17, 2025 •
edited by openshift-ci bot
Loading

@kuiwang02: This pull request references OCPQE-31108 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.21.0" version, but no target version was set.

In response to this:

/cc @jianzhangbjz @Xia-Zhao-rh @bandrade

if you expect your migrated case to support disc, follow this PR. thanks

Summary

Add disconnected environment support for migrated OLMv0 test cases

This PR implements the test-side changes for OCPQE-31108, enabling migrated QE test cases to run in both connected and disconnected OpenShift environments.

Related Issues

  • OCPQE-31108: Support OLMv0 Migrated test cases on Disconnected env (Test Cases)
  • OCPQE-31109: Support OLMv0 Migrated test cases on Disconnected env (CI Infrastructure)
  • OCPQE-31104: Parent epic for disconnected environment support

Testing

INFO[0193] Found 0 must-gather tests                    
started: 0/1/12 "[sig-operator][Jira:OLM] OLMv0 within a namespace PolarionID:25760-[OTP]Operator upgrades does not fail after change the channel"

started: 0/2/12 "[sig-operator][Jira:OLM] OLMv0 within a namespace PolarionID:27683-[OTP]InstallPlans can install from extracted bundles"

started: 0/3/12 "[sig-operator][Jira:OLM] OLMv0 within a namespace PolarionID:30762-[OTP]installs bundles with v1 CRDs"

started: 0/4/12 "[sig-operator][Jira:OLM] OLMv0 within a namespace PolarionID:23170-[OTP]API labels should be hash"

started: 0/5/12 "[sig-operator][Jira:OLM] OLMv0 within all namespace PolarionID:21484-PolarionID:21532-[OTP]watch special or all namespace by operator group"

started: 0/6/12 "[sig-operator][Jira:OLM] OLMv0 within a namespace PolarionID:29723-[OTP]As cluster admin find abnormal status condition via components of operator resource"

started: 0/7/12 "[sig-operator][Jira:OLM] OLMv0 within a namespace PolarionID:20979-[OTP]only one IP is generated"

started: 0/8/12 "[sig-operator][Jira:OLM] OLMv0 within a namespace PolarionID:24513-[OTP]Operator config support env only"


passed: (2m49s) 2025-11-17T06:32:37 "[sig-operator][Jira:OLM] OLMv0 within a namespace PolarionID:25760-[OTP]Operator upgrades does not fail after change the channel"


passed: (2m58s) 2025-11-17T06:32:46 "[sig-operator][Jira:OLM] OLMv0 within a namespace PolarionID:29723-[OTP]As cluster admin find abnormal status condition via components of operator resource"


passed: (2m59s) 2025-11-17T06:32:47 "[sig-operator][Jira:OLM] OLMv0 within a namespace PolarionID:30762-[OTP]installs bundles with v1 CRDs"


passed: (3m5s) 2025-11-17T06:32:53 "[sig-operator][Jira:OLM] OLMv0 within all namespace PolarionID:21484-PolarionID:21532-[OTP]watch special or all namespace by operator group"


passed: (3m21s) 2025-11-17T06:33:09 "[sig-operator][Jira:OLM] OLMv0 within a namespace PolarionID:23170-[OTP]API labels should be hash"


passed: (3m29s) 2025-11-17T06:33:17 "[sig-operator][Jira:OLM] OLMv0 within a namespace PolarionID:24513-[OTP]Operator config support env only"


passed: (3m29s) 2025-11-17T06:33:17 "[sig-operator][Jira:OLM] OLMv0 within a namespace PolarionID:27683-[OTP]InstallPlans can install from extracted bundles"


passed: (3m39s) 2025-11-17T06:33:27 "[sig-operator][Jira:OLM] OLMv0 within a namespace PolarionID:20979-[OTP]only one IP is generated"

started: 0/9/12 "[sig-operator][Jira:OLM] OLMv0 within all namespace PolarionID:21418-PolarionID:25679-[OTP]Cluster resource created and deleted correctly [Serial]"


passed: (2m16s) 2025-11-17T06:35:46 "[sig-operator][Jira:OLM] OLMv0 within all namespace PolarionID:21418-PolarionID:25679-[OTP]Cluster resource created and deleted correctly [Serial]"

started: 0/10/12 "[sig-operator][Jira:OLM] OLMv0 with multi ns PolarionID:71119-[OTP]pod does not start for installing operator of multi-ns mode when og is in one of the ns[Serial]"


passed: (4m58s) 2025-11-17T06:40:47 "[sig-operator][Jira:OLM] OLMv0 with multi ns PolarionID:71119-[OTP]pod does not start for installing operator of multi-ns mode when og is in one of the ns[Serial]"

started: 0/11/12 "[sig-operator][Jira:OLM] OLMv0 within a namespace PolarionID:39897-[OTP]operator objects should not be recreated after all other associated resources have been deleted[Serial]"


passed: (2m44s) 2025-11-17T06:43:34 "[sig-operator][Jira:OLM] OLMv0 within a namespace PolarionID:39897-[OTP]operator objects should not be recreated after all other associated resources have been deleted[Serial]"

started: 0/12/12 "[sig-operator][Jira:OLM] OLMv0 within all namespace PolarionID:24906-[OTP]Operators requesting cluster-scoped permission can trigger kube GC bug[Serial]"


passed: (2m19s) 2025-11-17T06:45:55 "[sig-operator][Jira:OLM] OLMv0 within all namespace PolarionID:24906-[OTP]Operators requesting cluster-scoped permission can trigger kube GC bug[Serial]"

Shutting down the monitor
Collecting data.
INFO[1164] Starting CollectData for all monitor tests   
INFO[1164]   Starting CollectData for [Monitor:watch-namespaces][Jira:"Test Framework"] monitor test watch-namespaces collection 
INFO[1164]   Finished CollectData for [Monitor:watch-namespaces][Jira:"Test Framework"] monitor test watch-namespaces collection 
INFO[1164] Finished CollectData for all monitor tests   
Computing intervals.
Evaluating tests.
Cleaning up.
INFO[1164] beginning cleanup                             monitorTest=watch-namespaces
Serializing results.
Writing to storage.
 m.startTime = 2025-11-17 14:29:44.700623 +0800 CST m=+193.427571209
 m.stopTime  = 2025-11-17 14:45:55.902426 +0800 CST m=+1164.584075709
Processing monitorTest: watch-namespaces
 finalIntervals size = 24
 first interval time: From = 2025-11-17 14:29:44.708813 +0800 CST m=+193.435760917; To = 2025-11-17 14:29:44.708813 +0800 CST m=+193.435760917
 last interval time: From = 2025-11-17 14:45:55.901903 +0800 CST m=+1164.583552459; To = 2025-11-17 14:45:55.901903 +0800 CST m=+1164.583552459
Writing junits.
Writing JUnit report to e2e-monitor-tests__20251117-062643.xml
12 pass, 0 flaky, 0 skip (19m12s)

Assisted-by: Claude Code

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
Contributor Author

kuiwang02 commented Nov 17, 2025

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

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Nov 17, 2025

@kuiwang02: 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/7d133bf0-c383-11f0-9cf0-fca0bbea36d6-0

@tmshort
Copy link
Contributor

tmshort commented Nov 17, 2025

/retest-required

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Nov 17, 2025

@kuiwang02: all tests passed!

Full PR test history. Your PR dashboard.

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.

@kuiwang02
Copy link
Contributor Author

kuiwang02 commented Nov 18, 2025

/verified by @kuiwang02

@openshift-ci-robot openshift-ci-robot added the verified Signifies that the PR passed pre-merge verification criteria label Nov 18, 2025
@openshift-ci-robot
Copy link

openshift-ci-robot commented Nov 18, 2025

@kuiwang02: This PR has been marked as verified by @kuiwang02.

In response to this:

/verified by @kuiwang02

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.

@jianzhangbjz
Copy link
Contributor

jianzhangbjz commented Nov 18, 2025

/approve
/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Nov 18, 2025
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Nov 18, 2025

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: jianzhangbjz, kuiwang02

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

The pull request process is described here

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 Nov 18, 2025
@openshift-merge-bot openshift-merge-bot bot merged commit c634723 into openshift:main Nov 18, 2025
14 checks passed
@kuiwang02 kuiwang02 deleted the discqe branch November 18, 2025 00:44
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@bandrade bandrade Awaiting requested review from bandrade

@jianzhangbjz jianzhangbjz Awaiting requested review from jianzhangbjz

@Xia-Zhao-rh Xia-Zhao-rh Awaiting requested review from Xia-Zhao-rh

Assignees

@jianzhangbjz jianzhangbjz

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

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

4 participants

@kuiwang02 @openshift-ci-robot @tmshort @jianzhangbjz