Skip to content

Conversation

microshift-rebase-script[bot]
Copy link
Contributor

@microshift-rebase-script microshift-rebase-script bot commented Oct 1, 2024

amd64: 4.18.0-0.nightly-2024-09-30-161817
arm64: 4.18.0-0.nightly-arm64-2024-10-01-011601
prow job: https://prow.ci.openshift.org/view/gs/origin-ci-test/logs/periodic-ci-openshift-microshift-main-rebase-on-nightlies/1840965180058505216

  • cluster-network-operator embedded-component 4eec256fe4565434ccf0f4b44ee74d24c40f6850 to 1773dcfb930d32b51580b1fa7158d9cbbe7b4274

    • 9a56d23 2024-09-26T18:15:29+01:00 HOSTEDCP-1981: Add controlplane cli image envar for use with hypershift
  • machine-config-operator embedded-component 56346ad6c09bb86d6e4b09850dde24b076d101d9 to 8dc705d80b2ab269e6346ebb5d35783fe96c32a3

    • 669db136 2024-09-23T11:57:26-04:00 openstack: fix non-old systemd compatible unit
  • operator-framework-olm embedded-component fccb629eb860057467a9287b23f5f8d2295aead9 to fbd00789eda3c50c35be61d04508e2230b17bffa

/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 Oct 1, 2024
@openshift-ci-robot
Copy link

openshift-ci-robot commented Oct 1, 2024

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

In response to this:

amd64: 4.18.0-0.nightly-2024-09-30-161817
arm64: 4.18.0-0.nightly-arm64-2024-10-01-011601
prow job: https://prow.ci.openshift.org/view/gs/origin-ci-test/logs/periodic-ci-openshift-microshift-main-rebase-on-nightlies/1840965180058505216

  • cluster-network-operator embedded-component 4eec256fe4565434ccf0f4b44ee74d24c40f6850 to 1773dcfb930d32b51580b1fa7158d9cbbe7b4274

  • 9a56d23 2024-09-26T18:15:29+01:00 HOSTEDCP-1981: Add controlplane cli image envar for use with hypershift

  • machine-config-operator embedded-component 56346ad6c09bb86d6e4b09850dde24b076d101d9 to 8dc705d80b2ab269e6346ebb5d35783fe96c32a3

  • 669db136 2024-09-23T11:57:26-04:00 openstack: fix non-old systemd compatible unit

  • operator-framework-olm embedded-component fccb629eb860057467a9287b23f5f8d2295aead9 to fbd00789eda3c50c35be61d04508e2230b17bffa

  • c136cee5 2024-09-29T13:27:28+00:00 Improve InstallPlan error handling (NO-ISSUE: rebase-main-4.17.0-0.nightly-2024-05-24-193308_amd64-2024-05-24_arm64-2024-05-28 #3404)

/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 Oct 1, 2024
Copy link
Contributor Author

Extra messages:

  • Deleted following branches: rebase-4.14.0-0.nightly-2024-09-29-193638_amd64-2024-09-29_arm64-2024-09-29, rebase-main-4.18.0-0.nightly-2024-09-29-150556_amd64-2024-09-29_arm64-2024-09-29, rebase-release-4.17-4.17.0-0.nightly-2024-09-29-173421_amd64-2024-09-29_arm64-2024-09-29

@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 Oct 1, 2024
@openshift-ci openshift-ci bot requested review from jerpeter1 and pacevedom October 1, 2024 04:39
Copy link
Contributor

openshift-ci bot commented Oct 1, 2024

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

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 Oct 1, 2024
Copy link
Contributor

openshift-ci bot commented Oct 1, 2024

[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

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 Oct 1, 2024
@openshift-merge-bot openshift-merge-bot bot merged commit 286c597 into main Oct 1, 2024
13 checks passed
@openshift-merge-bot openshift-merge-bot bot deleted the rebase-main-4.18.0-0.nightly-2024-09-30-161817_amd64-2024-09-30_arm64-2024-10-01 branch October 1, 2024 07:56
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