Skip to content

Conversation

@stbenjam
Copy link
Member

@stbenjam stbenjam commented Jun 4, 2025

Refactors openshift-tests to use OpenShift Tests Extension (OTE) framework for its own tests, and implements externally defined suites.

  • Consolidated the many scattered places origin filters tests down to the execution set using filter chains
  • Vendors and uses most OTE-provided Cobra commands
    • Replaced legacy run-test command with OTE, there's only one way tests are executed now
    • Added list command with subcommands for suites, extensions, and tests
  • Migrated origin existing suites to use CEL expressions
  • Retrieves suites from binaries, and makes them available for use

@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 Jun 4, 2025
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Jun 4, 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

@openshift-ci openshift-ci bot added vendor-update Touching vendor dir or related files approved Indicates a PR has been approved by an approver from all required OWNERS files. labels Jun 4, 2025
@stbenjam stbenjam force-pushed the suites branch 3 times, most recently from cb023b9 to 9f19c07 Compare June 11, 2025 14:13
@stbenjam
Copy link
Member Author

/payload-job-with-prs periodic-ci-openshift-release-master-ci-4.20-e2e-aws-ovn-techpreview openshift/kubernetes#2330

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Jun 11, 2025

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

  • periodic-ci-openshift-release-master-ci-4.20-e2e-aws-ovn-techpreview

See details on https://pr-payload-tests.ci.openshift.org/runs/ci/cefb7d70-46d2-11f0-98cf-d7542a299e08-0

@stbenjam
Copy link
Member Author

/payload-job-with-prs periodic-ci-openshift-release-master-ci-4.20-e2e-aws-ovn-techpreview openshift/kubernetes#2330

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Jun 11, 2025

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

  • periodic-ci-openshift-release-master-ci-4.20-e2e-aws-ovn-techpreview

See details on https://pr-payload-tests.ci.openshift.org/runs/ci/7493e860-46e9-11f0-8aa0-3d43604da7f0-0

@stbenjam
Copy link
Member Author

/test e2e-aws-ovn

@stbenjam
Copy link
Member Author

/test

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Jun 11, 2025

@stbenjam: The /test command needs one or more targets.
The following commands are available to trigger required jobs:

/test e2e-aws-jenkins
/test e2e-aws-ovn-edge-zones
/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-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 images
/test lint
/test okd-scos-images
/test unit
/test verify
/test verify-deps

The following commands are available to trigger optional jobs:

/test 4.12-upgrade-from-stable-4.11-e2e-aws-ovn-upgrade-rollback
/test e2e-agnostic-ovn-cmd
/test e2e-aws
/test e2e-aws-csi
/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-etcd-scaling
/test e2e-aws-ovn-ipsec-serial
/test e2e-aws-ovn-kube-apiserver-rollout
/test e2e-aws-ovn-kubevirt
/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-csi
/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-dualstack
/test e2e-metal-ipi-ovn-dualstack-bgp-local-gw-techpreview
/test e2e-metal-ipi-ovn-dualstack-bgp-techpreview
/test e2e-metal-ipi-ovn-dualstack-local-gateway
/test e2e-metal-ipi-ovn-kube-apiserver-rollout
/test e2e-metal-ipi-ovn-virt-dualstack
/test e2e-metal-ipi-ovn-virt-dualstack-techpreview
/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-e2e-gcp
/test okd-scos-e2e-aws-ovn

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

pull-ci-openshift-origin-main-4.12-upgrade-from-stable-4.11-e2e-aws-ovn-upgrade-rollback
pull-ci-openshift-origin-main-e2e-agnostic-ovn-cmd
pull-ci-openshift-origin-main-e2e-aws
pull-ci-openshift-origin-main-e2e-aws-csi
pull-ci-openshift-origin-main-e2e-aws-disruptive
pull-ci-openshift-origin-main-e2e-aws-ovn
pull-ci-openshift-origin-main-e2e-aws-ovn-cgroupsv2
pull-ci-openshift-origin-main-e2e-aws-ovn-edge-zones
pull-ci-openshift-origin-main-e2e-aws-ovn-etcd-scaling
pull-ci-openshift-origin-main-e2e-aws-ovn-fips
pull-ci-openshift-origin-main-e2e-aws-ovn-kube-apiserver-rollout
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-aws-ovn-serial-publicnet-1of2
pull-ci-openshift-origin-main-e2e-aws-ovn-serial-publicnet-2of2
pull-ci-openshift-origin-main-e2e-aws-ovn-single-node
pull-ci-openshift-origin-main-e2e-aws-ovn-single-node-serial
pull-ci-openshift-origin-main-e2e-aws-ovn-single-node-upgrade
pull-ci-openshift-origin-main-e2e-aws-ovn-upgrade
pull-ci-openshift-origin-main-e2e-aws-proxy
pull-ci-openshift-origin-main-e2e-azure
pull-ci-openshift-origin-main-e2e-azure-ovn-etcd-scaling
pull-ci-openshift-origin-main-e2e-azure-ovn-upgrade
pull-ci-openshift-origin-main-e2e-gcp-csi
pull-ci-openshift-origin-main-e2e-gcp-disruptive
pull-ci-openshift-origin-main-e2e-gcp-fips-serial-1of2
pull-ci-openshift-origin-main-e2e-gcp-fips-serial-2of2
pull-ci-openshift-origin-main-e2e-gcp-ovn
pull-ci-openshift-origin-main-e2e-gcp-ovn-etcd-scaling
pull-ci-openshift-origin-main-e2e-gcp-ovn-rt-upgrade
pull-ci-openshift-origin-main-e2e-gcp-ovn-upgrade
pull-ci-openshift-origin-main-e2e-hypershift-conformance
pull-ci-openshift-origin-main-e2e-metal-ipi-ovn
pull-ci-openshift-origin-main-e2e-metal-ipi-ovn-dualstack
pull-ci-openshift-origin-main-e2e-metal-ipi-ovn-dualstack-local-gateway
pull-ci-openshift-origin-main-e2e-metal-ipi-ovn-ipv6
pull-ci-openshift-origin-main-e2e-metal-ipi-ovn-kube-apiserver-rollout
pull-ci-openshift-origin-main-e2e-metal-ipi-serial-1of2
pull-ci-openshift-origin-main-e2e-metal-ipi-serial-2of2
pull-ci-openshift-origin-main-e2e-metal-ipi-serial-ovn-ipv6-1of2
pull-ci-openshift-origin-main-e2e-metal-ipi-serial-ovn-ipv6-2of2
pull-ci-openshift-origin-main-e2e-metal-ipi-virtualmedia
pull-ci-openshift-origin-main-e2e-openstack-ovn
pull-ci-openshift-origin-main-e2e-openstack-serial
pull-ci-openshift-origin-main-e2e-vsphere-ovn
pull-ci-openshift-origin-main-e2e-vsphere-ovn-dualstack-primaryv6
pull-ci-openshift-origin-main-e2e-vsphere-ovn-etcd-scaling
pull-ci-openshift-origin-main-e2e-vsphere-ovn-upi
pull-ci-openshift-origin-main-images
pull-ci-openshift-origin-main-lint
pull-ci-openshift-origin-main-okd-e2e-gcp
pull-ci-openshift-origin-main-okd-scos-e2e-aws-ovn
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

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.

@stbenjam
Copy link
Member Author

/test e2e-aws-ovn-serial-1of2
/test e2e-aws-ovn-serial-2of2
/test e2e-gcp-ovn-upgrade
/test e2e-aws-ovn-single-node-upgrade
/test e2e-aws-ovn-serial-publicnet-1of2
/test e2e-aws-ovn-kube-apiserver-rollout

@stbenjam
Copy link
Member Author

/test e2e-aws-ovn

@openshift-trt
Copy link

openshift-trt bot commented Jun 12, 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: 76bdb98

Job Name New Test Risk
pull-ci-openshift-origin-main-e2e-aws-ovn Medium - "[sig-network] services when using a plugin in a mode that does not isolate namespaces by default should allow connections to pods in different namespaces on different nodes via service IPs [Suite:openshift/conformance/parallel]" is a new test, and was only seen in one job.

New tests seen in this PR at sha: 76bdb98

  • "[sig-arch] ClusterOperators [apigroup:config.openshift.io] should define at least one namespace in their lists of related objects [Suite:openshift/conformance/parallel]" [Total: 3, Pass: 3, Fail: 0, Flake: 0]
  • "[sig-network] services when using a plugin in a mode that does not isolate namespaces by default should allow connections to pods in different namespaces on different nodes via service IPs [Suite:openshift/conformance/parallel]" [Total: 2, Pass: 2, Fail: 0, Flake: 0]
  • "[sig-network] services when using a plugin in a mode that does not isolate namespaces by default should allow connections to pods in different namespaces on the same node via service IPs [Suite:openshift/conformance/parallel]" [Total: 3, Pass: 3, Fail: 0, Flake: 0]

@stbenjam stbenjam changed the title [WIP] Enable using suite defintions from OTE TRT-2098, TRT-2097: Migrate origin to use OTE, and implement extension-derived suites Jun 12, 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 Jun 12, 2025
@openshift-ci-robot
Copy link

openshift-ci-robot commented Jun 12, 2025

@stbenjam: This pull request references TRT-2098 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.20.0" version, but no target version was set.

This pull request references TRT-2097 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.20.0" version, but no target version was set.

In response to this:

Refactors openshift-tests to use OpenShift Tests Extension (OTE) framework, and implements externally defined suites.

  • Vendors and uses most OTE-provided Cobra commands
  • Replaced legacy run-test command with OTE
  • Added new list command with subcommands for suites, extensions, and tests
  • Migrated origin existing suites to use CEL expressions
  • Retrieves suites from binaries, and makes them available
  • Consolidated the many scattered places origin filters tests down to the execution set using a new filter chain package

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 Jun 12, 2025

@stbenjam: This pull request references TRT-2098 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.20.0" version, but no target version was set.

This pull request references TRT-2097 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.20.0" version, but no target version was set.

In response to this:

Refactors openshift-tests to use OpenShift Tests Extension (OTE) framework, and implements externally defined suites.

  • Vendors and uses most OTE-provided Cobra commands
  • Replaced legacy run-test command with OTE, there's only one way tests are executed now
  • Added list command with subcommands for suites, extensions, and tests
  • Migrated origin existing suites to use CEL expressions
  • Retrieves suites from binaries, and makes them available for use
  • Consolidated the many scattered places origin filters tests down to the execution set using a new filter chain package

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.

@stbenjam stbenjam marked this pull request as ready for review June 12, 2025 11:27
@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 Jun 12, 2025
@openshift-ci openshift-ci bot requested review from deads2k and ironcladlou June 12, 2025 11:29
@openshift-ci-robot
Copy link

openshift-ci-robot commented Jun 12, 2025

@stbenjam: This pull request references TRT-2098 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.20.0" version, but no target version was set.

This pull request references TRT-2097 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.20.0" version, but no target version was set.

In response to this:

Refactors openshift-tests to use OpenShift Tests Extension (OTE) framework, and implements externally defined suites.

  • Consolidated the many scattered places origin filters tests down to the execution set using a new filter chain package
  • Vendors and uses most OTE-provided Cobra commands
  • Replaced legacy run-test command with OTE, there's only one way tests are executed now
  • Added list command with subcommands for suites, extensions, and tests
  • Migrated origin existing suites to use CEL expressions
  • Retrieves suites from binaries, and makes them available for use

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 Jun 12, 2025

@stbenjam: This pull request references TRT-2098 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.20.0" version, but no target version was set.

This pull request references TRT-2097 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.20.0" version, but no target version was set.

In response to this:

Refactors openshift-tests to use OpenShift Tests Extension (OTE) framework, and implements externally defined suites.

  • Consolidated the many scattered places origin filters tests down to the execution set using filter chains
  • Vendors and uses most OTE-provided Cobra commands
  • Replaced legacy run-test command with OTE, there's only one way tests are executed now
  • Added list command with subcommands for suites, extensions, and tests
  • Migrated origin existing suites to use CEL expressions
  • Retrieves suites from binaries, and makes them available for use

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.

@stbenjam
Copy link
Member Author

stbenjam commented Jul 7, 2025

/test e2e-metal-ipi-ovn-ipv6

@smg247
Copy link
Member

smg247 commented Jul 7, 2025

/lgtm

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

openshift-ci bot commented Jul 7, 2025

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: smg247, stbenjam

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

/retest-required

Remaining retests: 0 against base HEAD 9ff893a and 2 for PR HEAD c4895d7 in total

@openshift-trt
Copy link

openshift-trt bot commented Jul 7, 2025

Job Failure Risk Analysis for sha: c4895d7

Job Name Failure Risk
pull-ci-openshift-origin-main-e2e-metal-ipi-virtualmedia IncompleteTests
Tests for this run (22) are below the historical average (1607): IncompleteTests (not enough tests ran to make a reasonable risk analysis; this could be due to infra, installation, or upgrade problems)

@stbenjam
Copy link
Member Author

stbenjam commented Jul 7, 2025

/test e2e-aws-ovn-edge-zones

@openshift-trt
Copy link

openshift-trt bot commented Jul 8, 2025

Job Failure Risk Analysis for sha: c4895d7

Job Name Failure Risk
pull-ci-openshift-origin-main-e2e-metal-ipi-virtualmedia IncompleteTests
Tests for this run (22) are below the historical average (1649): IncompleteTests (not enough tests ran to make a reasonable risk analysis; this could be due to infra, installation, or upgrade problems)

@openshift-ci-robot
Copy link

/retest-required

Remaining retests: 0 against base HEAD f380d1e and 1 for PR HEAD c4895d7 in total

@stbenjam
Copy link
Member Author

stbenjam commented Jul 8, 2025

/override ci/prow/e2e-metal-ipi-ovn-ipv6

It passed on payload testing, keeps getting tripped on Fedora infra or a flaky test

362b539f-1233-4426-9278-36655866bfa8

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Jul 8, 2025

@stbenjam: Overrode contexts on behalf of stbenjam: ci/prow/e2e-metal-ipi-ovn-ipv6

In response to this:

/override ci/prow/e2e-metal-ipi-ovn-ipv6

It passed on payload testing, keeps getting tripped on Fedora infra or a flaky test

362b539f-1233-4426-9278-36655866bfa8

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.

@openshift-ci-robot
Copy link

/retest-required

Remaining retests: 0 against base HEAD f380d1e and 2 for PR HEAD c4895d7 in total

@stbenjam
Copy link
Member Author

stbenjam commented Jul 8, 2025

/skip
/override ci/prow/e2e-metal-ipi-ovn-ipv6

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Jul 8, 2025

@stbenjam: Overrode contexts on behalf of stbenjam: ci/prow/e2e-metal-ipi-ovn-ipv6

In response to this:

/skip
/override ci/prow/e2e-metal-ipi-ovn-ipv6

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.

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Jul 8, 2025

@stbenjam: Overrode contexts on behalf of stbenjam: ci/prow/e2e-metal-ipi-ovn-ipv6

In response to this:

/skip
/override ci/prow/e2e-metal-ipi-ovn-ipv6

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.

@openshift-trt
Copy link

openshift-trt bot commented Jul 8, 2025

Job Failure Risk Analysis for sha: c4895d7

Job Name Failure Risk
pull-ci-openshift-origin-main-e2e-metal-ipi-virtualmedia IncompleteTests
Tests for this run (22) are below the historical average (1577): IncompleteTests (not enough tests ran to make a reasonable risk analysis; this could be due to infra, installation, or upgrade problems)

@openshift-trt
Copy link

openshift-trt bot commented Jul 8, 2025

Job Failure Risk Analysis for sha: c4895d7

Job Name Failure Risk
pull-ci-openshift-origin-main-e2e-metal-ipi-virtualmedia IncompleteTests
Tests for this run (22) are below the historical average (1560): IncompleteTests (not enough tests ran to make a reasonable risk analysis; this could be due to infra, installation, or upgrade problems)

@stbenjam
Copy link
Member Author

stbenjam commented Jul 8, 2025

/override ci/prow/e2e-aws-ovn-microshift

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Jul 8, 2025

@stbenjam: Overrode contexts on behalf of stbenjam: ci/prow/e2e-aws-ovn-microshift

In response to this:

/override ci/prow/e2e-aws-ovn-microshift

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.

@stbenjam
Copy link
Member Author

stbenjam commented Jul 8, 2025

/override ci/prow/e2e-vpshere-ovn-upi

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Jul 8, 2025

@stbenjam: /override requires failed status contexts, check run or a prowjob name to operate on.
The following unknown contexts/checkruns were given:

  • ci/prow/e2e-vpshere-ovn-upi

Only the following failed contexts/checkruns were expected:

  • ci/prow/e2e-agnostic-ovn-cmd
  • ci/prow/e2e-aws
  • ci/prow/e2e-aws-csi
  • ci/prow/e2e-aws-disruptive
  • ci/prow/e2e-aws-ovn
  • ci/prow/e2e-aws-ovn-cgroupsv2
  • ci/prow/e2e-aws-ovn-edge-zones
  • ci/prow/e2e-aws-ovn-etcd-scaling
  • ci/prow/e2e-aws-ovn-fips
  • ci/prow/e2e-aws-ovn-kube-apiserver-rollout
  • ci/prow/e2e-aws-ovn-microshift
  • ci/prow/e2e-aws-ovn-microshift-serial
  • ci/prow/e2e-aws-ovn-serial-1of2
  • ci/prow/e2e-aws-ovn-serial-2of2
  • ci/prow/e2e-aws-ovn-serial-publicnet-1of2
  • ci/prow/e2e-aws-ovn-serial-publicnet-2of2
  • ci/prow/e2e-aws-ovn-single-node
  • ci/prow/e2e-aws-ovn-single-node-serial
  • ci/prow/e2e-aws-ovn-single-node-upgrade
  • ci/prow/e2e-aws-ovn-upgrade
  • ci/prow/e2e-aws-proxy
  • ci/prow/e2e-azure
  • ci/prow/e2e-azure-ovn-etcd-scaling
  • ci/prow/e2e-azure-ovn-upgrade
  • ci/prow/e2e-gcp-csi
  • ci/prow/e2e-gcp-disruptive
  • ci/prow/e2e-gcp-fips-serial-1of2
  • ci/prow/e2e-gcp-fips-serial-2of2
  • ci/prow/e2e-gcp-ovn
  • ci/prow/e2e-gcp-ovn-etcd-scaling
  • ci/prow/e2e-gcp-ovn-rt-upgrade
  • ci/prow/e2e-gcp-ovn-upgrade
  • ci/prow/e2e-hypershift-conformance
  • ci/prow/e2e-metal-ipi-ovn
  • ci/prow/e2e-metal-ipi-ovn-dualstack
  • ci/prow/e2e-metal-ipi-ovn-dualstack-local-gateway
  • ci/prow/e2e-metal-ipi-ovn-ipv6
  • ci/prow/e2e-metal-ipi-ovn-kube-apiserver-rollout
  • ci/prow/e2e-metal-ipi-serial-1of2
  • ci/prow/e2e-metal-ipi-serial-2of2
  • ci/prow/e2e-metal-ipi-serial-ovn-ipv6-1of2
  • ci/prow/e2e-metal-ipi-serial-ovn-ipv6-2of2
  • ci/prow/e2e-metal-ipi-virtualmedia
  • ci/prow/e2e-openstack-ovn
  • ci/prow/e2e-openstack-serial
  • ci/prow/e2e-vsphere-ovn
  • ci/prow/e2e-vsphere-ovn-dualstack-primaryv6
  • ci/prow/e2e-vsphere-ovn-etcd-scaling
  • ci/prow/e2e-vsphere-ovn-upi
  • ci/prow/images
  • ci/prow/lint
  • ci/prow/okd-e2e-gcp
  • ci/prow/okd-scos-e2e-aws-ovn
  • ci/prow/okd-scos-images
  • ci/prow/unit
  • ci/prow/verify
  • ci/prow/verify-deps
  • pull-ci-openshift-origin-main-e2e-agnostic-ovn-cmd
  • pull-ci-openshift-origin-main-e2e-aws
  • pull-ci-openshift-origin-main-e2e-aws-csi
  • pull-ci-openshift-origin-main-e2e-aws-disruptive
  • pull-ci-openshift-origin-main-e2e-aws-ovn
  • pull-ci-openshift-origin-main-e2e-aws-ovn-cgroupsv2
  • pull-ci-openshift-origin-main-e2e-aws-ovn-edge-zones
  • pull-ci-openshift-origin-main-e2e-aws-ovn-etcd-scaling
  • pull-ci-openshift-origin-main-e2e-aws-ovn-fips
  • pull-ci-openshift-origin-main-e2e-aws-ovn-kube-apiserver-rollout
  • 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-aws-ovn-serial-publicnet-1of2
  • pull-ci-openshift-origin-main-e2e-aws-ovn-serial-publicnet-2of2
  • pull-ci-openshift-origin-main-e2e-aws-ovn-single-node
  • pull-ci-openshift-origin-main-e2e-aws-ovn-single-node-serial
  • pull-ci-openshift-origin-main-e2e-aws-ovn-single-node-upgrade
  • pull-ci-openshift-origin-main-e2e-aws-ovn-upgrade
  • pull-ci-openshift-origin-main-e2e-aws-proxy
  • pull-ci-openshift-origin-main-e2e-azure
  • pull-ci-openshift-origin-main-e2e-azure-ovn-etcd-scaling
  • pull-ci-openshift-origin-main-e2e-azure-ovn-upgrade
  • pull-ci-openshift-origin-main-e2e-gcp-csi
  • pull-ci-openshift-origin-main-e2e-gcp-disruptive
  • pull-ci-openshift-origin-main-e2e-gcp-fips-serial-1of2
  • pull-ci-openshift-origin-main-e2e-gcp-fips-serial-2of2
  • pull-ci-openshift-origin-main-e2e-gcp-ovn
  • pull-ci-openshift-origin-main-e2e-gcp-ovn-etcd-scaling
  • pull-ci-openshift-origin-main-e2e-gcp-ovn-rt-upgrade
  • pull-ci-openshift-origin-main-e2e-gcp-ovn-upgrade
  • pull-ci-openshift-origin-main-e2e-hypershift-conformance
  • pull-ci-openshift-origin-main-e2e-metal-ipi-ovn
  • pull-ci-openshift-origin-main-e2e-metal-ipi-ovn-dualstack
  • pull-ci-openshift-origin-main-e2e-metal-ipi-ovn-dualstack-local-gateway
  • pull-ci-openshift-origin-main-e2e-metal-ipi-ovn-ipv6
  • pull-ci-openshift-origin-main-e2e-metal-ipi-ovn-kube-apiserver-rollout
  • pull-ci-openshift-origin-main-e2e-metal-ipi-serial-1of2
  • pull-ci-openshift-origin-main-e2e-metal-ipi-serial-2of2
  • pull-ci-openshift-origin-main-e2e-metal-ipi-serial-ovn-ipv6-1of2
  • pull-ci-openshift-origin-main-e2e-metal-ipi-serial-ovn-ipv6-2of2
  • pull-ci-openshift-origin-main-e2e-metal-ipi-virtualmedia
  • pull-ci-openshift-origin-main-e2e-openstack-ovn
  • pull-ci-openshift-origin-main-e2e-openstack-serial
  • pull-ci-openshift-origin-main-e2e-vsphere-ovn
  • pull-ci-openshift-origin-main-e2e-vsphere-ovn-dualstack-primaryv6
  • pull-ci-openshift-origin-main-e2e-vsphere-ovn-etcd-scaling
  • pull-ci-openshift-origin-main-e2e-vsphere-ovn-upi
  • pull-ci-openshift-origin-main-images
  • pull-ci-openshift-origin-main-lint
  • pull-ci-openshift-origin-main-okd-e2e-gcp
  • pull-ci-openshift-origin-main-okd-scos-e2e-aws-ovn
  • 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
  • tide

If you are trying to override a checkrun that has a space in it, you must put a double quote on the context.

In response to this:

/override ci/prow/e2e-vpshere-ovn-upi

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.

@stbenjam
Copy link
Member Author

stbenjam commented Jul 8, 2025

/override ci/prow/e2e-vsphere-ovn-upi

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Jul 8, 2025

@stbenjam: Overrode contexts on behalf of stbenjam: ci/prow/e2e-vsphere-ovn-upi

In response to this:

/override ci/prow/e2e-vsphere-ovn-upi

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.

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Jul 8, 2025

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

Test name Commit Details Required Rerun command
ci/prow/4.12-upgrade-from-stable-4.11-e2e-aws-ovn-upgrade-rollback 279a0cb link false /test 4.12-upgrade-from-stable-4.11-e2e-aws-ovn-upgrade-rollback
ci/prow/e2e-aws-ovn-serial-publicnet-1of2 c4895d7 link false /test e2e-aws-ovn-serial-publicnet-1of2
ci/prow/e2e-aws-ovn-etcd-scaling c4895d7 link false /test e2e-aws-ovn-etcd-scaling
ci/prow/e2e-azure-ovn-etcd-scaling c4895d7 link false /test e2e-azure-ovn-etcd-scaling
ci/prow/e2e-gcp-disruptive c4895d7 link false /test e2e-gcp-disruptive
ci/prow/e2e-gcp-fips-serial-1of2 c4895d7 link false /test e2e-gcp-fips-serial-1of2
ci/prow/e2e-gcp-ovn-etcd-scaling c4895d7 link false /test e2e-gcp-ovn-etcd-scaling
ci/prow/okd-scos-e2e-aws-ovn c4895d7 link false /test okd-scos-e2e-aws-ovn
ci/prow/e2e-aws-disruptive c4895d7 link false /test e2e-aws-disruptive
ci/prow/e2e-gcp-fips-serial-2of2 c4895d7 link false /test e2e-gcp-fips-serial-2of2
ci/prow/e2e-vsphere-ovn-etcd-scaling c4895d7 link false /test e2e-vsphere-ovn-etcd-scaling
ci/prow/e2e-vsphere-ovn-dualstack-primaryv6 c4895d7 link false /test e2e-vsphere-ovn-dualstack-primaryv6
ci/prow/e2e-azure-ovn-upgrade c4895d7 link false /test e2e-azure-ovn-upgrade
ci/prow/okd-e2e-gcp c4895d7 link false /test okd-e2e-gcp
ci/prow/e2e-openstack-ovn c4895d7 link false /test e2e-openstack-ovn
ci/prow/e2e-agnostic-ovn-cmd c4895d7 link false /test e2e-agnostic-ovn-cmd
ci/prow/e2e-metal-ipi-virtualmedia c4895d7 link false /test e2e-metal-ipi-virtualmedia
ci/prow/e2e-aws-ovn-single-node c4895d7 link false /test e2e-aws-ovn-single-node
ci/prow/e2e-aws-ovn-single-node-upgrade c4895d7 link false /test e2e-aws-ovn-single-node-upgrade

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.

@openshift-merge-bot openshift-merge-bot bot merged commit e9b1fca into openshift:main Jul 8, 2025
58 checks passed
@stbenjam stbenjam deleted the suites branch July 8, 2025 16:31
@openshift-bot
Copy link
Contributor

[ART PR BUILD NOTIFIER]

Distgit: openshift-enterprise-tests
This PR has been included in build openshift-enterprise-tests-container-v4.20.0-202507082342.p0.ge9b1fca.assembly.stream.el9.
All builds following this will include this PR.

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. vendor-update Touching vendor dir or related files

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants