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-31503: Bump to 1.28.8 #1926

Merged
merged 37 commits into from Apr 5, 2024

Conversation

bertinatto
Copy link
Member

/assign @soltysh

bzsuni and others added 30 commits February 12, 2024 17:43
Signed-off-by: bzsuni <bingzhe.sun@daocloud.io>
Signed-off-by: bzsuni <bingzhe.sun@daocloud.io>
Allow kubelet orphan cleanup to delete both files and empty directories as
subpath mount points.

A pod does not need to use a directory as a subpath, it can use a file
(unix domain socket, pipe, ...) too. Therefore the cleanup should use
`os.Remove` that deletes both files and empty directories.
Since v2.45, the `stress` subcommand was added and the CI issue was fixed:
- kubernetes/kubernetes PR 123258
- kubernetes/kubernetes PR 123284
- kubernetes/k8s.io     PR 6422

Signed-off-by: Akihiro Suda <akihiro.suda.cz@hco.ntt.co.jp>
(cherry picked from commit 5d861b6)
Signed-off-by: Akihiro Suda <akihiro.suda.cz@hco.ntt.co.jp>
agnhost now contains the stress functionality (PR 123258).

Fix issue 123146

Signed-off-by: Akihiro Suda <akihiro.suda.cz@hco.ntt.co.jp>
(cherry picked from commit e8b08cd)
Signed-off-by: Akihiro Suda <akihiro.suda.cz@hco.ntt.co.jp>
…s to flake.

Signed-off-by: TommyStarK <thomasmilox@gmail.com>
The code generation tools support verification only with the
--verify-only option, but this now fails because the files are nuked
ahead of time.

Signed-off-by: Stephen Kitt <skitt@redhat.com>
This fixes the race condition that could happen because
resize controller just finished volume expansiona and has only
finished marking PV and yet to mark PVC.

The workaround proposed here should not be necessary once
RecoverVolumeExpansionFailure goes GA/beta.
…88-1.28

[release-1.28] e2e_node: replace `registry.k8s.io/stress:v1` with agnhost
…k-of-#123603-upstream-release-1.28

Automated cherry pick of kubernetes#123603: fix UT failure TestPrintIPAddressList
…ck-of-#123069-kubernetes#123150-upstream-release-1.28

Automated cherry pick of kubernetes#123069: build etcd image v3.5.12
kubernetes#123150: etcd: Update to version 3.5.12
…-pick-of-#122703-upstream-release-1.28

Automated cherry pick of kubernetes#122703: dra: increase timeout in setupFakeDRADriverGRPCServer to
…-of-#123261-origin-release-1.28

Automated cherry pick of kubernetes#123261: codegen: don't nuke files if only verifying
…ck-of-#123055-upstream-release-1.28

Automated cherry pick of kubernetes#123055: Fix race condition between external-resizer and kubelet
…ick-of-#123052-upstream-release-1.28

Automated cherry pick of kubernetes#123052: Fix cleanup of file subpaths
…ick-of-#122999-upstream-release-1.28

Automated cherry pick of kubernetes#122999: fixing issue with GetCPUUsageNanoCores on Windows
…nd add a SeparateCacheWatchRPC feature flag to disable this behavior
This allows the state of restartable init containers to be transitioned
from terminated to non-terminated even for pods with RestartPolicyNever
or RestartPolicyOnFailure.
When the disruption controller updates the PDB status, it removes all conditions from the new status object and then re-adds the sufficient pods condition. Unfortunately, this behavior removes conditions set by other controllers, leading to multiple consecutive updates.
Therefore, this commit ensures that conditions are preserved during updates.
…-iptables to v0.4.6

Signed-off-by: cpanato <ctadeu@gmail.com>
Signed-off-by: Anish Ramasekar <anish.ramasekar@gmail.com>
Signed-off-by: Anish Ramasekar <anish.ramasekar@gmail.com>
[release-1.28] [go] Bump images, dependencies and versions to go 1.21.8 / distroless-iptables to v0.4.6
…ck-of-#123323-upstream-release-1.28

Automated cherry pick of kubernetes#123323: Validate restartable init container state transition
[1.28][CVE-2024-24786] Bump github.com/golang/protobuf v1.5.4, google.golang.org/protobuf v1.33.0
@openshift-ci openshift-ci bot added the backport-risk-assessed Indicates a PR to a release branch has been evaluated and considered safe to accept. label Apr 4, 2024
@gangwgr
Copy link

gangwgr commented Apr 4, 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 Apr 4, 2024
Copy link

openshift-ci bot commented Apr 4, 2024

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: bertinatto, 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 Apr 4, 2024
@openshift-ci-robot
Copy link

/retest-required

Remaining retests: 0 against base HEAD f1b5f6c and 2 for PR HEAD f82e7db in total

@soltysh
Copy link
Member

soltysh commented Apr 4, 2024

/retest-required

@soltysh
Copy link
Member

soltysh commented Apr 4, 2024

/test e2e-gcp-ovn-upgrade

@soltysh
Copy link
Member

soltysh commented Apr 4, 2024

/test k8s-e2e-gcp-ovn

@soltysh
Copy link
Member

soltysh commented Apr 4, 2024

/hold
there are issues in CI

@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 Apr 4, 2024
@flavianmissi
Copy link
Member

/retest

@soltysh
Copy link
Member

soltysh commented Apr 5, 2024

/hold cancel

1 similar comment
@soltysh
Copy link
Member

soltysh commented Apr 5, 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 Apr 5, 2024
@openshift-ci-robot
Copy link

/retest-required

Remaining retests: 0 against base HEAD c1f5b34 and 1 for PR HEAD f82e7db in total

Copy link

openshift-ci bot commented Apr 5, 2024

@bertinatto: 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/e2e-agnostic-ovn-cmd f82e7db link false /test e2e-agnostic-ovn-cmd

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 6b4a380 into openshift:release-4.15 Apr 5, 2024
22 of 23 checks passed
@openshift-ci-robot
Copy link

@bertinatto: Jira Issue OCPBUGS-31503: All pull requests linked via external trackers have merged:

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

In response to this:

/assign @soltysh

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.15.0-202404051341.p0.g6b4a380.assembly.stream.el9 for distgit openshift-enterprise-pod.
All builds following this will include this PR.

@openshift-merge-robot
Copy link

Fix included in accepted release 4.15.0-0.nightly-2024-04-07-120427

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