Skip to content

Conversation

@openshift-cherrypick-robot

This is an automated cherry-pick of #10169

/assign jcpowermac

@openshift-ci-robot
Copy link
Contributor

openshift-ci-robot commented Dec 18, 2025

@openshift-cherrypick-robot: Ignoring requests to cherry-pick non-bug issues: SPLAT-2584
Detected clone of Jira Issue OCPBUGS-69434 with correct target version. Will retitle the PR to link to the clone.
/retitle [release-4.21] SPLAT-2584,OCPBUGS-69685: Added ability to install different IPAM version when in TP.

Details

In response to this:

This is an automated cherry-pick of #10169

/assign jcpowermac

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 changed the title [release-4.21] SPLAT-2584,OCPBUGS-69434: Added ability to install different IPAM version when in TP. [release-4.21] SPLAT-2584,OCPBUGS-69685: Added ability to install different IPAM version when in TP. Dec 18, 2025
@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 Dec 18, 2025
@openshift-ci-robot
Copy link
Contributor

openshift-ci-robot commented Dec 18, 2025

@openshift-cherrypick-robot: This pull request references SPLAT-2584 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 task to target the "4.21.0" version, but no target version was set.

This pull request references Jira Issue OCPBUGS-69685, which is invalid:

  • release note text must be set and not match the template OR release note type must be set to "Release Note Not Required". For more information you can reference the OpenShift Bug Process.
  • expected dependent Jira Issue OCPBUGS-69434 to be in one of the following states: MODIFIED, ON_QA, VERIFIED, but it is POST instead
  • expected dependent Jira Issue OCPBUGS-69434 to target a version in 4.22.0, but it targets "4.22" 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.

Details

In response to this:

This is an automated cherry-pick of #10169

/assign jcpowermac

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.

@damdo
Copy link
Member

damdo commented Dec 18, 2025

/assign @tthvo @patrickdillon @jcpowermac @vr4manta @rvanderp3

@damdo
Copy link
Member

damdo commented Dec 18, 2025

/payload-job-with-prs periodic-ci-openshift-release-master-nightly-4.21-e2e-vsphere-static-ovn-techpreview openshift/cluster-api#257

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Dec 18, 2025

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

  • periodic-ci-openshift-release-master-nightly-4.21-e2e-vsphere-static-ovn-techpreview

See details on https://pr-payload-tests.ci.openshift.org/runs/ci/bfbf99e0-dc1e-11f0-9bb7-765439ef7b4f-0

@tthvo
Copy link
Member

tthvo commented Dec 18, 2025

/test e2e-vsphere-static-ovn

@tthvo
Copy link
Member

tthvo commented Dec 18, 2025

/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 Dec 18, 2025
@openshift-ci-robot
Copy link
Contributor

openshift-ci-robot commented Dec 18, 2025

@tthvo: This pull request references SPLAT-2584 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 task to target the "4.21.0" version, but no target version was set.

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

7 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 New, which is one of the valid states (NEW, ASSIGNED, POST)
  • release note type set to "Release Note Not Required"
  • dependent bug Jira Issue OCPBUGS-69434 is in the state MODIFIED, which is one of the valid states (MODIFIED, ON_QA, VERIFIED)
  • dependent Jira Issue OCPBUGS-69434 targets the "4.22.0" version, which is one of the valid target versions: 4.22.0
  • bug has dependents

Requesting review from QA contact:
/cc @sunzhaohua2

Details

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 sunzhaohua2 December 18, 2025 19:28
Copy link
Member

@tthvo tthvo left a comment

Choose a reason for hiding this comment

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

/lgtm
/approve

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

openshift-ci bot commented Dec 18, 2025

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: tthvo

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 Dec 18, 2025
@tthvo
Copy link
Member

tthvo commented Dec 18, 2025

/verified by payload testing (TP) and pre-submit (Default)

@openshift-ci-robot openshift-ci-robot added the verified Signifies that the PR passed pre-merge verification criteria label Dec 18, 2025
@openshift-ci-robot
Copy link
Contributor

@tthvo: This PR has been marked as verified by payload testing (TP) and pre-submit (Default).

Details

In response to this:

/verified by payload testing (TP) and pre-submit (Default)

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.

@tthvo
Copy link
Member

tthvo commented Dec 18, 2025

Payload testing for TP cluster passed: #10174 (comment) 🟢

Pre-submit testing for Default cluster also passed: ci/prow/e2e-vsphere-static-ovn 🟢

@tthvo
Copy link
Member

tthvo commented Dec 19, 2025

/cc @sadasu

@openshift-ci openshift-ci bot requested a review from sadasu December 19, 2025 18:20
@damdo
Copy link
Member

damdo commented Dec 20, 2025

/retest

1 similar comment
@damdo
Copy link
Member

damdo commented Dec 21, 2025

/retest

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Dec 21, 2025

@openshift-cherrypick-robot: The following test 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/okd-scos-images c5b5edf link true /test okd-scos-images

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.

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-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. verified Signifies that the PR passed pre-merge verification criteria

Projects

None yet

Development

Successfully merging this pull request may close these issues.

8 participants