Skip to content

Conversation

@lack
Copy link
Member

@lack lack commented Oct 21, 2025

Signed-off-by: Jim Ramsay [email protected]

@openshift-ci openshift-ci bot requested review from cgoncalves and fedepaol October 21, 2025 13:59
@openshift-ci
Copy link

openshift-ci bot commented Oct 21, 2025

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: lack

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 Oct 21, 2025
@lack
Copy link
Member Author

lack commented Oct 21, 2025

/jira cherry-pick OCPBUGS-62957

@openshift-ci-robot
Copy link
Collaborator

@lack: Jira Issue OCPBUGS-62957 has been cloned as Jira Issue OCPBUGS-63357. Will retitle bug to link to clone.
/retitle OCPBUGS-63357: core RDS: Ignore k8s.v1.cni.cncf.io/resourceName annotation

In response to this:

/jira cherry-pick OCPBUGS-62957

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 core RDS: Ignore k8s.v1.cni.cncf.io/resourceName annotation OCPBUGS-63357: core RDS: Ignore k8s.v1.cni.cncf.io/resourceName annotation Oct 21, 2025
@openshift-ci-robot
Copy link
Collaborator

@lack: This pull request references Jira Issue OCPBUGS-63357, which is invalid:

  • expected dependent Jira Issue OCPBUGS-62957 to be in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), 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:

Signed-off-by: Jim Ramsay [email protected]

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.

@lack
Copy link
Member Author

lack commented Nov 6, 2025

/jira refresh

@openshift-ci-robot
Copy link
Collaborator

@lack: This pull request references Jira Issue OCPBUGS-63357, 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.17.z) matches configured target version for branch (4.17.z)
  • 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-62957 is in the state Verified, which is one of the valid states (VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA))
  • dependent Jira Issue OCPBUGS-62957 targets the "4.18.z" version, which is one of the valid target versions: 4.18.0, 4.18.z
  • bug has dependents

Requesting review from QA contact:
/cc @dgonyier

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 dgonyier November 6, 2025 15:28
@lack
Copy link
Member Author

lack commented Nov 6, 2025

/cherry-pick release-4.16

@openshift-cherrypick-robot

@lack: once the present PR merges, I will cherry-pick it on top of release-4.16 in a new PR and assign it to you.

In response to this:

/cherry-pick release-4.16

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.

@abraham2512
Copy link
Member

/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Nov 6, 2025
@openshift-merge-bot openshift-merge-bot bot merged commit 7d231e1 into openshift-kni:release-4.17 Nov 6, 2025
5 checks passed
@openshift-ci-robot
Copy link
Collaborator

@lack: Jira Issue OCPBUGS-63357: All pull requests linked via external trackers have merged:

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

In response to this:

Signed-off-by: Jim Ramsay [email protected]

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-cherrypick-robot

@lack: new pull request created: #442

In response to this:

/cherry-pick release-4.16

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.

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. lgtm Indicates that a PR is ready to be merged.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants