Skip to content

NO-ISSUE: rebase-release-4.16-4.16.0-0.nightly-2024-12-18-161525_amd64-2024-12-18_arm64-2024-12-18#4337

Merged
openshift-merge-bot[bot] merged 5 commits intorelease-4.16from
rebase-release-4.16-4.16.0-0.nightly-2024-12-18-161525_amd64-2024-12-18_arm64-2024-12-18
Dec 19, 2024
Merged

NO-ISSUE: rebase-release-4.16-4.16.0-0.nightly-2024-12-18-161525_amd64-2024-12-18_arm64-2024-12-18#4337
openshift-merge-bot[bot] merged 5 commits intorelease-4.16from
rebase-release-4.16-4.16.0-0.nightly-2024-12-18-161525_amd64-2024-12-18_arm64-2024-12-18

Conversation

@microshift-rebase-script
Copy link
Copy Markdown
Contributor

amd64: 4.16.0-0.nightly-2024-12-18-161525
arm64: 4.16.0-0.nightly-arm64-2024-12-18-233740
prow job: https://prow.ci.openshift.org/view/gs/origin-ci-test/logs/periodic-ci-openshift-microshift-release-4.16-rebase-on-nightlies/1869593702335254528

  • cluster-network-operator embedded-component efa14fa349e7cd9ecd44dc90ad5dc1c7c52fea4c to aa286367d966f61fe06b4bb107e2b324328450ff

    • b67bafc 2024-12-13T18:48:14+01:00 Skip including default crypto policies to avoid authby issue
    • 530e7be 2024-12-11T02:19:19-05:00 Prevent live migration process from flapping between step-2 and step-3
  • operator-framework-olm embedded-component d718c4c564975f3d4fac468987c4424691201790 to cee1f16cea7e10b8317c8e75420b84820ff19607

/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 Dec 19, 2024
@openshift-ci-robot
Copy link
Copy Markdown

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

Details

In response to this:

amd64: 4.16.0-0.nightly-2024-12-18-161525
arm64: 4.16.0-0.nightly-arm64-2024-12-18-233740
prow job: https://prow.ci.openshift.org/view/gs/origin-ci-test/logs/periodic-ci-openshift-microshift-release-4.16-rebase-on-nightlies/1869593702335254528

  • cluster-network-operator embedded-component efa14fa349e7cd9ecd44dc90ad5dc1c7c52fea4c to aa286367d966f61fe06b4bb107e2b324328450ff

  • b67bafc 2024-12-13T18:48:14+01:00 Skip including default crypto policies to avoid authby issue

  • 530e7be 2024-12-11T02:19:19-05:00 Prevent live migration process from flapping between step-2 and step-3

  • operator-framework-olm embedded-component d718c4c564975f3d4fac468987c4424691201790 to cee1f16cea7e10b8317c8e75420b84820ff19607

  • bcf32067 2024-12-16T07:15:49+00:00 CRD upgrade existing CR validation fix ([release-4.16] USHIFT-3266 Increase cncf result collection timeout to 10m #3442)

/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 Dec 19, 2024
@openshift-ci openshift-ci Bot requested review from ggiguash and pliurh December 19, 2024 04:52
@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci Bot commented Dec 19, 2024

@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-sigs/prow repository. I understand the commands that are listed here.

@ggiguash
Copy link
Copy Markdown
Contributor

/lgtm

@openshift-ci openshift-ci Bot added the lgtm Indicates that a PR is ready to be merged. label Dec 19, 2024
@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci Bot commented Dec 19, 2024

[APPROVALNOTIFIER] This PR is APPROVED

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

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 Dec 19, 2024
@openshift-merge-bot openshift-merge-bot Bot merged commit b885376 into release-4.16 Dec 19, 2024
@openshift-merge-bot openshift-merge-bot Bot deleted the rebase-release-4.16-4.16.0-0.nightly-2024-12-18-161525_amd64-2024-12-18_arm64-2024-12-18 branch December 19, 2024 07: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.

2 participants