Skip to content

NO-ISSUE: rebase-main-4.19.0-0.nightly-2025-02-26-050226_amd64-2025-02-26_arm64-2025-02-27 #4612

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.

Sign up for GitHub

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

Jump to bottom
Merged
merged 5 commits into from
Feb 28, 2025
Merged

NO-ISSUE: rebase-main-4.19.0-0.nightly-2025-02-26-050226_amd64-2025-02-26_arm64-2025-02-27 #4612

merged 5 commits into from
Feb 28, 2025

Conversation

microshift-rebase-script[bot]
Copy link
Contributor

amd64: 4.19.0-0.nightly-2025-02-26-050226
arm64: 4.19.0-0.nightly-arm64-2025-02-27-211136
prow job: https://prow.ci.openshift.org/view/gs/origin-ci-test/logs/periodic-ci-openshift-microshift-main-rebase-on-nightlies/1895323291569098752

  • oc image-arm64 b2f8216d285c2ec38acc7aa8c41a5689062b61c8 to 514a4581b8a6b8b0aef5832e50adf1037ffd9566

    • cbecb375 2025-02-25T15:41:27-08:00 pkg/cli/admin/upgrade/recommend: Configureable version for test fixtures
    • f7378ff1 2025-02-25T15:41:27-08:00 pkg/cli/admin/upgrade/recommend/examples/README: Catch up with --show-outdated-releases
    • 04ddd208 2025-02-25T10:45:16+03:00 Bump indirect dependency go-jose to 4.0.5 version

  • kubernetes image-arm64 efd4d776fd6178a96e55e12bc035d4425febfe24 to 0d5e1846a2163960301184f0582fcfb3e805bee1

    • 33d7ffce5 2025-02-26T09:21:03-05:00 UPSTREAM: : admission: validate minimumKubeletVersion
    • 91780bc84 2025-02-26T09:21:03-05:00 UPSTREAM: : crdvalidation: move latency profile file to be agnostic of field

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

@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 28, 2025
@openshift-ci-robot
Copy link

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

In response to this:

amd64: 4.19.0-0.nightly-2025-02-26-050226
arm64: 4.19.0-0.nightly-arm64-2025-02-27-211136
prow job: https://prow.ci.openshift.org/view/gs/origin-ci-test/logs/periodic-ci-openshift-microshift-main-rebase-on-nightlies/1895323291569098752

  • oc image-arm64 b2f8216d285c2ec38acc7aa8c41a5689062b61c8 to 514a4581b8a6b8b0aef5832e50adf1037ffd9566

  • cbecb375 2025-02-25T15:41:27-08:00 pkg/cli/admin/upgrade/recommend: Configureable version for test fixtures

  • f7378ff1 2025-02-25T15:41:27-08:00 pkg/cli/admin/upgrade/recommend/examples/README: Catch up with --show-outdated-releases

  • 04ddd208 2025-02-25T10:45:16+03:00 Bump indirect dependency go-jose to 4.0.5 version

  • kubernetes image-arm64 efd4d776fd6178a96e55e12bc035d4425febfe24 to 0d5e1846a2163960301184f0582fcfb3e805bee1

  • 33d7ffce5 2025-02-26T09:21:03-05:00 UPSTREAM: : admission: validate minimumKubeletVersion

  • 91780bc84 2025-02-26T09:21:03-05:00 UPSTREAM: : crdvalidation: move latency profile file to be agnostic of field

/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 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. labels Feb 28, 2025
@microshift-rebase-script microshift-rebase-script
Copy link
Contributor Author

Extra messages:

  • Deleted following branches: rebase-release-4.15-4.15.0-0.nightly-2025-02-20-001209_amd64-2025-02-20_arm64-2025-02-21

@openshift-ci openshift-ci bot added 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 28, 2025
@openshift-ci openshift-ci bot requested review from ggiguash and pacevedom February 28, 2025 04:20
@openshift-ci OpenShift CI
Copy link
Contributor

openshift-ci bot commented Feb 28, 2025

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

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

@eslutsky
Copy link
Contributor

/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Feb 28, 2025
@openshift-ci OpenShift CI
Copy link
Contributor

openshift-ci bot commented Feb 28, 2025

[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

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 28, 2025
@openshift-merge-bot openshift-merge-bot bot merged commit 994a445 into main Feb 28, 2025
13 checks passed
@openshift-merge-bot openshift-merge-bot bot deleted the rebase-main-4.19.0-0.nightly-2025-02-26-050226_amd64-2025-02-26_arm64-2025-02-27 branch February 28, 2025 07:40
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@ggiguash ggiguash Awaiting requested review from ggiguash

@pacevedom pacevedom Awaiting requested review from pacevedom

Assignees

@eslutsky eslutsky

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
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
2 participants
@openshift-ci-robot @eslutsky