Skip to content

(DO NOT MERGE) OCPBUGS-60154: OLMv1: Skip check to verify maxOpenshiftVersion block upgrades due missing valid scenario #30056

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.

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

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

Conversation

camilamacedo86
Copy link
Contributor

@camilamacedo86 camilamacedo86 commented Aug 5, 2025

Ultimately, if we have no choice.

@openshift-ci openshift-ci bot requested review from kevinrizza and perdasilva August 5, 2025 11:48
Copy link
Contributor

openshift-ci bot commented Aug 5, 2025

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: camilamacedo86
Once this PR has been reviewed and has the lgtm label, please assign tmshort for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found 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

@camilamacedo86 camilamacedo86 changed the title Unblock release by skiping that which cannot be performed OLMv1: Skip check to verify maxOpenshiftVersion block upgrades due missing valid scenario Aug 5, 2025
@camilamacedo86
Copy link
Contributor Author

/retest-required

@camilamacedo86 camilamacedo86 reopened this Aug 7, 2025
@camilamacedo86 camilamacedo86 changed the title OLMv1: Skip check to verify maxOpenshiftVersion block upgrades due missing valid scenario (DO NOT MERGE) OLMv1: Skip check to verify maxOpenshiftVersion block upgrades due missing valid scenario Aug 7, 2025
@camilamacedo86 camilamacedo86 changed the title (DO NOT MERGE) OLMv1: Skip check to verify maxOpenshiftVersion block upgrades due missing valid scenario (DO NOT MERGE) OCPBUGS-60154: OLMv1: Skip check to verify maxOpenshiftVersion block upgrades due missing valid scenario Aug 7, 2025
@openshift-ci-robot openshift-ci-robot added jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. labels Aug 7, 2025
@openshift-ci-robot
Copy link

@camilamacedo86: This pull request references Jira Issue OCPBUGS-60154, which is valid.

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 POST, which is one of the valid states (NEW, ASSIGNED, POST)

Requesting review from QA contact:
/cc @Xia-Zhao-rh

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

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.

@openshift-ci openshift-ci bot requested a review from Xia-Zhao-rh August 7, 2025 12:18
@camilamacedo86
Copy link
Contributor Author

/retest-required

1 similar comment
@camilamacedo86
Copy link
Contributor Author

/retest-required

Copy link
Contributor

openshift-ci bot commented Aug 7, 2025

@camilamacedo86: 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-gcp-ovn-rt-upgrade faabffe link false /test e2e-gcp-ovn-rt-upgrade
ci/prow/e2e-aws-ovn-single-node faabffe link false /test e2e-aws-ovn-single-node
ci/prow/okd-scos-e2e-aws-ovn faabffe link false /test okd-scos-e2e-aws-ovn
ci/prow/e2e-aws-ovn-single-node-serial faabffe link false /test e2e-aws-ovn-single-node-serial
ci/prow/e2e-metal-ipi-ovn-dualstack-local-gateway faabffe link false /test e2e-metal-ipi-ovn-dualstack-local-gateway
ci/prow/e2e-openstack-ovn faabffe link false /test e2e-openstack-ovn
ci/prow/e2e-metal-ipi-serial-ovn-ipv6-2of2 faabffe link false /test e2e-metal-ipi-serial-ovn-ipv6-2of2
ci/prow/e2e-aws-ovn-kube-apiserver-rollout faabffe link false /test e2e-aws-ovn-kube-apiserver-rollout
ci/prow/e2e-agnostic-ovn-cmd faabffe link false /test e2e-agnostic-ovn-cmd
ci/prow/e2e-aws-disruptive faabffe link false /test e2e-aws-disruptive
ci/prow/e2e-aws-ovn-single-node-upgrade faabffe link false /test e2e-aws-ovn-single-node-upgrade
ci/prow/e2e-gcp-ovn-techpreview-serial-2of2 faabffe link false /test e2e-gcp-ovn-techpreview-serial-2of2

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.

Copy link

openshift-trt bot commented Aug 7, 2025

Job Failure Risk Analysis for sha: faabffe

Job Name Failure Risk
pull-ci-openshift-origin-main-e2e-aws-disruptive High
[sig-node] static pods should start after being created
This test has passed 99.48% of 3267 runs on release 4.20 [Overall] in the last week.
---
[bz-Etcd] clusteroperator/etcd should not change condition/Available
This test has passed 99.66% of 3267 runs on release 4.20 [Overall] in the last week.

@camilamacedo86
Copy link
Contributor Author

/hold

We have this PR done as latest resource

@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 Aug 8, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. 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.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants