Skip to content
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.

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

OCPBUGS-29662: Update to kubernetes 1.27.11 #1890

Merged
merged 15 commits into from Mar 8, 2024

Conversation

jerpeter1
Copy link
Member

danwinship and others added 15 commits January 16, 2024 12:51
ServicePortMap.Update() and EndpointsMap.Update() were just a tiny
wrappers around the corresponding apply() methods, which had no other
callers. So squash them together.

(Also fix the variable naming in ServicePortMap.Update() to match
other methods.)
…ults

This fixes a race condition where the tracker could be updated in
between us calling .PendingChanges() and .Update().
…n kube-system/kubelet-config ConfigMap does not respect user patch"
…ck-of-#123093-upstream-release-1.27

Automated cherry pick of kubernetes#123093: Revert "kubeadm: fix a bug where the uploaded kubelet
…k-of-#122204-upstream-release-1.27

Automated cherry pick of kubernetes#122204: Fix race condition in iptables partial sync handling
…ck-of-#122704-upstream-release-1.27

Automated cherry pick of kubernetes#122704: If a pvc has an empty storageclass name, don't try to assign
…y-pick-of-#122750-upstream-release-1.27

Automated cherry pick of kubernetes#122750: Add processStartTime in metrics/slis
…-iptables to v0.4.5

Signed-off-by: cpanato <ctadeu@gmail.com>
[release-1.27] [go] Bump images, dependencies and versions to go 1.21.7 / distroless-iptables to v0.4.5
Kubernetes official release v1.27.11
@openshift-ci-robot openshift-ci-robot added backports/unvalidated-commits Indicates that not all commits come to merged upstream PRs. 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 Feb 20, 2024
@openshift-ci-robot
Copy link

@jerpeter1: This pull request references Jira Issue OCPBUGS-29662, which is invalid:

  • expected dependent Jira Issue OCPBUGS-29661 to be in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but it is New instead
  • expected dependent Jira Issue OCPBUGS-29661 to target a version in 4.15.0, but it targets "4.15.z" 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:

/assign @soltysh @suleymanakbas91

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
Copy link

@jerpeter1: the contents of this pull request could not be automatically validated.

The following commits could not be validated and must be approved by a top-level approver:

Comment /validate-backports to re-evaluate validity of the upstream PRs, for example when they are merged upstream.

@openshift-ci openshift-ci bot added the vendor-update Touching vendor dir or related files label Feb 20, 2024
Copy link
Member

@soltysh soltysh 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

/remove-label backports/unvalidated-commits
/remove-label backports/validated-commits

@openshift-ci openshift-ci bot removed the backports/unvalidated-commits Indicates that not all commits come to merged upstream PRs. label Feb 20, 2024
Copy link

openshift-ci bot commented Feb 20, 2024

@soltysh: Those labels are not set on the issue: backports/validated-commits

In response to this:

/lgtm
/approve

/remove-label backports/unvalidated-commits
/remove-label backports/validated-commits

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.

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Feb 20, 2024
Copy link

openshift-ci bot commented Feb 20, 2024

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: jerpeter1, soltysh

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 Feb 20, 2024
@soltysh
Copy link
Member

soltysh commented Feb 20, 2024

/override ci/prow/verify-commits
this never passes on k8s bump

Copy link

openshift-ci bot commented Feb 20, 2024

@soltysh: Overrode contexts on behalf of soltysh: ci/prow/verify-commits

In response to this:

/override ci/prow/verify-commits
this never passes on k8s bump

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.

@soltysh
Copy link
Member

soltysh commented Feb 21, 2024

/label backports/validated-commits

@openshift-ci openshift-ci bot added the backports/validated-commits Indicates that all commits come to merged upstream PRs. label Feb 21, 2024
@soltysh
Copy link
Member

soltysh commented Mar 7, 2024

Manually overriding valid-bug since #1891 merged
/remove-label jira/invalid-bug
/label jira/valid-bug
/label backport-risk-assessed
/test e2e-azure-ovn-upgrade

@openshift-ci openshift-ci bot added jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. backport-risk-assessed Indicates a PR to a release branch has been evaluated and considered safe to accept. and removed jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. labels Mar 7, 2024
@gangwgr
Copy link

gangwgr commented Mar 7, 2024

/label cherry-pick-approved

@openshift-ci openshift-ci bot added the cherry-pick-approved Indicates a cherry-pick PR into a release branch has been approved by the release branch manager. label Mar 7, 2024
@soltysh
Copy link
Member

soltysh commented Mar 7, 2024

/override ci/prow/verify-commits
it fails on k8s bump PRs

Copy link

openshift-ci bot commented Mar 7, 2024

@soltysh: Overrode contexts on behalf of soltysh: ci/prow/verify-commits

In response to this:

/override ci/prow/verify-commits
it fails on k8s bump PRs

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.

@openshift-ci-robot
Copy link

/retest-required

Remaining retests: 0 against base HEAD c79e5e2 and 2 for PR HEAD 50ea65f in total

@soltysh
Copy link
Member

soltysh commented Mar 8, 2024

/override ci/prow/unit
it's a known failure, tracked elsewhere

Copy link

openshift-ci bot commented Mar 8, 2024

@soltysh: Overrode contexts on behalf of soltysh: ci/prow/unit

In response to this:

/override ci/prow/unit
it's a known failure, tracked elsewhere

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.

Copy link

openshift-ci bot commented Mar 8, 2024

@jerpeter1: 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/verify-commits 50ea65f link unknown /test verify-commits
ci/prow/unit 50ea65f link true /test unit

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

@openshift-merge-bot openshift-merge-bot bot merged commit d8e449a into openshift:release-4.14 Mar 8, 2024
23 checks passed
@openshift-ci-robot
Copy link

@jerpeter1: Jira Issue OCPBUGS-29662: All pull requests linked via external trackers have merged:

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

In response to this:

/assign @soltysh @suleymanakbas91

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

[ART PR BUILD NOTIFIER]

This PR has been included in build openshift-enterprise-pod-container-v4.14.0-202403081110.p0.gd8e449a.assembly.stream.el8 for distgit openshift-enterprise-pod.
All builds following this will include this PR.

@openshift-merge-robot
Copy link

Fix included in accepted release 4.14.0-0.nightly-2024-03-08-180353

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. backports/validated-commits Indicates that all commits come to merged upstream PRs. 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. vendor-update Touching vendor dir or related files
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet