Skip to content

NO-ISSUE: rebase-4.14.0-0.nightly-2025-02-14-202128_amd64-2025-02-14_arm64-2025-02-16#4557

Merged
openshift-merge-bot[bot] merged 5 commits intorelease-4.14from
rebase-4.14.0-0.nightly-2025-02-14-202128_amd64-2025-02-14_arm64-2025-02-16
Feb 17, 2025
Merged

NO-ISSUE: rebase-4.14.0-0.nightly-2025-02-14-202128_amd64-2025-02-14_arm64-2025-02-16#4557
openshift-merge-bot[bot] merged 5 commits intorelease-4.14from
rebase-4.14.0-0.nightly-2025-02-14-202128_amd64-2025-02-14_arm64-2025-02-16

Conversation

@microshift-rebase-script
Copy link
Contributor

amd64: 4.14.0-0.nightly-2025-02-14-202128
arm64: 4.14.0-0.nightly-arm64-2025-02-16-015909
prow job: https://prow.ci.openshift.org/view/gs/origin-ci-test/logs/periodic-ci-openshift-microshift-release-4.14-rebase-on-nightlies/1891336979275059200

  • cluster-kube-apiserver-operator embedded-component 1fe5769f9c30c79140484b11340f40e5208b5d2c to 9267f4543589ccb408d3e62fc0e35708d4b783df
    • f172ab3 2025-02-13T02:25:59+00:00 increase waitForFallbackDegradedConditionTimeout

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

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

Details

In response to this:

amd64: 4.14.0-0.nightly-2025-02-14-202128
arm64: 4.14.0-0.nightly-arm64-2025-02-16-015909
prow job: https://prow.ci.openshift.org/view/gs/origin-ci-test/logs/periodic-ci-openshift-microshift-release-4.14-rebase-on-nightlies/1891336979275059200

  • cluster-kube-apiserver-operator embedded-component 1fe5769f9c30c79140484b11340f40e5208b5d2c to 9267f4543589ccb408d3e62fc0e35708d4b783df
  • f172ab3 2025-02-13T02:25:59+00:00 increase waitForFallbackDegradedConditionTimeout

/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. 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 17, 2025
@openshift-ci openshift-ci bot requested review from pacevedom and pliurh February 17, 2025 04:17
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Feb 17, 2025

@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-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 17, 2025
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Feb 17, 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

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 17, 2025
@openshift-merge-bot openshift-merge-bot bot merged commit d409d44 into release-4.14 Feb 17, 2025
7 checks passed
@openshift-merge-bot openshift-merge-bot bot deleted the rebase-4.14.0-0.nightly-2025-02-14-202128_amd64-2025-02-14_arm64-2025-02-16 branch February 17, 2025 09:27
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