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-03-04-212436_amd64-2024-03-04_arm64-2024-03-05 #3107

Conversation

microshift-rebase-script[bot]
Copy link
Contributor

@microshift-rebase-script microshift-rebase-script bot commented Mar 5, 2024

amd64: 4.15.0-0.nightly-2024-03-04-212436
arm64: 4.15.0-0.nightly-arm64-2024-03-05-004026
prow job: https://prow.ci.openshift.org/view/gs/origin-ci-test/logs/periodic-ci-openshift-microshift-release-4.15-rebase-on-nightlies/1764878738769580032

  • cluster-kube-apiserver-operator embedded-component 689a2bdc377383c774cc353c8e643dfcbb40159e to 1a0ab60403ccf253f0f651866418592eb533773d

    • 31eac23 2024-02-09T11:48:58+00:00 OBSDA-553: add provider name to cluster_infrastructure_provider when platform external
  • operator-framework-olm embedded-component 0e8b957251ce3edb82ca8d9139380b18df1fe55c to 9537a6ac615d152b3079b87a4a7ed11c5319ee6f

  • ovn-kubernetes image-amd64 3fdc9242e361a5e5007556054f5b0cc68a5be3d4 to 42b1cc427538a736f8c056171b4de7e6c6a366fb

    • 9958671 2024-02-16T10:35:05+01:00 Update HostNetworkNamespace address_set for remote zone nodes
  • ovn-kubernetes image-arm64 3fdc9242e361a5e5007556054f5b0cc68a5be3d4 to 42b1cc427538a736f8c056171b4de7e6c6a366fb

    • 9958671 2024-02-16T10:35:05+01:00 Update HostNetworkNamespace address_set for remote zone nodes

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

openshift-ci-robot commented Mar 5, 2024

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

In response to this:

amd64: 4.15.0-0.nightly-2024-03-04-212436
arm64: 4.15.0-0.nightly-arm64-2024-03-05-004026
prow job: https://prow.ci.openshift.org/view/gs/origin-ci-test/logs/periodic-ci-openshift-microshift-release-4.15-rebase-on-nightlies/1764878738769580032

  • cluster-kube-apiserver-operator embedded-component 689a2bdc377383c774cc353c8e643dfcbb40159e to 1a0ab60403ccf253f0f651866418592eb533773d

  • 31eac23 2024-02-09T11:48:58+00:00 OBSDA-553: add provider name to cluster_infrastructure_provider when platform external

  • operator-framework-olm embedded-component 0e8b957251ce3edb82ca8d9139380b18df1fe55c to 9537a6ac615d152b3079b87a4a7ed11c5319ee6f

  • 7572c6c8 2024-03-02T00:37:43+00:00 UPSTREAM: : Add object cache for psm resource queries

  • cf925f97 2024-03-02T00:37:43+00:00 (psm) Wait for required RBAC before creating packageserver CSV

  • af148353 2024-03-01T10:22:14-08:00 Modify installation steps for ClusterRoleBindings and Services to use SSA in order to avoid race conditions. (NO-ISSUE: rebase-4.14.0-0.nightly-2024-03-24-035901_amd64-2024-03-24_arm64-2024-03-25 #3182)

  • ovn-kubernetes image-amd64 3fdc9242e361a5e5007556054f5b0cc68a5be3d4 to 42b1cc427538a736f8c056171b4de7e6c6a366fb

  • 9958671 2024-02-16T10:35:05+01:00 Update HostNetworkNamespace address_set for remote zone nodes

  • ovn-kubernetes image-arm64 3fdc9242e361a5e5007556054f5b0cc68a5be3d4 to 42b1cc427538a736f8c056171b4de7e6c6a366fb

  • 9958671 2024-02-16T10:35:05+01:00 Update HostNetworkNamespace address_set for remote zone nodes

/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 Mar 5, 2024
@eslutsky
Copy link
Contributor

eslutsky commented Mar 5, 2024

/test microshift-metal-tests

@eslutsky
Copy link
Contributor

eslutsky commented Mar 5, 2024

/lgtm

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

openshift-ci bot commented Mar 5, 2024

[APPROVALNOTIFIER] This PR is APPROVED

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

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 Mar 5, 2024
Copy link
Contributor

openshift-ci bot commented Mar 5, 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/test-infra repository. I understand the commands that are listed here.

@openshift-merge-bot openshift-merge-bot bot merged commit 66e70b4 into release-4.15 Mar 5, 2024
9 checks passed
@openshift-merge-bot openshift-merge-bot bot deleted the rebase-release-4.15-4.15.0-0.nightly-2024-03-04-212436_amd64-2024-03-04_arm64-2024-03-05 branch March 5, 2024 13: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.

None yet

2 participants