Skip to content

Conversation

bertinatto
Copy link
Member

/assign @kevinrizza

hack/update-kube-vendor.sh 6efb6a95323fe35285877dcdade237444b35cae0 github.com/openshift/kubernetes
@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 Sep 9, 2025
@openshift-ci-robot
Copy link

@bertinatto: This pull request references Jira Issue OCPBUGS-60507, which is invalid:

  • expected the bug to be in one of the following states: NEW, ASSIGNED, POST, but it is ON_QA instead

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:

/assign @kevinrizza

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.

@bertinatto
Copy link
Member 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 Sep 9, 2025
@openshift-ci-robot
Copy link

@bertinatto: This pull request references Jira Issue OCPBUGS-60507, which is valid.

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

Requesting review from QA contact:
/cc @gangwgr

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 openshift-ci bot requested a review from gangwgr September 9, 2025 13:30
@openshift-ci openshift-ci bot added the vendor-update Touching vendor dir or related files label Sep 9, 2025
@openshift-ci openshift-ci bot requested review from deads2k and sjenning September 9, 2025 13:30
@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Sep 9, 2025
@openshift-ci openshift-ci bot added the e2e-images-update Related to images used by e2e tests label Sep 9, 2025
@bertinatto
Copy link
Member Author

/retest

@kevinrizza
Copy link
Member

/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Sep 9, 2025
@kevinrizza
Copy link
Member

/verified bypass

Copy link
Contributor

openshift-ci bot commented Sep 9, 2025

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: bertinatto, kevinrizza

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 openshift-ci-robot added the verified Signifies that the PR passed pre-merge verification criteria label Sep 9, 2025
@openshift-ci-robot
Copy link

@kevinrizza: The verified label has been added.

In response to this:

/verified bypass

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.

Copy link
Contributor

openshift-ci bot commented Sep 9, 2025

@bertinatto: 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-metal-ipi-serial-ovn-ipv6-2of2 a847e32 link false /test e2e-metal-ipi-serial-ovn-ipv6-2of2
ci/prow/e2e-hypershift-conformance a847e32 link false /test e2e-hypershift-conformance
ci/prow/e2e-gcp-ovn-rt-upgrade a847e32 link false /test e2e-gcp-ovn-rt-upgrade
ci/prow/e2e-aws-disruptive a847e32 link false /test e2e-aws-disruptive
ci/prow/e2e-metal-ipi-virtualmedia a847e32 link false /test e2e-metal-ipi-virtualmedia
ci/prow/e2e-metal-ipi-ovn-dualstack a847e32 link false /test e2e-metal-ipi-ovn-dualstack
ci/prow/e2e-aws-ovn-kube-apiserver-rollout a847e32 link false /test e2e-aws-ovn-kube-apiserver-rollout

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 Sep 9, 2025

Job Failure Risk Analysis for sha: a847e32

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

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

Job Name New Test Risk
pull-ci-openshift-origin-main-okd-scos-e2e-aws-ovn High - "Find the input image origin_scos-4.21_tools and tag it into the pipeline" is a new test that was not present in all runs against the current commit.

New tests seen in this PR at sha: a847e32

  • "Find the input image origin_scos-4.21_tools and tag it into the pipeline" [Total: 2, Pass: 2, Fail: 0, Flake: 0]

@openshift-merge-bot openshift-merge-bot bot merged commit 841b786 into openshift:main Sep 9, 2025
40 of 47 checks passed
@openshift-ci-robot
Copy link

@bertinatto: Jira Issue OCPBUGS-60507: All pull requests linked via external trackers have merged:

Jira Issue OCPBUGS-60507 has been moved to the MODIFIED state.

In response to this:

/assign @kevinrizza

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.

@sdodson
Copy link
Member

sdodson commented Sep 9, 2025

/verified by the fact that we won't ship 4.21 on 1.33 so this won't matter

@openshift-ci-robot
Copy link

@sdodson: Jira Issue OCPBUGS-60507 is in an unrecognized state (MODIFIED) and will not be moved to the MODIFIED state.

In response to this:

/verified by the fact that we won't ship 4.21 on 1.33 so this won't matter

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.

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. e2e-images-update Related to images used by e2e tests 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. vendor-update Touching vendor dir or related files verified Signifies that the PR passed pre-merge verification criteria
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants