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.16-4.16.0-0.nightly-2024-05-23-173505_amd64-2024-05-23_arm64-2024-05-28 #3405

Conversation

microshift-rebase-script[bot]
Copy link
Contributor

amd64: 4.16.0-0.nightly-2024-05-23-173505
arm64: 4.16.0-0.nightly-arm64-2024-05-28-145249
prow job: https://prow.ci.openshift.org/view/gs/origin-ci-test/logs/periodic-ci-openshift-microshift-release-4.16-rebase-on-nightlies/1795681797380509696

  • oc image-arm64 2574bc791f17f3ca33d055e7645775e5db79159d to 12a2e98239d503af3e8e30a6fa9d0186c9524b77

    • 4292caa9 2024-05-23T21:11:34+00:00 upgrade status: upgrade -> update
    • 0614888c 2024-05-23T21:11:34+00:00 OCPBUGS-33903: Simplify output when not updating
    • bdd75eef 2024-05-18T21:23:01+00:00 adm update status: Fix target version field for install.
    • 12f58d05 2024-05-18T21:23:01+00:00 adm update status: Show information about upgrade target version
  • ovn-kubernetes image-arm64 9e6ce7fd4528f49b60cdbf280a247ff71f3a198e to d90fa545e17a27bdf253fa820a1d7552e3079465

    • 377a0dfc 2024-05-23T22:57:09+02:00 dns: fix deadlock in case of error

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

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

In response to this:

amd64: 4.16.0-0.nightly-2024-05-23-173505
arm64: 4.16.0-0.nightly-arm64-2024-05-28-145249
prow job: https://prow.ci.openshift.org/view/gs/origin-ci-test/logs/periodic-ci-openshift-microshift-release-4.16-rebase-on-nightlies/1795681797380509696

  • oc image-arm64 2574bc791f17f3ca33d055e7645775e5db79159d to 12a2e98239d503af3e8e30a6fa9d0186c9524b77

  • 4292caa9 2024-05-23T21:11:34+00:00 upgrade status: upgrade -> update

  • 0614888c 2024-05-23T21:11:34+00:00 OCPBUGS-33903: Simplify output when not updating

  • bdd75eef 2024-05-18T21:23:01+00:00 adm update status: Fix target version field for install.

  • 12f58d05 2024-05-18T21:23:01+00:00 adm update status: Show information about upgrade target version

  • ovn-kubernetes image-arm64 9e6ce7fd4528f49b60cdbf280a247ff71f3a198e to d90fa545e17a27bdf253fa820a1d7552e3079465

  • 377a0dfc 2024-05-23T22:57:09+02:00 dns: fix deadlock in case of error

/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 May 29, 2024
@openshift-ci openshift-ci bot requested review from jogeo and pliurh May 29, 2024 05:24
@pacevedom
Copy link
Contributor

/test microshift-metal-tests-arm

Copy link
Contributor

openshift-ci bot commented May 29, 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 May 29, 2024
Copy link
Contributor

openshift-ci bot commented May 29, 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 May 29, 2024
@openshift-merge-bot openshift-merge-bot bot merged commit 3c21564 into release-4.16 May 29, 2024
9 checks passed
@openshift-merge-bot openshift-merge-bot bot deleted the rebase-release-4.16-4.16.0-0.nightly-2024-05-23-173505_amd64-2024-05-23_arm64-2024-05-28 branch May 29, 2024 07:29
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