Skip to content

Conversation

benluddy
Copy link

@openshift-ci openshift-ci bot requested a review from deads2k September 12, 2025 15:01
@p0lyn0mial
Copy link
Contributor

/retest-required

@p0lyn0mial
Copy link
Contributor

openshift/kubernetes-apiserver#70 merged - we can rebase.

@benluddy benluddy force-pushed the release-4.17-2025-september-12-apiserver-bump branch from ea4a2f4 to 47989e4 Compare September 19, 2025 12:52
@benluddy benluddy changed the title Bump openshift/kubernetes-apiserver for etcd retry patches. [release-4.17] OCPBUGS-61584: Bump openshift/kubernetes-apiserver for etcd retry patches. Sep 19, 2025
@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Sep 19, 2025
@openshift-ci-robot
Copy link
Contributor

@benluddy: This pull request references Jira Issue OCPBUGS-61584, which is valid.

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 POST, which is one of the valid states (NEW, ASSIGNED, POST)
  • release note type set to "Release Note Not Required"
  • dependent bug Jira Issue OCPBUGS-49841 is in the state Closed (Done-Errata), which is one of the valid states (VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA))
  • dependent Jira Issue OCPBUGS-49841 targets the "4.18.0" version, which is one of the valid target versions: 4.18.0, 4.18.z
  • bug has dependents

Requesting review from QA contact:
/cc @wangke19

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

In response to this:

openshift/kubernetes-apiserver#70
openshift/kubernetes-apiserver#58

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 openshift-ci-robot added the jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. label Sep 19, 2025
@openshift-ci openshift-ci bot requested a review from wangke19 September 19, 2025 12:53
@benluddy
Copy link
Author

/cc @p0lyn0mial

@openshift-ci openshift-ci bot requested a review from p0lyn0mial September 19, 2025 13:17
@wangke19
Copy link

/retest

Copy link
Contributor

openshift-ci bot commented Sep 23, 2025

@benluddy: all tests passed!

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.

@p0lyn0mial
Copy link
Contributor

/lgtm
/approve

@p0lyn0mial p0lyn0mial added the backport-risk-assessed Indicates a PR to a release branch has been evaluated and considered safe to accept. label Sep 25, 2025
@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Sep 25, 2025
@p0lyn0mial p0lyn0mial added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Sep 25, 2025
Copy link
Contributor

openshift-ci bot commented Sep 25, 2025

[APPROVALNOTIFIER] This PR is APPROVED

Approval requirements bypassed by manually added approval.

This pull-request has been approved by: benluddy, p0lyn0mial

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

@p0lyn0mial
Copy link
Contributor

/verified later @benluddy

@openshift-ci-robot openshift-ci-robot added verified-later verified Signifies that the PR passed pre-merge verification criteria labels Sep 25, 2025
@openshift-ci-robot
Copy link
Contributor

@p0lyn0mial: This PR has been marked to be verified later by @benluddy.

In response to this:

/verified later @benluddy

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-merge-bot openshift-merge-bot bot merged commit 731ed82 into openshift:release-4.17 Sep 25, 2025
9 checks passed
@openshift-ci-robot
Copy link
Contributor

@benluddy: Jira Issue OCPBUGS-61584: All pull requests linked via external trackers have merged:

This pull request has the verified-later tag and will need to be manually moved to VERIFIED after testing. Jira Issue OCPBUGS-61584 has been moved to the MODIFIED state.

In response to this:

openshift/kubernetes-apiserver#70
openshift/kubernetes-apiserver#58

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-merge-robot
Copy link
Contributor

Fix included in accepted release 4.17.0-0.nightly-2025-09-25-030800

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. backport-risk-assessed Indicates a PR to a release branch has been evaluated and considered safe to accept. 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 verified-later
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants