Skip to content

OCPBUGS-57632: Revert "Merge pull request #29808 from Prashanth684/4552-cvo-test" #29926

New issue

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

Sign up for GitHub

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

Already on GitHub? Sign in to your account

Jump to bottom
Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

OCPBUGS-57632: Revert "Merge pull request #29808 from Prashanth684/4552-cvo-test" #29926

wants to merge 1 commit into from

Conversation

Prashanth684
Copy link
Contributor

This reverts commit 757cf53, reversing changes made to 4a5cc22.

Revert until https://issues.redhat.com/browse/OCPBUGS-57632 gets fixed. This test is failing on the metal-ipv6 platform because the test pod needs to have the registry certificate to access the image.

@Prashanth684
Revert "Merge pull request openshift#29808 from Prashanth684/4552-cvo…
5018491 
…-test"

This reverts commit 757cf53, reversing
changes made to 4a5cc22.
@openshift-ci-robot openshift-ci-robot added jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. labels Jun 18, 2025
@openshift-ci-robot
Copy link

@Prashanth684: This pull request references Jira Issue OCPBUGS-57632, which is invalid:

  • expected the bug to target the "4.20.0" version, but no target version was set

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

The bug has been updated to refer to the pull request using the external bug tracker.

In response to this:

This reverts commit 757cf53, reversing changes made to 4a5cc22.

Revert until https://issues.redhat.com/browse/OCPBUGS-57632 gets fixed. This test is failing on the metal-ipv6 platform because the test pod needs to have the registry certificate to access the image.

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.

@dgoodwin
Copy link
Contributor

/lgtm
/override ci/prow/e2e-metal-ipi-serial-ovn-ipv6-1of2
/override ci/prow/e2e-metal-ipi-ovn-ipv6
/override ci/prow/e2e-metal-ipi-ovn-dualstack
/override ci/prow/e2e-gcp-fips-serial-2of2
/override ci/prow/e2e-azure-ovn-etcd-scaling
/override ci/prow/okd-e2e-gcp
/override ci/prow/e2e-metal-ipi-serial-ovn-ipv6-2of2
/override ci/prow/e2e-metal-ipi-ovn-kube-apiserver-rollout
/override ci/prow/e2e-metal-ipi-ovn-dualstack-local-gateway
/override ci/prow/e2e-metal-ipi-ovn
/override ci/prow/e2e-gcp-fips-serial-1of2
/override ci/prow/e2e-gcp-disruptive
/override ci/prow/e2e-hypershift-conformance
/override ci/prow/e2e-gcp-ovn-upgrade
/override ci/prow/e2e-gcp-ovn-rt-upgrade
/override ci/prow/e2e-gcp-csi
/override ci/prow/e2e-azure
/override ci/prow/e2e-metal-ipi-serial-2of2
/override ci/prow/e2e-metal-ipi-serial-1of2
/override ci/prow/e2e-gcp-ovn-etcd-scaling
/override ci/prow/e2e-gcp-ovn
/override ci/prow/e2e-azure-ovn-upgrade
/override ci/prow/okd-scos-e2e-aws-ovn

No need to churn on testing for a revert.

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

openshift-ci bot commented Jun 18, 2025

@dgoodwin: Overrode contexts on behalf of dgoodwin: 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/okd-e2e-gcp, ci/prow/okd-scos-e2e-aws-ovn

In response to this:

/lgtm
/override ci/prow/e2e-metal-ipi-serial-ovn-ipv6-1of2
/override ci/prow/e2e-metal-ipi-ovn-ipv6
/override ci/prow/e2e-metal-ipi-ovn-dualstack
/override ci/prow/e2e-gcp-fips-serial-2of2
/override ci/prow/e2e-azure-ovn-etcd-scaling
/override ci/prow/okd-e2e-gcp
/override ci/prow/e2e-metal-ipi-serial-ovn-ipv6-2of2
/override ci/prow/e2e-metal-ipi-ovn-kube-apiserver-rollout
/override ci/prow/e2e-metal-ipi-ovn-dualstack-local-gateway
/override ci/prow/e2e-metal-ipi-ovn
/override ci/prow/e2e-gcp-fips-serial-1of2
/override ci/prow/e2e-gcp-disruptive
/override ci/prow/e2e-hypershift-conformance
/override ci/prow/e2e-gcp-ovn-upgrade
/override ci/prow/e2e-gcp-ovn-rt-upgrade
/override ci/prow/e2e-gcp-csi
/override ci/prow/e2e-azure
/override ci/prow/e2e-metal-ipi-serial-2of2
/override ci/prow/e2e-metal-ipi-serial-1of2
/override ci/prow/e2e-gcp-ovn-etcd-scaling
/override ci/prow/e2e-gcp-ovn
/override ci/prow/e2e-azure-ovn-upgrade
/override ci/prow/okd-scos-e2e-aws-ovn

No need to churn on testing for a revert.

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 OpenShift CI
Copy link
Contributor

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

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 18, 2025
@Prashanth684
Copy link
Contributor Author

/jira refresh

@openshift-ci-robot openshift-ci-robot added jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. and removed jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. labels Jun 24, 2025
@openshift-ci-robot
Copy link

@Prashanth684: This pull request references Jira Issue OCPBUGS-57632, which is valid. The bug has been moved to the POST state.

3 validation(s) were run on this bug
  • bug is open, matching expected state (open)
  • bug target version (4.20.0) matches configured target version for branch (4.20.0)
  • bug is in the state New, which is one of the valid states (NEW, ASSIGNED, POST)

No GitHub users were found matching the public email listed for the QA contact in Jira ([email protected]), skipping review request.

In response to this:

/jira refresh

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 03bd521 and 2 for PR HEAD 5018491 in total

@openshift-trt openshift-trt
Copy link

openshift-trt bot commented Jun 24, 2025

Job Failure Risk Analysis for sha: 5018491

Job Name Failure Risk
pull-ci-openshift-origin-main-e2e-aws-ovn-fips High

@openshift-ci-robot
Copy link

/retest-required

Remaining retests: 0 against base HEAD 03bd521 and 2 for PR HEAD 5018491 in total

1 similar comment
@openshift-ci-robot
Copy link

/retest-required

Remaining retests: 0 against base HEAD 03bd521 and 2 for PR HEAD 5018491 in total

@openshift-ci-robot
Copy link

/retest-required

Remaining retests: 0 against base HEAD 9de3251 and 1 for PR HEAD 5018491 in total

@openshift-ci-robot
Copy link

/retest-required

Remaining retests: 0 against base HEAD 9de3251 and 2 for PR HEAD 5018491 in total

@openshift-ci OpenShift CI
Copy link
Contributor

openshift-ci bot commented Jun 25, 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-1of2 5018491 link false /test e2e-aws-ovn-serial-publicnet-1of2
ci/prow/e2e-openstack-serial 5018491 link false /test e2e-openstack-serial
ci/prow/e2e-vsphere-ovn-etcd-scaling 5018491 link false /test e2e-vsphere-ovn-etcd-scaling
ci/prow/e2e-aws-ovn-single-node 5018491 link false /test e2e-aws-ovn-single-node
ci/prow/e2e-aws-ovn-etcd-scaling 5018491 link false /test e2e-aws-ovn-etcd-scaling
ci/prow/e2e-vsphere-ovn-dualstack-primaryv6 5018491 link false /test e2e-vsphere-ovn-dualstack-primaryv6
ci/prow/e2e-aws-ovn-kube-apiserver-rollout 5018491 link false /test e2e-aws-ovn-kube-apiserver-rollout
ci/prow/e2e-aws-ovn-single-node-upgrade 5018491 link false /test e2e-aws-ovn-single-node-upgrade
ci/prow/e2e-aws-disruptive 5018491 link false /test e2e-aws-disruptive
ci/prow/e2e-aws-ovn-fips 5018491 link true /test e2e-aws-ovn-fips

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

/retest-required

Remaining retests: 0 against base HEAD c72e949 and 1 for PR HEAD 5018491 in total

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@deads2k deads2k Awaiting requested review from deads2k

@LalatenduMohanty LalatenduMohanty Awaiting requested review from LalatenduMohanty

Assignees

@dgoodwin dgoodwin

Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. 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
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
3 participants
@Prashanth684 @openshift-ci-robot @dgoodwin