Skip to content

[release-4.17] OCPBUGS-61584: Bump openshift/kubernetes-apiserver for etcd retry patches. #143

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.

Sign up for GitHub

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

Jump to bottom
Merged
merged 1 commit into from
Sep 19, 2025
Merged

[release-4.17] OCPBUGS-61584: Bump openshift/kubernetes-apiserver for etcd retry patches. #143

merged 1 commit into from
Sep 19, 2025
+123 −29

Conversation

benluddy
Copy link
Contributor

@benluddy
Copy link
Contributor Author

/hold

Need to update the replace directive once the fork PR merges.

@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 Sep 12, 2025
@benluddy benluddy force-pushed the release-4.17-2025-september-12-apiserver-bump branch from dfe2d54 to e2941b9 Compare September 12, 2025 14:58
@p0lyn0mial
Copy link
Contributor

/retest-required

1 similar comment
@p0lyn0mial
Copy link
Contributor

/retest-required

@p0lyn0mial
Copy link
Contributor

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

@benluddy benluddy changed the title Bump openshift/kubernetes-apiserver for etcd retry patches. [release-4.17] Bump openshift/kubernetes-apiserver for etcd retry patches. Sep 18, 2025
@benluddy benluddy force-pushed the release-4.17-2025-september-12-apiserver-bump branch from e2941b9 to 47aa7bd Compare September 18, 2025 14:33
@benluddy
Copy link
Contributor Author

/hold cancel

@openshift-ci openshift-ci bot removed the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Sep 18, 2025
@p0lyn0mial
Copy link
Contributor

/lgtm

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

openshift-ci bot commented Sep 18, 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.

@benluddy benluddy changed the title [release-4.17] Bump openshift/kubernetes-apiserver for etcd retry patches. [release-4.17] OCPBUGS-61584: Bump openshift/kubernetes-apiserver for etcd retry patches. Sep 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 Sep 18, 2025
@openshift-ci-robot
Copy link
Contributor

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

  • expected the bug to be in one of the following states: NEW, ASSIGNED, POST, but it is MODIFIED 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:

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.

@benluddy
Copy link
Contributor 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 18, 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

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 wangke19 September 18, 2025 20:28
@p0lyn0mial p0lyn0mial added 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. labels Sep 19, 2025
@openshift-ci OpenShift CI
Copy link

openshift-ci bot commented Sep 19, 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 19, 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 f970d59 into openshift:release-4.17 Sep 19, 2025
9 checks passed
@openshift-ci-robot openshift-ci-robot mentioned this pull request Sep 19, 2025
Merged
@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-bot
Copy link
Contributor

[ART PR BUILD NOTIFIER]

Distgit: ose-oauth-apiserver
This PR has been included in build ose-oauth-apiserver-container-v4.17.0-202509200037.p0.gf970d59.assembly.stream.el9.
All builds following this will include this PR.

@openshift-ci-robot openshift-ci-robot mentioned this pull request Sep 25, 2025
Merged
@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
Reviewers

@deads2k deads2k Awaiting requested review from deads2k

@p0lyn0mial p0lyn0mial Awaiting requested review from p0lyn0mial

@wangke19 wangke19 Awaiting requested review from wangke19

Assignees

@p0lyn0mial p0lyn0mial

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
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
5 participants
@benluddy @p0lyn0mial @openshift-ci-robot @openshift-bot @openshift-merge-robot