Skip to content

MULTIARCH-5391: Add new featuregate test to check if desired.Architecture is set as intended#29808

Merged
openshift-merge-bot[bot] merged 1 commit intoopenshift:mainfrom
Prashanth684:4552-cvo-test
Jun 10, 2025
Merged

MULTIARCH-5391: Add new featuregate test to check if desired.Architecture is set as intended#29808
openshift-merge-bot[bot] merged 1 commit intoopenshift:mainfrom
Prashanth684:4552-cvo-test

Conversation

@Prashanth684
Copy link
Copy Markdown
Contributor

A new featuregated field was introduced a while ago under clusterversion status - desired.Architecture which denotes the architecture of the release image being reconciled to. As we plan to promote the feature gate to default - this adds a basic test to check if the desired.Architecture is set based on the release.openshift.io/architecture: multi being present as part of the release metadata.

@Prashanth684 Prashanth684 requested a review from wking May 16, 2025 16:31
@Prashanth684
Copy link
Copy Markdown
Contributor Author

/test e2e-gcp-ovn-techpreview-serial

@Prashanth684
Copy link
Copy Markdown
Contributor Author

/test e2e-gcp-ovn-techpreview

@openshift-trt
Copy link
Copy Markdown

openshift-trt Bot commented May 20, 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: 9d53ca0

Job Name New Test Risk
pull-ci-openshift-origin-main-e2e-gcp-ovn-techpreview Medium - "[sig-cluster-lifecycle][OCPFeatureGate:ImageStreamImportMode] ClusterVersion API desired.architecture field in the CV should be multi or empty depending on the 'release.openshift.io/architecture' field being set in the release payload's metadata [apigroup:config.openshift.io] [Suite:openshift/conformance/parallel]" is a new test, and was only seen in one job.

New tests seen in this PR at sha: 9d53ca0

  • "[sig-cluster-lifecycle][OCPFeatureGate:ImageStreamImportMode] ClusterVersion API desired.architecture field in the CV should be multi or empty depending on the 'release.openshift.io/architecture' field being set in the release payload's metadata [apigroup:config.openshift.io] [Suite:openshift/conformance/parallel]" [Total: 1, Pass: 1, Fail: 0, Flake: 0]

@@ -0,0 +1,5 @@
reviewers:
- cluster-version-operator-test-case-reviewers
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

Our existing consumer for this alias is in test/extended/util/openshift/clusterversionoperator. I'm not all that clear on how test/extended is organized, but it seems like we should keep these CVO-functionality tests collected in the same directory?

Copy link
Copy Markdown
Contributor Author

@Prashanth684 Prashanth684 May 27, 2025

Choose a reason for hiding this comment

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

that file seems to be the utils file whereas this is where the test is actually defined, listing cvo folks as owners. The implementation here is similar, defining a new directory for this test case - but having it as a more generic clusterversion directory than be specific to a test.

Comment thread test/extended/clusterversion/clusterversion.go Outdated
Comment thread test/extended/clusterversion/clusterversion.go Outdated
@Prashanth684
Copy link
Copy Markdown
Contributor Author

/retest-required

@petr-muller
Copy link
Copy Markdown
Member

/cc

@openshift-ci openshift-ci Bot requested a review from petr-muller May 28, 2025 14:05
@Prashanth684
Copy link
Copy Markdown
Contributor Author

/test e2e-gcp-ovn-techpreview-serial

@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci Bot commented May 28, 2025

@Prashanth684: The specified target(s) for /test were not found.
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-ovn-virt-techpreview
/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-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
Details

In response to this:

/test e2e-gcp-ovn-techpreview-serial

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.

@Prashanth684
Copy link
Copy Markdown
Contributor Author

/test e2e-gcp-ovn-techpreview

@openshift-trt
Copy link
Copy Markdown

openshift-trt Bot commented May 29, 2025

Job Failure Risk Analysis for sha: bca8bc2

Job Name Failure Risk
pull-ci-openshift-origin-main-4.12-upgrade-from-stable-4.11-e2e-aws-ovn-upgrade-rollback High
operator conditions network
This test has passed 99.02% of 3875 runs on release 4.20 [Overall] in the last week.
pull-ci-openshift-origin-main-e2e-aws-disruptive Medium
[sig-node] static pods should start after being created
Potential external regression detected for High Risk Test analysis
---
[sig-node] node-lifecycle detects unexpected not ready node
Potential external regression detected for High Risk Test analysis

Open Bugs
node-lifecycle detects unexpected not ready node failing on azure serial and upgrade jobs
---
[sig-architecture] platform pods in ns/openshift-etcd should not exit an excessive amount of times
Potential external regression detected for High Risk Test analysis
---
[bz-Etcd] clusteroperator/etcd should not change condition/Available
Potential external regression detected for High Risk Test analysis
pull-ci-openshift-origin-main-e2e-azure-ovn-upgrade IncompleteTests
Tests for this run (2124) are below the historical average (2890): IncompleteTests (not enough tests ran to make a reasonable risk analysis; this could be due to infra, installation, or upgrade problems)
pull-ci-openshift-origin-main-e2e-gcp-disruptive High
[sig-node] node-lifecycle detects unexpected not ready node
This test has passed 99.76% of 5437 runs on release 4.20 [Overall] in the last week.

Open Bugs
node-lifecycle detects unexpected not ready node failing on azure serial and upgrade jobs

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: bca8bc2

Job Name New Test Risk
pull-ci-openshift-origin-main-e2e-gcp-ovn-techpreview Medium - "[sig-cluster-lifecycle][OCPFeatureGate:ImageStreamImportMode] ClusterVersion API desired.architecture field in the CV should be multi or empty depending on the 'release.openshift.io/architecture' field being set in the release payload's metadata [apigroup:config.openshift.io] [Suite:openshift/conformance/parallel]" is a new test, and was only seen in one job.

New tests seen in this PR at sha: bca8bc2

  • "[sig-cluster-lifecycle][OCPFeatureGate:ImageStreamImportMode] ClusterVersion API desired.architecture field in the CV should be multi or empty depending on the 'release.openshift.io/architecture' field being set in the release payload's metadata [apigroup:config.openshift.io] [Suite:openshift/conformance/parallel]" [Total: 1, Pass: 1, Fail: 0, Flake: 0]

@Prashanth684 Prashanth684 changed the title Add new featuregate test to check if desired.Architecture is set as intended MULTIARCH-5391: Add new featuregate test to check if desired.Architecture is set as intended Jun 3, 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 3, 2025
@openshift-ci-robot
Copy link
Copy Markdown

openshift-ci-robot commented Jun 3, 2025

@Prashanth684: This pull request references MULTIARCH-5391 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.

Details

In response to this:

A new featuregated field was introduced a while ago under clusterversion status - desired.Architecture which denotes the architecture of the release image being reconciled to. As we plan to promote the feature gate to default - this adds a basic test to check if the desired.Architecture is set based on the release.openshift.io/architecture: multi being present as part of the release metadata.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

Comment thread test/extended/clusterversion/clusterversion.go
Comment thread test/extended/clusterversion/clusterversion.go Outdated
…ntended

A new featuregated field was introduced a while ago under clusterversion status -
`desired.Architecture` which denotes the architecture of the release
image being reconciled to. As we plan to promote the feature gate to
default - this adds a basic test to check if the `desired.Architecture`
is set based on the `release.openshift.io/architecture: multi`
being present as part of the release metadata.

This field in the ClusterVersion was added as part of https://issues.redhat.com/browse/MULTIARCH-4552
and is under the ImageStreamImportMode feature gate.
@Prashanth684
Copy link
Copy Markdown
Contributor Author

/test e2e-gcp-ovn-techpreview

@dgoodwin
Copy link
Copy Markdown
Contributor

/lgtm

@openshift-ci openshift-ci Bot added the lgtm Indicates that a PR is ready to be merged. label Jun 10, 2025
@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci Bot commented Jun 10, 2025

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: dgoodwin, Prashanth684

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 Jun 10, 2025
@openshift-ci-robot
Copy link
Copy Markdown

/retest-required

Remaining retests: 0 against base HEAD 3819a9b and 2 for PR HEAD 764dbfd in total

@Prashanth684
Copy link
Copy Markdown
Contributor Author

/retest-required

@openshift-ci-robot
Copy link
Copy Markdown

/retest-required

Remaining retests: 0 against base HEAD 3819a9b and 2 for PR HEAD 764dbfd in total

@openshift-trt
Copy link
Copy Markdown

openshift-trt Bot commented Jun 10, 2025

Job Failure Risk Analysis for sha: 764dbfd

Job Name Failure Risk
pull-ci-openshift-origin-main-4.12-upgrade-from-stable-4.11-e2e-aws-ovn-upgrade-rollback Medium
Job run should complete before timeout
This test has passed 96.60% of 3793 runs on release 4.20 [Overall] in the last week.
pull-ci-openshift-origin-main-e2e-aws-disruptive Medium
[sig-node] node-lifecycle detects unexpected not ready node
Potential external regression detected for High Risk Test analysis

Open Bugs
node-lifecycle detects unexpected not ready node failing on azure serial and upgrade jobs
---
[sig-architecture] platform pods in ns/openshift-etcd should not exit an excessive amount of times
Potential external regression detected for High Risk Test analysis
---
[sig-node] static pods should start after being created
This test has passed 97.77% of 5300 runs on release 4.20 [Overall] in the last week.

Open Bugs
[sig-node] static pods should start after being created
pull-ci-openshift-origin-main-e2e-aws-ovn-single-node-upgrade IncompleteTests
Tests for this run (103) are below the historical average (4157): IncompleteTests (not enough tests ran to make a reasonable risk analysis; this could be due to infra, installation, or upgrade problems)
pull-ci-openshift-origin-main-e2e-azure-ovn-etcd-scaling Low
[bz-kube-storage-version-migrator] clusteroperator/kube-storage-version-migrator should not change condition/Available
This test has passed 0.00% of 1 runs on release 4.20 [Architecture:amd64 FeatureSet:default Installer:ipi JobTier:rare Network:ovn NetworkStack:ipv4 Owner:eng Platform:azure SecurityMode:default Topology:ha Upgrade:none] in the last week.

Open Bugs
[CI] e2e-openstack-ovn-etcd-scaling job permanent fails at many openshift-test tests
---
[bz-Cloud Compute] clusteroperator/control-plane-machine-set should not change condition/Degraded
This test has passed 0.00% of 1 runs on release 4.20 [Architecture:amd64 FeatureSet:default Installer:ipi JobTier:rare Network:ovn NetworkStack:ipv4 Owner:eng Platform:azure SecurityMode:default Topology:ha Upgrade:none] in the last week.
pull-ci-openshift-origin-main-e2e-azure-ovn-upgrade IncompleteTests
Tests for this run (33) are below the historical average (3228): IncompleteTests (not enough tests ran to make a reasonable risk analysis; this could be due to infra, installation, or upgrade problems)
pull-ci-openshift-origin-main-e2e-gcp-disruptive High
[bz-openshift-apiserver] clusteroperator/openshift-apiserver should not change condition/Available
This test has passed 98.23% of 5300 runs on release 4.20 [Overall] in the last week.
---
[bz-Monitoring] clusteroperator/monitoring should not change condition/Available
This test has passed 99.09% of 5300 runs on release 4.20 [Overall] in the last week.
---
[bz-Monitoring] clusteroperator/monitoring should not change condition/Degraded
This test has passed 99.00% of 5300 runs on release 4.20 [Overall] in the last week.
---
[sig-arch][Late] operators should not create watch channels very often
This test has passed 98.13% of 4863 runs on release 4.20 [Overall] in the last week.

Open Bugs
Component Readiness Shows Old Test Name For Renamed Tests
ResilientWatchCacheInitialization (Re)enablement - operator watch counts from component readiness
pull-ci-openshift-origin-main-e2e-gcp-ovn-etcd-scaling High
[Jira:"kube-apiserver"] monitor test apiserver-incluster-availability collection
This test has passed 98.55% of 5300 runs on release 4.20 [Overall] in the last week.
---
[sig-api-machinery][Feature:APIServer][Late] API LBs follow /readyz of kube-apiserver and stop sending requests before server shutdowns for external clients [Suite:openshift/conformance/parallel]
This test has passed 98.21% of 3120 runs on release 4.20 [Overall] in the last week.

Open Bugs
[CI] e2e-openstack-ovn-etcd-scaling job permanent fails at many openshift-test tests
---
[Jira:"kube-apiserver"] monitor test audit-log-analyzer collection
This test has passed 98.55% of 5300 runs on release 4.20 [Overall] in the last week.
---
[sig-arch][Late][Jira:"kube-apiserver"] collect certificate data [Suite:openshift/conformance/parallel]
This test has passed 98.33% of 3173 runs on release 4.20 [Overall] in the last week.
---
Showing 4 of 6 test results

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: 764dbfd

Job Name New Test Risk
pull-ci-openshift-origin-main-e2e-gcp-ovn-techpreview Medium - "[sig-cluster-lifecycle][OCPFeatureGate:ImageStreamImportMode] ClusterVersion API desired architecture should be valid when architecture is set in release payload metadata [apigroup:config.openshift.io] [Suite:openshift/conformance/parallel]" is a new test, and was only seen in one job.

New tests seen in this PR at sha: 764dbfd

  • "[sig-cluster-lifecycle][OCPFeatureGate:ImageStreamImportMode] ClusterVersion API desired architecture should be valid when architecture is set in release payload metadata [apigroup:config.openshift.io] [Suite:openshift/conformance/parallel]" [Total: 1, Pass: 1, Fail: 0, Flake: 0]

@Prashanth684
Copy link
Copy Markdown
Contributor Author

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

@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci Bot commented Jun 10, 2025

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

Details

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
Copy Markdown
Contributor

openshift-ci Bot commented Jun 10, 2025

@Prashanth684: 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/e2e-aws-ovn-serial-publicnet 9d53ca0 link false /test e2e-aws-ovn-serial-publicnet
ci/prow/e2e-gcp-fips-serial 9d53ca0 link false /test e2e-gcp-fips-serial
ci/prow/e2e-metal-ipi-serial-ovn-ipv6 9d53ca0 link false /test e2e-metal-ipi-serial-ovn-ipv6
ci/prow/e2e-gcp-ovn-techpreview-serial 9d53ca0 link false /test e2e-gcp-ovn-techpreview-serial
ci/prow/4.12-upgrade-from-stable-4.11-e2e-aws-ovn-upgrade-rollback 764dbfd link false /test 4.12-upgrade-from-stable-4.11-e2e-aws-ovn-upgrade-rollback
ci/prow/e2e-aws-ovn-kube-apiserver-rollout 764dbfd link false /test e2e-aws-ovn-kube-apiserver-rollout
ci/prow/okd-e2e-gcp 764dbfd link false /test okd-e2e-gcp
ci/prow/e2e-vsphere-ovn-etcd-scaling 764dbfd link false /test e2e-vsphere-ovn-etcd-scaling
ci/prow/e2e-aws-ovn-serial-publicnet-1of2 764dbfd link false /test e2e-aws-ovn-serial-publicnet-1of2
ci/prow/e2e-metal-ipi-virtualmedia 764dbfd link false /test e2e-metal-ipi-virtualmedia
ci/prow/e2e-metal-ipi-serial-ovn-ipv6-2of2 764dbfd link false /test e2e-metal-ipi-serial-ovn-ipv6-2of2
ci/prow/e2e-azure-ovn-etcd-scaling 764dbfd link false /test e2e-azure-ovn-etcd-scaling
ci/prow/e2e-gcp-ovn-etcd-scaling 764dbfd link false /test e2e-gcp-ovn-etcd-scaling
ci/prow/e2e-aws-disruptive 764dbfd link false /test e2e-aws-disruptive
ci/prow/e2e-metal-ipi-ovn 764dbfd link false /test e2e-metal-ipi-ovn
ci/prow/e2e-openstack-serial 764dbfd link false /test e2e-openstack-serial
ci/prow/e2e-gcp-fips-serial-1of2 764dbfd link false /test e2e-gcp-fips-serial-1of2
ci/prow/e2e-azure-ovn-upgrade 764dbfd link false /test e2e-azure-ovn-upgrade
ci/prow/e2e-gcp-fips-serial-2of2 764dbfd link false /test e2e-gcp-fips-serial-2of2
ci/prow/e2e-vsphere-ovn-dualstack-primaryv6 764dbfd link false /test e2e-vsphere-ovn-dualstack-primaryv6
ci/prow/e2e-aws-ovn-single-node-upgrade 764dbfd link false /test e2e-aws-ovn-single-node-upgrade
ci/prow/e2e-openstack-ovn 764dbfd link false /test e2e-openstack-ovn
ci/prow/e2e-aws-ovn-etcd-scaling 764dbfd link false /test e2e-aws-ovn-etcd-scaling
ci/prow/e2e-gcp-disruptive 764dbfd link false /test e2e-gcp-disruptive

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.

@openshift-merge-bot openshift-merge-bot Bot merged commit 757cf53 into openshift:main Jun 10, 2025
40 of 60 checks passed
@openshift-bot
Copy link
Copy Markdown
Contributor

[ART PR BUILD NOTIFIER]

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

Prashanth684 added a commit to Prashanth684/origin that referenced this pull request Jun 18, 2025
…-test"

This reverts commit 757cf53, reversing
changes made to 4a5cc22.
openshift-merge-bot Bot added a commit that referenced this pull request Jun 27, 2025
OCPBUGS-57632: Revert "Merge pull request #29808 from Prashanth684/4552-cvo-test"
Prashanth684 added a commit to Prashanth684/origin that referenced this pull request Jul 8, 2025
openshift-merge-bot Bot added a commit that referenced this pull request Jul 18, 2025
MULTIARCH-5390: Reapply "Merge pull request #29808 from Prashanth684/4552-cvo-test"
ShudiLi pushed a commit to ShudiLi/origin that referenced this pull request Dec 11, 2025
…-test"

This reverts commit 757cf53, reversing
changes made to 4a5cc22.
ShudiLi pushed a commit to ShudiLi/origin that referenced this pull request Dec 11, 2025
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.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants