Skip to content

NO-ISSUE: rebase-release-4.15-4.15.0-0.nightly-2024-01-31-130653_amd64-2024-01-31_arm64-2024-01-30#2959

Merged
openshift-merge-bot[bot] merged 4 commits into
release-4.15from
rebase-release-4.15-4.15.0-0.nightly-2024-01-31-130653_amd64-2024-01-31_arm64-2024-01-30
Feb 1, 2024
Merged

NO-ISSUE: rebase-release-4.15-4.15.0-0.nightly-2024-01-31-130653_amd64-2024-01-31_arm64-2024-01-30#2959
openshift-merge-bot[bot] merged 4 commits into
release-4.15from
rebase-release-4.15-4.15.0-0.nightly-2024-01-31-130653_amd64-2024-01-31_arm64-2024-01-30

Conversation

@microshift-rebase-script
Copy link
Copy Markdown
Contributor

amd64: 4.15.0-0.nightly-2024-01-31-130653
arm64: 4.15.0-0.nightly-arm64-2024-01-30-193622
prow job: https://prow.ci.openshift.org/view/gs/origin-ci-test/logs/periodic-ci-openshift-microshift-release-4.15-rebase-on-nightlies/1752919841267781632

  • cluster-network-operator embedded-component d4ebd6af6ca400f22acd071532be50da7eae0f4b to a1ddc470cb58e599d16b7a7878cc37a339b47b0f
    • 5f4573e 2024-01-25T16:04:26+00:00 Add unit tests for function ensureMachineConfigPools
    • e5071b4 2024-01-25T16:04:26+00:00 Not update migration conditions when any MCP is updating

/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 1, 2024
@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.15.0-0.nightly-2024-01-31-130653
arm64: 4.15.0-0.nightly-arm64-2024-01-30-193622
prow job: https://prow.ci.openshift.org/view/gs/origin-ci-test/logs/periodic-ci-openshift-microshift-release-4.15-rebase-on-nightlies/1752919841267781632

  • cluster-network-operator embedded-component d4ebd6af6ca400f22acd071532be50da7eae0f4b to a1ddc470cb58e599d16b7a7878cc37a339b47b0f
  • 5f4573e 2024-01-25T16:04:26+00:00 Add unit tests for function ensureMachineConfigPools
  • e5071b4 2024-01-25T16:04:26+00:00 Not update migration conditions when any MCP is updating

/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 1, 2024
@openshift-ci openshift-ci Bot requested review from copejon and pacevedom February 1, 2024 05:09
@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci Bot commented Feb 1, 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.

@copejon
Copy link
Copy Markdown
Contributor

copejon commented Feb 1, 2024

/lgtm

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

openshift-ci Bot commented Feb 1, 2024

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: copejon, 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 1, 2024
@openshift-merge-bot openshift-merge-bot Bot merged commit 22902fb into release-4.15 Feb 1, 2024
@openshift-merge-bot openshift-merge-bot Bot deleted the rebase-release-4.15-4.15.0-0.nightly-2024-01-31-130653_amd64-2024-01-31_arm64-2024-01-30 branch February 1, 2024 19:34
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