Skip to content

OCPBUGS-30304: cert rotation: Bump library-go to latest master#1653

Merged
openshift-merge-bot[bot] merged 2 commits intoopenshift:release-4.15from
vrutkovs:4.15-bump-library-go-mar05
Mar 7, 2024
Merged

OCPBUGS-30304: cert rotation: Bump library-go to latest master#1653
openshift-merge-bot[bot] merged 2 commits intoopenshift:release-4.15from
vrutkovs:4.15-bump-library-go-mar05

Conversation

@vrutkovs
Copy link
Copy Markdown
Contributor

@vrutkovs vrutkovs commented Mar 6, 2024

Cherrypick of #1651 on 4.15

@vrutkovs
Copy link
Copy Markdown
Contributor Author

vrutkovs commented Mar 6, 2024

/jira cherrypick OCPBUGS-30119

@openshift-ci-robot
Copy link
Copy Markdown

@vrutkovs: Jira Issue OCPBUGS-30119 has been cloned as Jira Issue OCPBUGS-30304. Will retitle bug to link to clone.
/retitle OCPBUGS-30304: [release-4.15] Bump library-go to latest master

Details

In response to this:

/jira cherrypick OCPBUGS-30119

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.15] Bump library-go to latest master OCPBUGS-30304: [release-4.15] Bump library-go to latest master Mar 6, 2024
@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Mar 6, 2024
@openshift-ci-robot
Copy link
Copy Markdown

@vrutkovs: This pull request references Jira Issue OCPBUGS-30304, which is invalid:

  • expected dependent Jira Issue OCPBUGS-30119 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.

Details

In response to this:

Cherrypick of #1651 on 4.15

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/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. label Mar 6, 2024
@openshift-ci openshift-ci Bot requested review from benluddy and dgrisonnet March 6, 2024 10:43
@vrutkovs vrutkovs force-pushed the 4.15-bump-library-go-mar05 branch 2 times, most recently from f0fe199 to f8ad97a Compare March 6, 2024 11:30
@mfojtik mfojtik added the backport-risk-assessed Indicates a PR to a release branch has been evaluated and considered safe to accept. label Mar 6, 2024
@mfojtik
Copy link
Copy Markdown
Contributor

mfojtik commented Mar 6, 2024

/lgtm

@openshift-ci openshift-ci Bot added lgtm Indicates that a PR is ready to be merged. approved Indicates a PR has been approved by an approver from all required OWNERS files. labels Mar 6, 2024
Comment thread go.mod Outdated
github.com/openshift/client-go v0.0.0-20230926161409-848405da69e1
github.com/openshift/library-go v0.0.0-20231130112926-2285c05489d7
github.com/openshift/client-go v0.0.0-20231218140158-47f6d749b9d9
github.com/openshift/library-go v0.0.0-20240305144041-18ee8279b4e3
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

/hold

this is bringing 4.16 library-go into 4.15 kube-apiserver-operator. Unless or until we need to update client-go from an unsupported level, this should remain in sync

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

My fault, openshift/library-go#1688 is 4.15 cherrypick for library-go

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

Updated

@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 Mar 6, 2024
@vrutkovs vrutkovs force-pushed the 4.15-bump-library-go-mar05 branch from f8ad97a to 1648c7f Compare March 6, 2024 17:58
@openshift-ci openshift-ci Bot removed the lgtm Indicates that a PR is ready to be merged. label Mar 6, 2024
@vrutkovs
Copy link
Copy Markdown
Contributor Author

vrutkovs commented Mar 6, 2024

/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 Mar 6, 2024
@wallylewis
Copy link
Copy Markdown

/jira refresh

@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 Mar 6, 2024
@openshift-ci-robot
Copy link
Copy Markdown

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

6 validation(s) were run on this bug
  • bug is open, matching expected state (open)
  • bug target version (4.15.z) matches configured target version for branch (4.15.z)
  • bug is in the state New, which is one of the valid states (NEW, ASSIGNED, POST)
  • dependent bug Jira Issue OCPBUGS-30119 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-30119 targets the "4.16.0" version, which is one of the valid target versions: 4.16.0
  • bug has dependents

Requesting review from QA contact:
/cc @wangke19

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-robot openshift-ci-robot removed the jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. label Mar 6, 2024
@openshift-ci openshift-ci Bot requested a review from wangke19 March 6, 2024 17:59
@sdodson
Copy link
Copy Markdown
Member

sdodson commented Mar 6, 2024

/retest-required

@vrutkovs vrutkovs force-pushed the 4.15-bump-library-go-mar05 branch from 1648c7f to 11f4bf6 Compare March 6, 2024 18:28
@sdodson sdodson added the cherry-pick-approved Indicates a cherry-pick PR into a release branch has been approved by the release branch manager. label Mar 6, 2024
@sdodson sdodson changed the title OCPBUGS-30304: [release-4.15] Bump library-go to latest master OCPBUGS-30304: cert rotation: Bump library-go to latest master Mar 6, 2024
Comment thread go.mod Outdated
Comment on lines +26 to +31
k8s.io/api v0.29.0
k8s.io/apiextensions-apiserver v0.29.0
k8s.io/apimachinery v0.29.0
k8s.io/apiserver v0.29.0
k8s.io/client-go v0.29.0
k8s.io/component-base v0.29.0
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Is this expected?

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

/hold

The bump commit looks like the result of bumping library-go to the current release-4.15 after bumping to 4.16 and tidying (all of the other dependency changes that came along with 4.16 were preserved). I see a one-line go.mod diff if I revert the other changes from accidental 4.16 bump first: benluddy@d1d767f#diff-33ef32bf6c23acb95f5902d7097b7a1d5128ca061167ec0716715b0b9eeaa5f6

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

Updated
/hold cancel

@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 Mar 6, 2024
@vrutkovs vrutkovs force-pushed the 4.15-bump-library-go-mar05 branch from 11f4bf6 to 774dfdd Compare March 7, 2024 06:22
@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 Mar 7, 2024
@vrutkovs vrutkovs force-pushed the 4.15-bump-library-go-mar05 branch from 774dfdd to 7f03359 Compare March 7, 2024 06:53
@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci Bot commented Mar 7, 2024

@vrutkovs: 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-aws-operator-disruptive-single-node 7f03359 link false /test e2e-aws-operator-disruptive-single-node
ci/prow/e2e-gcp-operator-single-node 7f03359 link false /test e2e-gcp-operator-single-node

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/test-infra repository. I understand the commands that are listed here.

@benluddy
Copy link
Copy Markdown
Contributor

benluddy commented Mar 7, 2024

/lgtm

@openshift-ci openshift-ci Bot added the lgtm Indicates that a PR is ready to be merged. label Mar 7, 2024
@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci Bot commented Mar 7, 2024

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: benluddy, mfojtik, vrutkovs

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-merge-bot openshift-merge-bot Bot merged commit 9fe0ab1 into openshift:release-4.15 Mar 7, 2024
@openshift-ci-robot
Copy link
Copy Markdown

@vrutkovs: Jira Issue OCPBUGS-30304: All pull requests linked via external trackers have merged:

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

Details

In response to this:

Cherrypick of #1651 on 4.15

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
Copy Markdown
Contributor

[ART PR BUILD NOTIFIER]

This PR has been included in build ose-cluster-kube-apiserver-operator-container-v4.15.0-202403071539.p0.g9fe0ab1.assembly.stream.el9 for distgit ose-cluster-kube-apiserver-operator.
All builds following this will include this PR.

@openshift-merge-robot
Copy link
Copy Markdown
Contributor

Fix included in accepted release 4.15.0-0.nightly-2024-03-07-174330

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. cherry-pick-approved Indicates a cherry-pick PR into a release branch has been approved by the release branch manager. 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.

Projects

None yet

Development

Successfully merging this pull request may close these issues.