Skip to content

NO-ISSUE: rebase-4.14.0-0.nightly-2024-05-08-232852_amd64-2024-05-08_arm64-2024-05-09#3341

Merged
openshift-merge-bot[bot] merged 5 commits intorelease-4.14from
rebase-4.14.0-0.nightly-2024-05-08-232852_amd64-2024-05-08_arm64-2024-05-09
May 10, 2024
Merged

NO-ISSUE: rebase-4.14.0-0.nightly-2024-05-08-232852_amd64-2024-05-08_arm64-2024-05-09#3341
openshift-merge-bot[bot] merged 5 commits intorelease-4.14from
rebase-4.14.0-0.nightly-2024-05-08-232852_amd64-2024-05-08_arm64-2024-05-09

Conversation

@microshift-rebase-script
Copy link
Copy Markdown
Contributor

amd64: 4.14.0-0.nightly-2024-05-08-232852
arm64: 4.14.0-0.nightly-arm64-2024-05-09-233233
prow job: https://prow.ci.openshift.org/view/gs/origin-ci-test/logs/periodic-ci-openshift-microshift-release-4.14-rebase-on-nightlies/1788796487472254976

  • router image-arm64 e1e59b3337700e2b94c8d5c5e5414519f9785614 to e17abdff0095edee65e3be926f98b758aa3c87bb
    • f0ad69e 2024-05-08T07:45:09+00:00 OCPBUGS-29690: Count active services before setting weight to 1

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

@microshift-rebase-script
Copy link
Copy Markdown
Contributor Author

Extra messages:

@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 10, 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.14.0-0.nightly-2024-05-08-232852
arm64: 4.14.0-0.nightly-arm64-2024-05-09-233233
prow job: https://prow.ci.openshift.org/view/gs/origin-ci-test/logs/periodic-ci-openshift-microshift-release-4.14-rebase-on-nightlies/1788796487472254976

  • router image-arm64 e1e59b3337700e2b94c8d5c5e5414519f9785614 to e17abdff0095edee65e3be926f98b758aa3c87bb
  • f0ad69e 2024-05-08T07:45:09+00:00 OCPBUGS-29690: Count active services before setting weight to 1

/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 10, 2024
@openshift-ci openshift-ci Bot requested review from dhellmann and jogeo May 10, 2024 05:09
@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci Bot commented May 10, 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 May 10, 2024
@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci Bot commented May 10, 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 May 10, 2024
@openshift-merge-bot openshift-merge-bot Bot merged commit a49dea6 into release-4.14 May 10, 2024
@openshift-merge-bot openshift-merge-bot Bot deleted the rebase-4.14.0-0.nightly-2024-05-08-232852_amd64-2024-05-08_arm64-2024-05-09 branch May 10, 2024 06:47
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