Skip to content

NO-ISSUE: rebase-main-4.16.0-0.nightly-2024-02-26-013420_amd64-2024-02-26_arm64-2024-02-29#3086

Merged
openshift-merge-bot[bot] merged 5 commits intomainfrom
rebase-main-4.16.0-0.nightly-2024-02-26-013420_amd64-2024-02-26_arm64-2024-02-29
Feb 29, 2024
Merged

NO-ISSUE: rebase-main-4.16.0-0.nightly-2024-02-26-013420_amd64-2024-02-26_arm64-2024-02-29#3086
openshift-merge-bot[bot] merged 5 commits intomainfrom
rebase-main-4.16.0-0.nightly-2024-02-26-013420_amd64-2024-02-26_arm64-2024-02-29

Conversation

@microshift-rebase-script
Copy link
Copy Markdown
Contributor

amd64: 4.16.0-0.nightly-2024-02-26-013420
arm64: 4.16.0-0.nightly-arm64-2024-02-29-010347
prow job: https://prow.ci.openshift.org/view/gs/origin-ci-test/logs/periodic-ci-openshift-microshift-main-rebase-on-nightlies/1763066601487208448

  • oc image-arm64 a36a8e36c0eaec9c6905becac2f5a941b78b5123 to 91ba77aaeedb6810a30eaf7418ee76e9fb45f8ee

    • 846ce4d7 2024-02-26T10:16:41+03:00 Extract oc also for linux/ppc64le
    • 6e766588 2024-02-13T10:14:26+03:00 Revert "Revert "NO-JIRA: Bump k8s dependencies to 1.29.1""
  • router image-arm64 4c436c604e093a8cadcee72c8a45b214e24f40ac to cf0442b1850b94b4bf123eb0a37b5491513e0b70

    • 34cf2a7 2024-02-14T13:53:53+00:00 container builds: add socat package
    • 6c58af9 2024-02-14T13:49:35+00:00 Revert "Merge pull request Populate the the NO_PROXY environment #561 from dgoodwin/revert-551-1707829993043"
  • kube-rbac-proxy image-arm64 6ea01c5c6e0c56d07b66c90e27caeda58b4ce872 to 49a835a819d735f5e0b059471f9c1ec0b447c995

  • kubernetes image-arm64 2eba5a9a34b4e3ac7f3cb5f03cf04282f7464356 to 6116860ab8000581009cd889e4cc1a1985207ddf

    • 1a9c833e8 2024-02-26T14:11:59-05:00 UPSTREAM: 123055: Fix race condition between resizer and kubelet

/label tide/merge-method-squash
/label cherry-pick-approved
/label backport-risk-assessed
/label jira/valid-bug

@openshift-ci-robot
Copy link
Copy Markdown

@microshift-rebase-script[bot]: This pull request explicitly references no jira issue.

Details

In response to this:

amd64: 4.16.0-0.nightly-2024-02-26-013420
arm64: 4.16.0-0.nightly-arm64-2024-02-29-010347
prow job: https://prow.ci.openshift.org/view/gs/origin-ci-test/logs/periodic-ci-openshift-microshift-main-rebase-on-nightlies/1763066601487208448

  • oc image-arm64 a36a8e36c0eaec9c6905becac2f5a941b78b5123 to 91ba77aaeedb6810a30eaf7418ee76e9fb45f8ee

  • 846ce4d7 2024-02-26T10:16:41+03:00 Extract oc also for linux/ppc64le

  • 6e766588 2024-02-13T10:14:26+03:00 Revert "Revert "NO-JIRA: Bump k8s dependencies to 1.29.1""

  • router image-arm64 4c436c604e093a8cadcee72c8a45b214e24f40ac to cf0442b1850b94b4bf123eb0a37b5491513e0b70

  • 34cf2a7 2024-02-14T13:53:53+00:00 container builds: add socat package

  • 6c58af9 2024-02-14T13:49:35+00:00 Revert "Merge pull request Populate the the NO_PROXY environment #561 from dgoodwin/revert-551-1707829993043"

  • kube-rbac-proxy image-arm64 6ea01c5c6e0c56d07b66c90e27caeda58b4ce872 to 49a835a819d735f5e0b059471f9c1ec0b447c995

  • ca2ca5b 2024-02-27T10:13:15+00:00 Updating kube-rbac-proxy-container image to be consistent with ART for 4.16 Reconciling with https://github.com/openshift/ocp-build-data/tree/7e3c85650685dcd13127a6bf27372dece89b5cc8/images/kube-rbac-proxy.yml

  • kubernetes image-arm64 2eba5a9a34b4e3ac7f3cb5f03cf04282f7464356 to 6116860ab8000581009cd889e4cc1a1985207ddf

  • 1a9c833e8 2024-02-26T14:11:59-05:00 UPSTREAM: 123055: Fix race condition between resizer and kubelet

/label tide/merge-method-squash
/label cherry-pick-approved
/label backport-risk-assessed
/label jira/valid-bug

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/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Feb 29, 2024
@openshift-ci openshift-ci bot added tide/merge-method-squash Denotes a PR that should be squashed by tide when it merges. cherry-pick-approved Indicates a cherry-pick PR into a release branch has been approved by the release branch manager. 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. labels Feb 29, 2024
@openshift-ci openshift-ci bot requested review from jogeo and pacevedom February 29, 2024 05:10
@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci bot commented Feb 29, 2024

@microshift-rebase-script[bot]: all tests passed!

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.

@eslutsky
Copy link
Copy Markdown
Contributor

/lgtm

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

openshift-ci bot commented Feb 29, 2024

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: eslutsky, microshift-rebase-script[bot]

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-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Feb 29, 2024
@openshift-merge-bot openshift-merge-bot bot merged commit 1efed78 into main Feb 29, 2024
@openshift-merge-bot openshift-merge-bot bot deleted the rebase-main-4.16.0-0.nightly-2024-02-26-013420_amd64-2024-02-26_arm64-2024-02-29 branch February 29, 2024 09:11
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. tide/merge-method-squash Denotes a PR that should be squashed by tide when it merges.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants