Skip to content

Conversation

microshift-rebase-script[bot]
Copy link
Contributor

amd64: 4.18.0-0.nightly-2024-09-23-182657
arm64: 4.18.0-0.nightly-arm64-2024-09-25-225501
prow job: https://prow.ci.openshift.org/view/gs/origin-ci-test/logs/periodic-ci-openshift-microshift-main-rebase-on-nightlies/1839153234388717568

  • cluster-ingress-operator embedded-component 871b2b20f9a3381e7ee31fda34f5821f51fff13c to b67185f557fceab56fc27d0fde5f6aca3f96e30c

    • 8655f59 2024-08-28T10:16:47+02:00 Set required-scc dynamically for ingress
    • f5099e4 2024-08-28T10:16:24+02:00 Set required-scc for openshift workloads
  • machine-config-operator embedded-component 2bea7cd03f26a85f9a76d6c9db7dbb8067a45ee6 to a6ee4b40c68c3d1c89748f7519886a0e27444685

    • 4a633c80 2024-09-20T10:59:44-04:00 envtest: update CRD install location
    • 3e29baec 2024-09-20T10:59:12-04:00 make go-deps
  • oc image-arm64 d6387d4acdcc020925d993d896437cffbf883671 to e75d922ae2a2af65a647dd6c094be9e78d49f7d4

    • 3f424dac 2024-09-25T16:21:13+03:00 Skip inspection of the daemonset pods running on data plane
    • db010056 2024-09-24T17:16:21-07:00 pkg/cli/admin/upgrade/recommend: Add end-to-end output test coverage
  • kubernetes image-arm64 ce117ff87249deb45bf9564d976255645e530105 to 947ea2f8f2a97d76a8bc9382c1ecda89fbc13555

    • d656b56da 2024-09-24T11:26:17-04:00 UPSTREAM: 125398: Fix issue with scheduler failing on hostname mismatch

/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.18.0-0.nightly-2024-09-23-182657
arm64: 4.18.0-0.nightly-arm64-2024-09-25-225501
prow job: https://prow.ci.openshift.org/view/gs/origin-ci-test/logs/periodic-ci-openshift-microshift-main-rebase-on-nightlies/1839153234388717568

  • cluster-ingress-operator embedded-component 871b2b20f9a3381e7ee31fda34f5821f51fff13c to b67185f557fceab56fc27d0fde5f6aca3f96e30c

  • 8655f59 2024-08-28T10:16:47+02:00 Set required-scc dynamically for ingress

  • f5099e4 2024-08-28T10:16:24+02:00 Set required-scc for openshift workloads

  • machine-config-operator embedded-component 2bea7cd03f26a85f9a76d6c9db7dbb8067a45ee6 to a6ee4b40c68c3d1c89748f7519886a0e27444685

  • 4a633c80 2024-09-20T10:59:44-04:00 envtest: update CRD install location

  • 3e29baec 2024-09-20T10:59:12-04:00 make go-deps

  • oc image-arm64 d6387d4acdcc020925d993d896437cffbf883671 to e75d922ae2a2af65a647dd6c094be9e78d49f7d4

  • 3f424dac 2024-09-25T16:21:13+03:00 Skip inspection of the daemonset pods running on data plane

  • db010056 2024-09-24T17:16:21-07:00 pkg/cli/admin/upgrade/recommend: Add end-to-end output test coverage

  • kubernetes image-arm64 ce117ff87249deb45bf9564d976255645e530105 to 947ea2f8f2a97d76a8bc9382c1ecda89fbc13555

  • d656b56da 2024-09-24T11:26:17-04:00 UPSTREAM: 125398: Fix issue with scheduler failing on hostname mismatch

/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 Sep 26, 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 Sep 26, 2024
Copy link
Contributor Author

Extra messages:

  • Deleted following branches: rebase-4.14.0-0.nightly-2024-09-23-173207_amd64-2024-09-23_arm64-2024-09-24, rebase-main-4.18.0-0.nightly-2024-09-23-182657_amd64-2024-09-23_arm64-2024-09-24, rebase-release-4.16-4.16.0-0.nightly-2024-09-24-060552_amd64-2024-09-24_arm64-2024-09-24, rebase-release-4.17-4.17.0-0.nightly-2024-09-23-211417_amd64-2024-09-23_arm64-2024-09-24

@openshift-ci openshift-ci bot requested review from copejon and pacevedom September 26, 2024 04:23
@pmtk
Copy link
Member

pmtk commented Sep 26, 2024

/lgtm

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

openshift-ci bot commented Sep 26, 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

@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Sep 26, 2024
@openshift-ci-robot
Copy link

/retest-required

Remaining retests: 0 against base HEAD 8e9cbf0 and 2 for PR HEAD bdd889a in total

Copy link
Contributor

openshift-ci bot commented Sep 26, 2024

@microshift-rebase-script: 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.

@openshift-merge-bot openshift-merge-bot bot merged commit 28b472a into main Sep 26, 2024
14 checks passed
@openshift-merge-bot openshift-merge-bot bot deleted the rebase-main-4.18.0-0.nightly-2024-09-23-182657_amd64-2024-09-23_arm64-2024-09-25 branch September 26, 2024 10:16
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