Skip to content
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

NO-ISSUE: rebase-release-4.15-4.15.0-0.nightly-2024-02-14-214710_amd64-2024-02-14_arm64-2024-02-14 #3020

Conversation

microshift-rebase-script[bot]
Copy link
Contributor

amd64: 4.15.0-0.nightly-2024-02-14-214710
arm64: 4.15.0-0.nightly-arm64-2024-02-14-183347
prow job: https://prow.ci.openshift.org/view/gs/origin-ci-test/logs/periodic-ci-openshift-microshift-release-4.15-rebase-on-nightlies/1757993295406960640

  • machine-config-operator embedded-component 6305fca334948e9ed37b078884d96051f8859b99 to c7981fcb54fcae3976818479a01f19f3fef40cd9

    • 6f4f363a 2024-02-06T03:22:08+00:00 Add existing kubeletconfig suffix key
  • operator-framework-olm embedded-component 711336ec8ded4b51cc93d5d68b152e5db71aa9a6 to 0e8b957251ce3edb82ca8d9139380b18df1fe55c

/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 15, 2024
@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-02-14-214710
arm64: 4.15.0-0.nightly-arm64-2024-02-14-183347
prow job: https://prow.ci.openshift.org/view/gs/origin-ci-test/logs/periodic-ci-openshift-microshift-release-4.15-rebase-on-nightlies/1757993295406960640

  • machine-config-operator embedded-component 6305fca334948e9ed37b078884d96051f8859b99 to c7981fcb54fcae3976818479a01f19f3fef40cd9

  • 6f4f363a 2024-02-06T03:22:08+00:00 Add existing kubeletconfig suffix key

  • operator-framework-olm embedded-component 711336ec8ded4b51cc93d5d68b152e5db71aa9a6 to 0e8b957251ce3edb82ca8d9139380b18df1fe55c

  • 59dcec3e 2024-02-13T12:59:45+01:00 fix crd data loss e2e test (USHIFT-2798: MicroShift bootc pilot  #3173)

/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 15, 2024
@openshift-ci openshift-ci bot requested review from copejon and jogeo February 15, 2024 05:08
Copy link
Contributor

openshift-ci bot commented Feb 15, 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/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 Feb 15, 2024
Copy link
Contributor

openshift-ci bot commented Feb 15, 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 Feb 15, 2024
@openshift-merge-bot openshift-merge-bot bot merged commit 8413173 into release-4.15 Feb 15, 2024
9 checks passed
@openshift-merge-bot openshift-merge-bot bot deleted the rebase-release-4.15-4.15.0-0.nightly-2024-02-14-214710_amd64-2024-02-14_arm64-2024-02-14 branch February 15, 2024 08:25
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.

None yet

2 participants