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-8314: bump to k8s 1.23.17 #1497

Merged
merged 169 commits into from Mar 22, 2023

Conversation

jerpeter1
Copy link
Member

No description provided.

prateekgogia and others added 30 commits July 19, 2022 17:38
Co-authored-by: silenceper <silenceper@gmail.com>
Signed-off-by: Zhecheng Li <zhechengli@microsoft.com>
Fix the one path where boundNextDispatchLocked was not being called
after modifying a queue.

Also check for negative work in a request.

These are motivated by
kubernetes#112169 but I do not
have a way to reproduce it and so can not check that these changes
actually remove that symptom.  But these changes are good anyway.
Currently, when kubelet will try to compress the logs to a .gz file,
it will attempt to rename the archive before closing its file handles,
which results in an error on Windows.

This addresses the issue mentioned above.
For example, we have two filesystems, one is embedded into another:

/a/test		# first filesystem with a directory "/a/test/b2"
/a/test/b2	# not auto mounted yet second filesystem, notice "/a/test/b2" is
	        # a new directory on this filesystem after this filesystem is mounted

For subpath mount "/a/test/b2",  `openat("/a/test", "b2")` gets directory "b2" on the first
filesystem, then "mount -c" will use this wrong directory as source directory.

`fstatat("/a/test", "b2/")` forces triggering auto mount of second filesystem, so
`openat("/a/test", "b2")` gets correct source directory for "mount -c".

This fixes issue kubernetes#110818 (comment)

References:

1. https://man7.org/linux/man-pages/man2/openat.2.html

   If pathname refers to an automount point that has not yet
   been triggered, so no other filesystem is mounted on it,
   then the call returns a file descriptor referring to the
   automount directory without triggering a mount.

2. https://man7.org/linux/man-pages/man2/open_by_handle_at.2.html

   name_to_handle_at() does not trigger a mount when the final
   component of the pathname is an automount point.  When a
   filesystem supports both file handles and automount points, a
   name_to_handle_at() call on an automount point will return with
   error EOVERFLOW without having increased handle_bytes.  This can
   happen since Linux 4.13 with NFS when accessing a directory which
   is on a separate filesystem on the server.  In this case, the
   automount can be triggered by adding a "/" to the end of the
   pathname.
Signed-off-by: Marko Mudrinić <mudrinic.mare@gmail.com>
[release-1.23] CHANGELOG-1.23: Add missing changes for 1.23.12
…ck-of-#112557-upstream-release-1.23

Automated cherry pick of kubernetes#112557: Fix list estimator for lists that are executed as gets
…pick-of-#111428-upstream-release-1.23

Automated cherry pick of kubernetes#111428: Skip "instance not found" error for LB backend address pools
…k-of-#112403-upstream-release-1.23

Automated cherry pick of kubernetes#112403: Call SetupDevice only if Volume is not globally Mounted
…-pick-of-#110973-upstream-release-1.23

Automated cherry pick of kubernetes#110973: Make sure auto-mounted subpath mount source is already
…ck-of-#109114-upstream-release-1.23-1661519732

client-go: make retry in Request thread safe
…k-of-#111549-upstream-release-1.23

Automated cherry pick of kubernetes#111549: Fixes kubelet log compression on Windows
Change-Id: I8a860d336060848fe71b46991ac148ff704f7b60
…changed.

Signed-off-by: MartinForReal <fanshangxiang@gmail.com>
…rry-pick-of-#112785-upstream-release-1.23

Automated cherry pick of kubernetes#112785: service update event should be triggered when appProtocol in
@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Mar 15, 2023
@gangwgr
Copy link

gangwgr commented Mar 15, 2023

/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 15, 2023
@openshift-ci
Copy link

openshift-ci bot commented Mar 15, 2023

@soltysh: Overrode contexts on behalf of soltysh: ci/prow/e2e-aws-fips, ci/prow/k8s-e2e-gcp

In response to this:

/override ci/prow/e2e-aws-fips
this failure is known problem being taken care of in #1510
/override ci/prow/k8s-e2e-gcp
the single failure in that job is being debugged in #1511

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

openshift-ci bot commented Mar 15, 2023

[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 Mar 15, 2023
@openshift-ci-robot
Copy link

/retest-required

Remaining retests: 0 against base HEAD a57ef08 and 2 for PR HEAD 57b6a49 in total

@vfreex
Copy link

vfreex commented Mar 16, 2023

/retest-required

@soltysh
Copy link
Member

soltysh commented Mar 16, 2023

/test e2e-azure-upgrade

1 similar comment
@soltysh
Copy link
Member

soltysh commented Mar 16, 2023

/test e2e-azure-upgrade

@vfreex
Copy link

vfreex commented Mar 17, 2023

/retest-required

@soltysh
Copy link
Member

soltysh commented Mar 17, 2023

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

/test e2e-gcp

@openshift-ci
Copy link

openshift-ci bot commented Mar 17, 2023

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

/test e2e-gcp

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.

@jerpeter1
Copy link
Member Author

/retest-required

1 similar comment
@jerpeter1
Copy link
Member Author

/retest-required

@openshift-ci-robot
Copy link

/retest-required

Remaining retests: 0 against base HEAD a57ef08 and 2 for PR HEAD 57b6a49 in total

@jerpeter1
Copy link
Member Author

/test e2e-aws-cgroupsv2
/test e2e-gcp

@soltysh
Copy link
Member

soltysh commented Mar 21, 2023

/test e2e-gcp

@openshift-ci
Copy link

openshift-ci bot commented Mar 21, 2023

@jerpeter1: The following test 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 57b6a49 link true /test verify-commits

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.

@soltysh
Copy link
Member

soltysh commented Mar 22, 2023

/test e2e-gcp

@soltysh
Copy link
Member

soltysh commented Mar 22, 2023

/override ci/prow/e2e-aws-cgroupsv2
this is not related and fails pretty everywhere else

@openshift-ci
Copy link

openshift-ci bot commented Mar 22, 2023

@soltysh: Overrode contexts on behalf of soltysh: ci/prow/e2e-aws-cgroupsv2

In response to this:

/override ci/prow/e2e-aws-cgroupsv2
this is not related and fails pretty everywhere else

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-merge-robot openshift-merge-robot merged commit 16bcd69 into openshift:release-4.10 Mar 22, 2023
3 checks passed
@openshift-ci-robot
Copy link

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

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

In response to this:

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

[ART PR BUILD NOTIFIER]

This PR has been included in build openshift-enterprise-pod-container-v4.10.0-202305011254.p0.g16bcd69.assembly.stream for distgit openshift-enterprise-pod.
All builds following this will include this PR.

@openshift-bot
Copy link

[ART PR BUILD NOTIFIER]

This PR has been included in build openshift-enterprise-hyperkube-container-v4.10.0-202305011254.p0.g16bcd69.assembly.stream for distgit openshift-enterprise-hyperkube.
All builds following this will include this PR.

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. bugzilla/valid-bug Indicates that a referenced Bugzilla bug is valid for the branch this PR is targeting. cherry-pick-approved Indicates a cherry-pick PR into a release branch has been approved by the release branch manager. jira/severity-important Referenced Jira bug's severity is important for the branch this PR is targeting. 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