Skip to content

Conversation

@DavidHurta
Copy link
Contributor

@DavidHurta DavidHurta commented Sep 29, 2025

Register the cluster version operator (CVO) tests extension in the origin's extension registry.


Testing

Confirming info outputs correct API version, metadata

$ ./_output/linux/amd64/cluster-version-operator-tests info
{
    "apiVersion": "v1.0",
    "source": {
        "commit": "420e6d07",
        "build_date": "2025-11-03T13:51:50Z",
        "git_tree_state": "clean"
    },
    "component": {
        "product": "openshift",
        "type": "payload",
        "name": "cluster-version-operator"
    },
    "suites": [
        {
            "name": "openshift/cluster-version-operator/conformance/parallel",
            "parents": [
                "openshift/conformance/parallel"
            ],
            "qualifiers": [
                "(source == \"openshift:payload:cluster-version-operator\") \u0026\u0026 (!(name.contains(\"[Serial]\") || name.contains(\"[Slow]\")))"
            ]
        },
        {
            "name": "openshift/cluster-version-operator/conformance/serial",
            "parents": [
                "openshift/conformance/serial"
            ],
            "qualifiers": [
                "(source == \"openshift:payload:cluster-version-operator\") \u0026\u0026 (name.contains(\"[Serial]\"))"
            ]
        }
    ],
    "images": null
}

Confirming list outputs tests properly filtered by environment

$ ./_output/linux/amd64/cluster-version-operator-tests list
[
  {
    "name": "[Jira:Cluster Version Operator] cluster-version-operator-tests should support passing tests",
    "labels": {},
    "resources": {
      "isolation": {}
    },
    "source": "openshift:payload:cluster-version-operator",
    "lifecycle": "blocking",
    "environmentSelector": {}
  }
]

Confirming run-suite functions and produces valid JSON test results

$ ./_output/linux/amd64/cluster-version-operator-tests run-suite openshift/cluster-version-operator/conformance/parallel
  Running Suite:  - /home/dhurta/GolandProjects/cluster-version-operator
  ======================================================================
  Random Seed: 1762178101 - will randomize all specs

  Will run 1 of 1 specs
  ------------------------------
  [Jira:Cluster Version Operator] cluster-version-operator-tests should support passing tests
  /home/dhurta/GolandProjects/cluster-version-operator/test/cvo/cvo.go:9
  • [0.000 seconds]
  ------------------------------

  Ran 1 of 1 Specs in 0.000 seconds
  SUCCESS! -- 1 Passed | 0 Failed | 0 Pending | 0 Skipped
[
  {
    "name": "[Jira:Cluster Version Operator] cluster-version-operator-tests should support passing tests",
    "lifecycle": "blocking",
    "duration": 0,
    "startTime": "2025-11-03 13:55:01.681724 UTC",
    "endTime": "2025-11-03 13:55:01.682308 UTC",
    "result": "passed",
    "output": ""
  }
]
$ ./_output/linux/amd64/cluster-version-operator-tests run-suite openshift/cluster-version-operator/conformance/serial
null

Confirming run-test functions and produces valid JSON test results

$ ./_output/linux/amd64/cluster-version-operator-tests run-test -n "[Jira:Cluster Version Operator] cluster-version-operator-tests should support passing tests"
  Running Suite:  - /home/dhurta/GolandProjects/cluster-version-operator
  ======================================================================
  Random Seed: 1762178152 - will randomize all specs

  Will run 1 of 1 specs
  ------------------------------
  [Jira:Cluster Version Operator] cluster-version-operator-tests should support passing tests
  /home/dhurta/GolandProjects/cluster-version-operator/test/cvo/cvo.go:9
  • [0.000 seconds]
  ------------------------------

  Ran 1 of 1 Specs in 0.000 seconds
  SUCCESS! -- 1 Passed | 0 Failed | 0 Pending | 0 Skipped
[
  {
    "name": "[Jira:Cluster Version Operator] cluster-version-operator-tests should support passing tests",
    "lifecycle": "blocking",
    "duration": 0,
    "startTime": "2025-11-03 13:55:52.869586 UTC",
    "endTime": "2025-11-03 13:55:52.870196 UTC",
    "result": "passed",
    "output": ""
  }
]

Checking an e2e run for the sole sanity test:

The sole CVO test [Jira:Cluster Version Operator] cluster-version-operator-tests should support passing tests is visible in a pull-ci-openshift-origin-main-e2e-gcp-ovn run.

@openshift-ci openshift-ci bot added the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Sep 29, 2025
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Sep 29, 2025

Skipping CI for Draft Pull Request.
If you want CI signal for your change, please convert it to an actual PR.
You can still manually trigger a test run with /test all

@DavidHurta
Copy link
Contributor Author

/testwith openshift/cluster-version-operator/main/e2e-agnostic-ovn openshift/cluster-version-operator#1236

@DavidHurta DavidHurta changed the title WIP: Add CVO test extension OTA-1585: WIP: Add CVO test extension Sep 29, 2025
@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Sep 29, 2025
@openshift-ci-robot
Copy link

openshift-ci-robot commented Sep 29, 2025

@DavidHurta: This pull request references OTA-1585 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 "4.21.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.

@DavidHurta
Copy link
Contributor Author

/testwith openshift/cluster-version-operator/main/e2e-agnostic-ovn openshift/cluster-version-operator#1236 openshift/cluster-version-operator#1238

@DavidHurta
Copy link
Contributor Author

/testwith openshift/cluster-version-operator/main/e2e-agnostic-ovn openshift/cluster-version-operator#1236 openshift/cluster-version-operator#1238

7 similar comments
@DavidHurta
Copy link
Contributor Author

/testwith openshift/cluster-version-operator/main/e2e-agnostic-ovn openshift/cluster-version-operator#1236 openshift/cluster-version-operator#1238

@DavidHurta
Copy link
Contributor Author

/testwith openshift/cluster-version-operator/main/e2e-agnostic-ovn openshift/cluster-version-operator#1236 openshift/cluster-version-operator#1238

@DavidHurta
Copy link
Contributor Author

/testwith openshift/cluster-version-operator/main/e2e-agnostic-ovn openshift/cluster-version-operator#1236 openshift/cluster-version-operator#1238

@DavidHurta
Copy link
Contributor Author

/testwith openshift/cluster-version-operator/main/e2e-agnostic-ovn openshift/cluster-version-operator#1236 openshift/cluster-version-operator#1238

@DavidHurta
Copy link
Contributor Author

/testwith openshift/cluster-version-operator/main/e2e-agnostic-ovn openshift/cluster-version-operator#1236 openshift/cluster-version-operator#1238

@DavidHurta
Copy link
Contributor Author

/testwith openshift/cluster-version-operator/main/e2e-agnostic-ovn openshift/cluster-version-operator#1236 openshift/cluster-version-operator#1238

@DavidHurta
Copy link
Contributor Author

/testwith openshift/cluster-version-operator/main/e2e-agnostic-ovn openshift/cluster-version-operator#1236 openshift/cluster-version-operator#1238

@DavidHurta
Copy link
Contributor Author

/testwith openshift/cluster-version-operator/main/e2e-agnostic-ovn

@DavidHurta
Copy link
Contributor Author

/test ?

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Nov 2, 2025

@DavidHurta: The following commands are available to trigger required jobs:

/test e2e-aws-csi
/test e2e-aws-jenkins
/test e2e-aws-ovn-fips
/test e2e-aws-ovn-image-registry
/test e2e-aws-ovn-microshift
/test e2e-aws-ovn-microshift-serial
/test e2e-aws-ovn-serial-1of2
/test e2e-aws-ovn-serial-2of2
/test e2e-gcp-csi
/test e2e-gcp-ovn
/test e2e-gcp-ovn-builds
/test e2e-gcp-ovn-image-ecosystem
/test e2e-gcp-ovn-upgrade
/test e2e-metal-ipi-ovn-ipv6
/test e2e-vsphere-ovn
/test e2e-vsphere-ovn-upi
/test go-verify-deps
/test images
/test lint
/test okd-scos-images
/test unit
/test verify
/test verify-deps

The following commands are available to trigger optional jobs:

/test e2e-agnostic-ovn-cmd
/test e2e-aws-disruptive
/test e2e-aws-etcd-certrotation
/test e2e-aws-etcd-recovery
/test e2e-aws-ovn
/test e2e-aws-ovn-cgroupsv2
/test e2e-aws-ovn-edge-zones
/test e2e-aws-ovn-etcd-scaling
/test e2e-aws-ovn-kube-apiserver-rollout
/test e2e-aws-ovn-kubevirt
/test e2e-aws-ovn-serial-fast
/test e2e-aws-ovn-serial-ipsec
/test e2e-aws-ovn-serial-publicnet-1of2
/test e2e-aws-ovn-serial-publicnet-2of2
/test e2e-aws-ovn-single-node
/test e2e-aws-ovn-single-node-serial
/test e2e-aws-ovn-single-node-techpreview
/test e2e-aws-ovn-single-node-techpreview-serial
/test e2e-aws-ovn-single-node-upgrade
/test e2e-aws-ovn-upgrade
/test e2e-aws-ovn-upgrade-rollback
/test e2e-aws-ovn-upi
/test e2e-aws-proxy
/test e2e-azure
/test e2e-azure-ovn-etcd-scaling
/test e2e-azure-ovn-upgrade
/test e2e-baremetalds-kubevirt
/test e2e-external-aws
/test e2e-external-aws-ccm
/test e2e-external-vsphere-ccm
/test e2e-gcp-disruptive
/test e2e-gcp-fips-serial-1of2
/test e2e-gcp-fips-serial-2of2
/test e2e-gcp-ovn-etcd-scaling
/test e2e-gcp-ovn-rt-upgrade
/test e2e-gcp-ovn-techpreview
/test e2e-gcp-ovn-techpreview-serial-1of2
/test e2e-gcp-ovn-techpreview-serial-2of2
/test e2e-gcp-ovn-usernamespace
/test e2e-hypershift-conformance
/test e2e-metal-ipi-ovn
/test e2e-metal-ipi-ovn-bgp-virt-dualstack
/test e2e-metal-ipi-ovn-bgp-virt-dualstack-techpreview
/test e2e-metal-ipi-ovn-dualstack
/test e2e-metal-ipi-ovn-dualstack-bgp
/test e2e-metal-ipi-ovn-dualstack-bgp-local-gw
/test e2e-metal-ipi-ovn-dualstack-local-gateway
/test e2e-metal-ipi-ovn-kube-apiserver-rollout
/test e2e-metal-ipi-serial-1of2
/test e2e-metal-ipi-serial-2of2
/test e2e-metal-ipi-serial-ovn-ipv6-1of2
/test e2e-metal-ipi-serial-ovn-ipv6-2of2
/test e2e-metal-ipi-virtualmedia
/test e2e-metal-ovn-single-node-live-iso
/test e2e-metal-ovn-single-node-with-worker-live-iso
/test e2e-metal-ovn-two-node-arbiter
/test e2e-metal-ovn-two-node-fencing
/test e2e-openstack-ovn
/test e2e-openstack-serial
/test e2e-vsphere-ovn-dualstack-primaryv6
/test e2e-vsphere-ovn-etcd-scaling
/test okd-scos-e2e-aws-ovn

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

pull-ci-openshift-origin-main-e2e-aws-csi
pull-ci-openshift-origin-main-e2e-aws-ovn-fips
pull-ci-openshift-origin-main-e2e-aws-ovn-microshift
pull-ci-openshift-origin-main-e2e-aws-ovn-microshift-serial
pull-ci-openshift-origin-main-e2e-aws-ovn-serial-1of2
pull-ci-openshift-origin-main-e2e-aws-ovn-serial-2of2
pull-ci-openshift-origin-main-e2e-gcp-csi
pull-ci-openshift-origin-main-e2e-gcp-ovn
pull-ci-openshift-origin-main-e2e-gcp-ovn-upgrade
pull-ci-openshift-origin-main-e2e-metal-ipi-ovn-ipv6
pull-ci-openshift-origin-main-e2e-vsphere-ovn
pull-ci-openshift-origin-main-e2e-vsphere-ovn-upi
pull-ci-openshift-origin-main-go-verify-deps
pull-ci-openshift-origin-main-images
pull-ci-openshift-origin-main-lint
pull-ci-openshift-origin-main-okd-scos-images
pull-ci-openshift-origin-main-unit
pull-ci-openshift-origin-main-verify
pull-ci-openshift-origin-main-verify-deps
Details

In response to this:

/test ?

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.

@DavidHurta
Copy link
Contributor Author

/test pull-ci-openshift-origin-main-e2e-gcp-ovn

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Nov 2, 2025

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

/test e2e-aws-csi
/test e2e-aws-jenkins
/test e2e-aws-ovn-fips
/test e2e-aws-ovn-image-registry
/test e2e-aws-ovn-microshift
/test e2e-aws-ovn-microshift-serial
/test e2e-aws-ovn-serial-1of2
/test e2e-aws-ovn-serial-2of2
/test e2e-gcp-csi
/test e2e-gcp-ovn
/test e2e-gcp-ovn-builds
/test e2e-gcp-ovn-image-ecosystem
/test e2e-gcp-ovn-upgrade
/test e2e-metal-ipi-ovn-ipv6
/test e2e-vsphere-ovn
/test e2e-vsphere-ovn-upi
/test go-verify-deps
/test images
/test lint
/test okd-scos-images
/test unit
/test verify
/test verify-deps

The following commands are available to trigger optional jobs:

/test e2e-agnostic-ovn-cmd
/test e2e-aws-disruptive
/test e2e-aws-etcd-certrotation
/test e2e-aws-etcd-recovery
/test e2e-aws-ovn
/test e2e-aws-ovn-cgroupsv2
/test e2e-aws-ovn-edge-zones
/test e2e-aws-ovn-etcd-scaling
/test e2e-aws-ovn-kube-apiserver-rollout
/test e2e-aws-ovn-kubevirt
/test e2e-aws-ovn-serial-fast
/test e2e-aws-ovn-serial-ipsec
/test e2e-aws-ovn-serial-publicnet-1of2
/test e2e-aws-ovn-serial-publicnet-2of2
/test e2e-aws-ovn-single-node
/test e2e-aws-ovn-single-node-serial
/test e2e-aws-ovn-single-node-techpreview
/test e2e-aws-ovn-single-node-techpreview-serial
/test e2e-aws-ovn-single-node-upgrade
/test e2e-aws-ovn-upgrade
/test e2e-aws-ovn-upgrade-rollback
/test e2e-aws-ovn-upi
/test e2e-aws-proxy
/test e2e-azure
/test e2e-azure-ovn-etcd-scaling
/test e2e-azure-ovn-upgrade
/test e2e-baremetalds-kubevirt
/test e2e-external-aws
/test e2e-external-aws-ccm
/test e2e-external-vsphere-ccm
/test e2e-gcp-disruptive
/test e2e-gcp-fips-serial-1of2
/test e2e-gcp-fips-serial-2of2
/test e2e-gcp-ovn-etcd-scaling
/test e2e-gcp-ovn-rt-upgrade
/test e2e-gcp-ovn-techpreview
/test e2e-gcp-ovn-techpreview-serial-1of2
/test e2e-gcp-ovn-techpreview-serial-2of2
/test e2e-gcp-ovn-usernamespace
/test e2e-hypershift-conformance
/test e2e-metal-ipi-ovn
/test e2e-metal-ipi-ovn-bgp-virt-dualstack
/test e2e-metal-ipi-ovn-bgp-virt-dualstack-techpreview
/test e2e-metal-ipi-ovn-dualstack
/test e2e-metal-ipi-ovn-dualstack-bgp
/test e2e-metal-ipi-ovn-dualstack-bgp-local-gw
/test e2e-metal-ipi-ovn-dualstack-local-gateway
/test e2e-metal-ipi-ovn-kube-apiserver-rollout
/test e2e-metal-ipi-serial-1of2
/test e2e-metal-ipi-serial-2of2
/test e2e-metal-ipi-serial-ovn-ipv6-1of2
/test e2e-metal-ipi-serial-ovn-ipv6-2of2
/test e2e-metal-ipi-virtualmedia
/test e2e-metal-ovn-single-node-live-iso
/test e2e-metal-ovn-single-node-with-worker-live-iso
/test e2e-metal-ovn-two-node-arbiter
/test e2e-metal-ovn-two-node-fencing
/test e2e-openstack-ovn
/test e2e-openstack-serial
/test e2e-vsphere-ovn-dualstack-primaryv6
/test e2e-vsphere-ovn-etcd-scaling
/test okd-scos-e2e-aws-ovn

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

pull-ci-openshift-origin-main-e2e-aws-csi
pull-ci-openshift-origin-main-e2e-aws-ovn-fips
pull-ci-openshift-origin-main-e2e-aws-ovn-microshift
pull-ci-openshift-origin-main-e2e-aws-ovn-microshift-serial
pull-ci-openshift-origin-main-e2e-aws-ovn-serial-1of2
pull-ci-openshift-origin-main-e2e-aws-ovn-serial-2of2
pull-ci-openshift-origin-main-e2e-gcp-csi
pull-ci-openshift-origin-main-e2e-gcp-ovn
pull-ci-openshift-origin-main-e2e-gcp-ovn-upgrade
pull-ci-openshift-origin-main-e2e-metal-ipi-ovn-ipv6
pull-ci-openshift-origin-main-e2e-vsphere-ovn
pull-ci-openshift-origin-main-e2e-vsphere-ovn-upi
pull-ci-openshift-origin-main-go-verify-deps
pull-ci-openshift-origin-main-images
pull-ci-openshift-origin-main-lint
pull-ci-openshift-origin-main-okd-scos-images
pull-ci-openshift-origin-main-unit
pull-ci-openshift-origin-main-verify
pull-ci-openshift-origin-main-verify-deps
Details

In response to this:

/test pull-ci-openshift-origin-main-e2e-gcp-ovn

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.

@DavidHurta
Copy link
Contributor Author

/test e2e-aws-ovn

@DavidHurta DavidHurta force-pushed the add-cvo-test-extension branch from c327f8e to 281c514 Compare November 3, 2025 13:20
@DavidHurta
Copy link
Contributor Author

/test all

@DavidHurta DavidHurta changed the title OTA-1585: WIP: Add CVO test extension OTA-1585: Register the CVO tests extension Nov 3, 2025
@openshift-ci-robot
Copy link

openshift-ci-robot commented Nov 3, 2025

@DavidHurta: This pull request references OTA-1585 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 "4.21.0" version, but no target version was set.

Details

In response to this:

Register the cluster version operator (CVO) tests extension in the origin's extension registry.


Testing

Confirming info outputs correct API version, metadata

$ ./_output/linux/amd64/cluster-version-operator-tests info
{
   "apiVersion": "v1.0",
   "source": {
       "commit": "420e6d07",
       "build_date": "2025-11-03T13:51:50Z",
       "git_tree_state": "clean"
   },
   "component": {
       "product": "openshift",
       "type": "payload",
       "name": "cluster-version-operator"
   },
   "suites": [
       {
           "name": "openshift/cluster-version-operator/conformance/parallel",
           "parents": [
               "openshift/conformance/parallel"
           ],
           "qualifiers": [
               "(source == \"openshift:payload:cluster-version-operator\") \u0026\u0026 (!(name.contains(\"[Serial]\") || name.contains(\"[Slow]\")))"
           ]
       },
       {
           "name": "openshift/cluster-version-operator/conformance/serial",
           "parents": [
               "openshift/conformance/serial"
           ],
           "qualifiers": [
               "(source == \"openshift:payload:cluster-version-operator\") \u0026\u0026 (name.contains(\"[Serial]\"))"
           ]
       }
   ],
   "images": null
}

Confirming list outputs tests properly filtered by environment

$ ./_output/linux/amd64/cluster-version-operator-tests list
[
 {
   "name": "[Jira:Cluster Version Operator] cluster-version-operator-tests should support passing tests",
   "labels": {},
   "resources": {
     "isolation": {}
   },
   "source": "openshift:payload:cluster-version-operator",
   "lifecycle": "blocking",
   "environmentSelector": {}
 }
]

Confirming run-suite functions and produces valid JSON test results

$ ./_output/linux/amd64/cluster-version-operator-tests run-suite openshift/cluster-version-operator/conformance/parallel
 Running Suite:  - /home/dhurta/GolandProjects/cluster-version-operator
 ======================================================================
 Random Seed: 1762178101 - will randomize all specs

 Will run 1 of 1 specs
 ------------------------------
 [Jira:Cluster Version Operator] cluster-version-operator-tests should support passing tests
 /home/dhurta/GolandProjects/cluster-version-operator/test/cvo/cvo.go:9
 • [0.000 seconds]
 ------------------------------

 Ran 1 of 1 Specs in 0.000 seconds
 SUCCESS! -- 1 Passed | 0 Failed | 0 Pending | 0 Skipped
[
 {
   "name": "[Jira:Cluster Version Operator] cluster-version-operator-tests should support passing tests",
   "lifecycle": "blocking",
   "duration": 0,
   "startTime": "2025-11-03 13:55:01.681724 UTC",
   "endTime": "2025-11-03 13:55:01.682308 UTC",
   "result": "passed",
   "output": ""
 }
]
$ ./_output/linux/amd64/cluster-version-operator-tests run-suite openshift/cluster-version-operator/conformance/serial
null

Confirming run-test functions and produces valid JSON test results

$ ./_output/linux/amd64/cluster-version-operator-tests run-test -n "[Jira:Cluster Version Operator] cluster-version-operator-tests should support passing tests"
 Running Suite:  - /home/dhurta/GolandProjects/cluster-version-operator
 ======================================================================
 Random Seed: 1762178152 - will randomize all specs

 Will run 1 of 1 specs
 ------------------------------
 [Jira:Cluster Version Operator] cluster-version-operator-tests should support passing tests
 /home/dhurta/GolandProjects/cluster-version-operator/test/cvo/cvo.go:9
 • [0.000 seconds]
 ------------------------------

 Ran 1 of 1 Specs in 0.000 seconds
 SUCCESS! -- 1 Passed | 0 Failed | 0 Pending | 0 Skipped
[
 {
   "name": "[Jira:Cluster Version Operator] cluster-version-operator-tests should support passing tests",
   "lifecycle": "blocking",
   "duration": 0,
   "startTime": "2025-11-03 13:55:52.869586 UTC",
   "endTime": "2025-11-03 13:55:52.870196 UTC",
   "result": "passed",
   "output": ""
 }
]

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

openshift-ci-robot commented Nov 3, 2025

@DavidHurta: This pull request references OTA-1585 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 "4.21.0" version, but no target version was set.

Details

In response to this:

Register the cluster version operator (CVO) tests extension in the origin's extension registry.


Testing

Confirming info outputs correct API version, metadata

$ ./_output/linux/amd64/cluster-version-operator-tests info
{
   "apiVersion": "v1.0",
   "source": {
       "commit": "420e6d07",
       "build_date": "2025-11-03T13:51:50Z",
       "git_tree_state": "clean"
   },
   "component": {
       "product": "openshift",
       "type": "payload",
       "name": "cluster-version-operator"
   },
   "suites": [
       {
           "name": "openshift/cluster-version-operator/conformance/parallel",
           "parents": [
               "openshift/conformance/parallel"
           ],
           "qualifiers": [
               "(source == \"openshift:payload:cluster-version-operator\") \u0026\u0026 (!(name.contains(\"[Serial]\") || name.contains(\"[Slow]\")))"
           ]
       },
       {
           "name": "openshift/cluster-version-operator/conformance/serial",
           "parents": [
               "openshift/conformance/serial"
           ],
           "qualifiers": [
               "(source == \"openshift:payload:cluster-version-operator\") \u0026\u0026 (name.contains(\"[Serial]\"))"
           ]
       }
   ],
   "images": null
}

Confirming list outputs tests properly filtered by environment

$ ./_output/linux/amd64/cluster-version-operator-tests list
[
 {
   "name": "[Jira:Cluster Version Operator] cluster-version-operator-tests should support passing tests",
   "labels": {},
   "resources": {
     "isolation": {}
   },
   "source": "openshift:payload:cluster-version-operator",
   "lifecycle": "blocking",
   "environmentSelector": {}
 }
]

Confirming run-suite functions and produces valid JSON test results

$ ./_output/linux/amd64/cluster-version-operator-tests run-suite openshift/cluster-version-operator/conformance/parallel
 Running Suite:  - /home/dhurta/GolandProjects/cluster-version-operator
 ======================================================================
 Random Seed: 1762178101 - will randomize all specs

 Will run 1 of 1 specs
 ------------------------------
 [Jira:Cluster Version Operator] cluster-version-operator-tests should support passing tests
 /home/dhurta/GolandProjects/cluster-version-operator/test/cvo/cvo.go:9
 • [0.000 seconds]
 ------------------------------

 Ran 1 of 1 Specs in 0.000 seconds
 SUCCESS! -- 1 Passed | 0 Failed | 0 Pending | 0 Skipped
[
 {
   "name": "[Jira:Cluster Version Operator] cluster-version-operator-tests should support passing tests",
   "lifecycle": "blocking",
   "duration": 0,
   "startTime": "2025-11-03 13:55:01.681724 UTC",
   "endTime": "2025-11-03 13:55:01.682308 UTC",
   "result": "passed",
   "output": ""
 }
]
$ ./_output/linux/amd64/cluster-version-operator-tests run-suite openshift/cluster-version-operator/conformance/serial
null

Confirming run-test functions and produces valid JSON test results

$ ./_output/linux/amd64/cluster-version-operator-tests run-test -n "[Jira:Cluster Version Operator] cluster-version-operator-tests should support passing tests"
 Running Suite:  - /home/dhurta/GolandProjects/cluster-version-operator
 ======================================================================
 Random Seed: 1762178152 - will randomize all specs

 Will run 1 of 1 specs
 ------------------------------
 [Jira:Cluster Version Operator] cluster-version-operator-tests should support passing tests
 /home/dhurta/GolandProjects/cluster-version-operator/test/cvo/cvo.go:9
 • [0.000 seconds]
 ------------------------------

 Ran 1 of 1 Specs in 0.000 seconds
 SUCCESS! -- 1 Passed | 0 Failed | 0 Pending | 0 Skipped
[
 {
   "name": "[Jira:Cluster Version Operator] cluster-version-operator-tests should support passing tests",
   "lifecycle": "blocking",
   "duration": 0,
   "startTime": "2025-11-03 13:55:52.869586 UTC",
   "endTime": "2025-11-03 13:55:52.870196 UTC",
   "result": "passed",
   "output": ""
 }
]

Checking an e2e job for the sole sanity test:

The sole CVO test [Jira:Cluster Version Operator] cluster-version-operator-tests should support passing tests is visible in a pull-ci-openshift-origin-main-e2e-gcp-ovn run.

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

openshift-ci-robot commented Nov 3, 2025

@DavidHurta: This pull request references OTA-1585 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 "4.21.0" version, but no target version was set.

Details

In response to this:

Register the cluster version operator (CVO) tests extension in the origin's extension registry.


Testing

Confirming info outputs correct API version, metadata

$ ./_output/linux/amd64/cluster-version-operator-tests info
{
   "apiVersion": "v1.0",
   "source": {
       "commit": "420e6d07",
       "build_date": "2025-11-03T13:51:50Z",
       "git_tree_state": "clean"
   },
   "component": {
       "product": "openshift",
       "type": "payload",
       "name": "cluster-version-operator"
   },
   "suites": [
       {
           "name": "openshift/cluster-version-operator/conformance/parallel",
           "parents": [
               "openshift/conformance/parallel"
           ],
           "qualifiers": [
               "(source == \"openshift:payload:cluster-version-operator\") \u0026\u0026 (!(name.contains(\"[Serial]\") || name.contains(\"[Slow]\")))"
           ]
       },
       {
           "name": "openshift/cluster-version-operator/conformance/serial",
           "parents": [
               "openshift/conformance/serial"
           ],
           "qualifiers": [
               "(source == \"openshift:payload:cluster-version-operator\") \u0026\u0026 (name.contains(\"[Serial]\"))"
           ]
       }
   ],
   "images": null
}

Confirming list outputs tests properly filtered by environment

$ ./_output/linux/amd64/cluster-version-operator-tests list
[
 {
   "name": "[Jira:Cluster Version Operator] cluster-version-operator-tests should support passing tests",
   "labels": {},
   "resources": {
     "isolation": {}
   },
   "source": "openshift:payload:cluster-version-operator",
   "lifecycle": "blocking",
   "environmentSelector": {}
 }
]

Confirming run-suite functions and produces valid JSON test results

$ ./_output/linux/amd64/cluster-version-operator-tests run-suite openshift/cluster-version-operator/conformance/parallel
 Running Suite:  - /home/dhurta/GolandProjects/cluster-version-operator
 ======================================================================
 Random Seed: 1762178101 - will randomize all specs

 Will run 1 of 1 specs
 ------------------------------
 [Jira:Cluster Version Operator] cluster-version-operator-tests should support passing tests
 /home/dhurta/GolandProjects/cluster-version-operator/test/cvo/cvo.go:9
 • [0.000 seconds]
 ------------------------------

 Ran 1 of 1 Specs in 0.000 seconds
 SUCCESS! -- 1 Passed | 0 Failed | 0 Pending | 0 Skipped
[
 {
   "name": "[Jira:Cluster Version Operator] cluster-version-operator-tests should support passing tests",
   "lifecycle": "blocking",
   "duration": 0,
   "startTime": "2025-11-03 13:55:01.681724 UTC",
   "endTime": "2025-11-03 13:55:01.682308 UTC",
   "result": "passed",
   "output": ""
 }
]
$ ./_output/linux/amd64/cluster-version-operator-tests run-suite openshift/cluster-version-operator/conformance/serial
null

Confirming run-test functions and produces valid JSON test results

$ ./_output/linux/amd64/cluster-version-operator-tests run-test -n "[Jira:Cluster Version Operator] cluster-version-operator-tests should support passing tests"
 Running Suite:  - /home/dhurta/GolandProjects/cluster-version-operator
 ======================================================================
 Random Seed: 1762178152 - will randomize all specs

 Will run 1 of 1 specs
 ------------------------------
 [Jira:Cluster Version Operator] cluster-version-operator-tests should support passing tests
 /home/dhurta/GolandProjects/cluster-version-operator/test/cvo/cvo.go:9
 • [0.000 seconds]
 ------------------------------

 Ran 1 of 1 Specs in 0.000 seconds
 SUCCESS! -- 1 Passed | 0 Failed | 0 Pending | 0 Skipped
[
 {
   "name": "[Jira:Cluster Version Operator] cluster-version-operator-tests should support passing tests",
   "lifecycle": "blocking",
   "duration": 0,
   "startTime": "2025-11-03 13:55:52.869586 UTC",
   "endTime": "2025-11-03 13:55:52.870196 UTC",
   "result": "passed",
   "output": ""
 }
]

Checking an e2e run for the sole sanity test:

The sole CVO test [Jira:Cluster Version Operator] cluster-version-operator-tests should support passing tests is visible in a pull-ci-openshift-origin-main-e2e-gcp-ovn run.

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.

@DavidHurta DavidHurta marked this pull request as ready for review November 3, 2025 17:32
@openshift-ci openshift-ci bot removed the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Nov 3, 2025
@DavidHurta
Copy link
Contributor Author

/cc @hongkailiu

@openshift-ci openshift-ci bot requested a review from hongkailiu November 3, 2025 17:35
@openshift-trt
Copy link

openshift-trt bot commented Nov 4, 2025

Risk analysis has seen new tests most likely introduced by this PR.
Please ensure that new tests meet guidelines for naming and stability.

New tests seen in this PR at sha: 281c514

  • "[Jira:Cluster Version Operator] cluster-version-operator-tests should support passing tests" [Total: 12, Pass: 12, Fail: 0, Flake: 0]

Copy link
Member

@hongkailiu hongkailiu left a comment

Choose a reason for hiding this comment

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

/lgtm

/hold

https://github.com/openshift/cluster-version-operator/pull/1249/files#diff-af72828533c5a74651f4d542a30b2552e25fdbb62be6e03ac19a573231bc2348R3 is changes test name.

Should we merge ^^^ before registration (to avoid the process of renaming)?

@openshift-ci openshift-ci bot added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Nov 5, 2025
@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Nov 5, 2025
@DavidHurta
Copy link
Contributor Author

/hold
Addressing #30316 (review)

@DavidHurta DavidHurta force-pushed the add-cvo-test-extension branch from 281c514 to 0e5a1c8 Compare November 14, 2025 13:49
@openshift-ci openshift-ci bot removed the lgtm Indicates that a PR is ready to be merged. label Nov 14, 2025
@DavidHurta
Copy link
Contributor Author

/unhold

@openshift-ci openshift-ci bot removed the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Nov 14, 2025
@DavidHurta
Copy link
Contributor Author

/retest-required

@openshift-trt
Copy link

openshift-trt bot commented Nov 18, 2025

Risk analysis has seen new tests most likely introduced by this PR.
Please ensure that new tests meet guidelines for naming and stability.

New Test Risks for sha: 0e5a1c8

Job Name New Test Risk
pull-ci-openshift-origin-main-e2e-aws-ovn-microshift High - "[Jira:"Cluster Version Operator"] cluster-version-operator-tests should support passing tests" is a new test that was not present in all runs against the current commit.
pull-ci-openshift-origin-main-e2e-metal-ipi-ovn-ipv6 High - "[Jira:"Cluster Version Operator"] cluster-version-operator-tests should support passing tests" is a new test that was not present in all runs against the current commit.

New tests seen in this PR at sha: 0e5a1c8

  • "[Jira:"Cluster Version Operator"] cluster-version-operator-tests should support passing tests" [Total: 10, Pass: 10, Fail: 0, Flake: 0]

@hongkailiu
Copy link
Member

/lgtm

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

/assign @xueqzhan

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Nov 24, 2025

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: DavidHurta, hongkailiu, petr-muller

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 Nov 24, 2025
@DavidHurta
Copy link
Contributor Author

/verified by CI

The sole test, as of the moment, in the CVO extension is discoverable and is passing in the correct jobs.

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

@DavidHurta: This PR has been marked as verified by CI.

Details

In response to this:

/verified by CI

The sole test, as of the moment, in the CVO extension is discoverable and is passing in the correct jobs.

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

/retest-required

Remaining retests: 0 against base HEAD 66bb721 and 2 for PR HEAD 0e5a1c8 in total

@openshift-trt
Copy link

openshift-trt bot commented Nov 25, 2025

Risk analysis has seen new tests most likely introduced by this PR.
Please ensure that new tests meet guidelines for naming and stability.

New Test Risks for sha: 0e5a1c8

Job Name New Test Risk
pull-ci-openshift-origin-main-e2e-aws-ovn-microshift High - "[Jira:"Cluster Version Operator"] cluster-version-operator-tests should support passing tests" is a new test that was not present in all runs against the current commit.
pull-ci-openshift-origin-main-e2e-metal-ipi-ovn-ipv6 High - "[Jira:"Cluster Version Operator"] cluster-version-operator-tests should support passing tests" is a new test that was not present in all runs against the current commit.

New tests seen in this PR at sha: 0e5a1c8

  • "[Jira:"Cluster Version Operator"] cluster-version-operator-tests should support passing tests" [Total: 11, Pass: 11, Fail: 0, Flake: 0]

@openshift-merge-bot openshift-merge-bot bot merged commit 1f741ac into openshift:main Nov 25, 2025
19 of 20 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.

5 participants