Skip to content

NO-ISSUE: rebase-release-4.15-4.15.0-0.nightly-2024-06-29-151522_amd64-2024-06-29_arm64-2024-06-30 #3558

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.

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

Conversation

microshift-rebase-script[bot]
Copy link
Contributor

amd64: 4.15.0-0.nightly-2024-06-29-151522
arm64: 4.15.0-0.nightly-arm64-2024-06-30-212316
prow job: https://prow.ci.openshift.org/view/gs/origin-ci-test/logs/periodic-ci-openshift-microshift-release-4.15-rebase-on-nightlies/1807625473379799040

  • machine-config-operator embedded-component eac63b92593461d31042085ab5d156bb680006ed to 98cf6fbede4d0ba3746bcaa5c13211e2e88faa86
    • 55c0ad08 2024-06-27T09:38:36+00:00 daemon/update: add workaround for OCPBUGS-33694
    • 16652746 2024-06-27T09:38:36+00:00 daemon/update: disable systemd unit before overwriting

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

@openshift-ci-robot
Copy link

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

In response to this:

amd64: 4.15.0-0.nightly-2024-06-29-151522
arm64: 4.15.0-0.nightly-arm64-2024-06-30-212316
prow job: https://prow.ci.openshift.org/view/gs/origin-ci-test/logs/periodic-ci-openshift-microshift-release-4.15-rebase-on-nightlies/1807625473379799040

  • machine-config-operator embedded-component eac63b92593461d31042085ab5d156bb680006ed to 98cf6fbede4d0ba3746bcaa5c13211e2e88faa86
  • 55c0ad08 2024-06-27T09:38:36+00:00 daemon/update: add workaround for OCPBUGS-33694
  • 16652746 2024-06-27T09:38:36+00:00 daemon/update: disable systemd unit before overwriting

/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-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Jul 1, 2024
@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 Jul 1, 2024
@openshift-ci openshift-ci bot requested review from copejon and jerpeter1 July 1, 2024 04:13
Copy link
Contributor

openshift-ci bot commented Jul 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.

@pmtk
Copy link
Member

pmtk commented Jul 1, 2024

/lgtm

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

openshift-ci bot commented Jul 1, 2024

[APPROVALNOTIFIER] This PR is APPROVED

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

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

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