Skip to content

NO-ISSUE: rebase-4.14.0-0.nightly-2023-11-20-172527_amd64-2023-11-20_arm64-2023-11-21#2628

Merged
openshift-merge-bot[bot] merged 4 commits intorelease-4.14from
rebase-4.14.0-0.nightly-2023-11-20-172527_amd64-2023-11-20_arm64-2023-11-21
Nov 21, 2023
Merged

NO-ISSUE: rebase-4.14.0-0.nightly-2023-11-20-172527_amd64-2023-11-20_arm64-2023-11-21#2628
openshift-merge-bot[bot] merged 4 commits intorelease-4.14from
rebase-4.14.0-0.nightly-2023-11-20-172527_amd64-2023-11-20_arm64-2023-11-21

Conversation

@microshift-rebase-script
Copy link
Contributor

@microshift-rebase-script microshift-rebase-script bot commented Nov 21, 2023

amd64: 4.14.0-0.nightly-2023-11-20-172527
arm64: 4.14.0-0.nightly-arm64-2023-11-21-005956
prow job: https://prow.ci.openshift.org/view/gs/origin-ci-test/logs/periodic-ci-openshift-microshift-release-4.14-rebase-on-nightlies/1726827985819930624

  • machine-config-operator embedded-component f57144e1ffc7904dd34722da07ccb471adaa8954 to a6cdd850c44f8809b10a057202ccd502a21c33fc
    • b4e2e4f0 2023-11-13T15:21:41+01:00 CNV-34844: workaround nmstate bug by configuring ipv{4,6} addresses

/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 Nov 21, 2023
@openshift-ci-robot
Copy link

openshift-ci-robot commented Nov 21, 2023

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

Details

In response to this:

amd64: 4.14.0-0.nightly-2023-11-20-172527
arm64: 4.14.0-0.nightly-arm64-2023-11-21-005956
prow job: https://prow.ci.openshift.org/view/gs/origin-ci-test/logs/periodic-ci-openshift-microshift-release-4.14-rebase-on-nightlies/1726827985819930624

  • machine-config-operator embedded-component f57144e1ffc7904dd34722da07ccb471adaa8954 to a6cdd850c44f8809b10a057202ccd502a21c33fc
  • b4e2e4f0 2023-11-13T15:21:41+01:00 CNV-34844: workaround nmstate bug by configuring ipv{4,6} addresses

/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 kubernetes/test-infra 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 Nov 21, 2023
@openshift-ci openshift-ci bot requested review from copejon and ggiguash November 21, 2023 05:08
@pacevedom
Copy link
Contributor

/test microshift-metal-tests

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Nov 21, 2023

@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.

Copy link
Contributor

@pacevedom pacevedom left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Nov 21, 2023
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Nov 21, 2023

[APPROVALNOTIFIER] This PR is APPROVED

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

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 Nov 21, 2023
@openshift-merge-bot openshift-merge-bot bot merged commit 5d8fa1a into release-4.14 Nov 21, 2023
@openshift-merge-bot openshift-merge-bot bot deleted the rebase-4.14.0-0.nightly-2023-11-20-172527_amd64-2023-11-20_arm64-2023-11-21 branch November 21, 2023 10:39
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