Skip to content

NO-ISSUE: rebase-release-4.15-4.15.0-0.nightly-2024-07-14-093612_amd64-2024-07-14_arm64-2024-07-14#3628

Merged
openshift-merge-bot[bot] merged 4 commits intorelease-4.15from
rebase-release-4.15-4.15.0-0.nightly-2024-07-14-093612_amd64-2024-07-14_arm64-2024-07-14
Jul 15, 2024
Merged

NO-ISSUE: rebase-release-4.15-4.15.0-0.nightly-2024-07-14-093612_amd64-2024-07-14_arm64-2024-07-14#3628
openshift-merge-bot[bot] merged 4 commits intorelease-4.15from
rebase-release-4.15-4.15.0-0.nightly-2024-07-14-093612_amd64-2024-07-14_arm64-2024-07-14

Conversation

@microshift-rebase-script
Copy link
Contributor

@microshift-rebase-script microshift-rebase-script bot commented Jul 15, 2024

amd64: 4.15.0-0.nightly-2024-07-14-093612
arm64: 4.15.0-0.nightly-arm64-2024-07-14-235456
prow job: https://prow.ci.openshift.org/view/gs/origin-ci-test/logs/periodic-ci-openshift-microshift-release-4.15-rebase-on-nightlies/1812698829137383424

  • cluster-ingress-operator embedded-component 28bcd5f6f2ce8496e1967860ee5646f0f5c373b3 to 0928822bf67774af6798b218bff54ff5d14594cd

    • 357c1a7 2024-07-02T20:23:53-04:00 Delete & recreate canary route to clear spec.host
    • a1d3934 2024-07-02T20:23:53-04:00 Allow operator to update Route spec.subdomain
  • machine-config-operator embedded-component e45c36964262382c4d320317ea3efe0cca56dce4 to cee5dd7922f666583d92128b72fe7adac77c04ae

    • 11e8f78d 2024-06-10T13:47:43+00:00 OCPBUGS-33357: Check both ready and health ingress endpoints
    • a2db2f2f 2024-03-04T17:15:20+01:00 OCPBUGS-22324: Fix wait-for-br-ex-up enablement logic
    • acf9f5d0 2024-03-04T17:15:19+01:00 Wait for br-ex up event before node-valid-hostname
    • 2e12a64a 2024-03-04T17:15:18+01:00 OCPBUGS-27162: Add dependency on crio-wipe to resolv-prepender
    • 4efd96aa 2024-03-04T17:15:17+01:00 OCPBUGS-29732: Always touch resolv-prepender file at end of script
    • cb26598a 2024-03-04T17:15:16+01:00 OPNET-469: Apply new DNS configuration only if changed
    • 0740a606 2024-03-04T17:15:15+01:00 OCPBUGS-29624: Restart resolv-prepender on failure
    • d7d1c96b 2024-03-04T17:15:14+01:00 OPNET-355: Use NM's dns-change event for resolv.conf
  • operator-framework-olm embedded-component 89cf3705e28c59cc9228f606de8b555771eb474a to 28befe20a9f97db2a4a47c655b483de3197622da

  • oc image-amd64 44edfb50c55756395abc844fc4f7edb19dfefa50 to 1e41aa3e007fc60af9edfc77be1c610205943f4a

    • f976e195 2024-07-05T15:01:09+01:00 debug: set required-scc annotation to privileged for node debug pods
  • oc image-arm64 44edfb50c55756395abc844fc4f7edb19dfefa50 to 1e41aa3e007fc60af9edfc77be1c610205943f4a

    • f976e195 2024-07-05T15:01:09+01:00 debug: set required-scc annotation to privileged for node debug pods

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

@openshift-ci-robot
Copy link

openshift-ci-robot commented Jul 15, 2024

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

Details

In response to this:

amd64: 4.15.0-0.nightly-2024-07-14-093612
arm64: 4.15.0-0.nightly-arm64-2024-07-14-235456
prow job: https://prow.ci.openshift.org/view/gs/origin-ci-test/logs/periodic-ci-openshift-microshift-release-4.15-rebase-on-nightlies/1812698829137383424

  • cluster-ingress-operator embedded-component 28bcd5f6f2ce8496e1967860ee5646f0f5c373b3 to 0928822bf67774af6798b218bff54ff5d14594cd

  • 357c1a7 2024-07-02T20:23:53-04:00 Delete & recreate canary route to clear spec.host

  • a1d3934 2024-07-02T20:23:53-04:00 Allow operator to update Route spec.subdomain

  • machine-config-operator embedded-component e45c36964262382c4d320317ea3efe0cca56dce4 to cee5dd7922f666583d92128b72fe7adac77c04ae

  • 11e8f78d 2024-06-10T13:47:43+00:00 OCPBUGS-33357: Check both ready and health ingress endpoints

  • a2db2f2f 2024-03-04T17:15:20+01:00 OCPBUGS-22324: Fix wait-for-br-ex-up enablement logic

  • acf9f5d0 2024-03-04T17:15:19+01:00 Wait for br-ex up event before node-valid-hostname

  • 2e12a64a 2024-03-04T17:15:18+01:00 OCPBUGS-27162: Add dependency on crio-wipe to resolv-prepender

  • 4efd96aa 2024-03-04T17:15:17+01:00 OCPBUGS-29732: Always touch resolv-prepender file at end of script

  • cb26598a 2024-03-04T17:15:16+01:00 OPNET-469: Apply new DNS configuration only if changed

  • 0740a606 2024-03-04T17:15:15+01:00 OCPBUGS-29624: Restart resolv-prepender on failure

  • d7d1c96b 2024-03-04T17:15:14+01:00 OPNET-355: Use NM's dns-change event for resolv.conf

  • operator-framework-olm embedded-component 89cf3705e28c59cc9228f606de8b555771eb474a to 28befe20a9f97db2a4a47c655b483de3197622da

  • 1849397f 2024-07-10T10:16:43-04:00 [OCPBUGS-25341]: perform operator apiService certificate validity checks directly (NO-ISSUE: rebase-main-4.16.0-0.nightly-2024-04-03-065948_amd64-2024-04-03_arm64-2024-04-04 #3217)

  • 8c4e7516 2024-07-02T10:50:25-07:00 Unpack Job Creation Failure Test (NO-ISSUE: Manual 4.15 rebase. Pull csi-snapshot-webhook new manifests #3297)

  • 2069e356 2024-07-02T10:50:25-07:00 Fix: Ensure jobs without unpack label are considered (**FAILURE** rebase-release-4.15-4.15.0-0.nightly-2024-04-21-051624_amd64-2024-04-21_arm64-2024-04-21 #3262)

  • oc image-amd64 44edfb50c55756395abc844fc4f7edb19dfefa50 to 1e41aa3e007fc60af9edfc77be1c610205943f4a

  • f976e195 2024-07-05T15:01:09+01:00 debug: set required-scc annotation to privileged for node debug pods

  • oc image-arm64 44edfb50c55756395abc844fc4f7edb19dfefa50 to 1e41aa3e007fc60af9edfc77be1c610205943f4a

  • f976e195 2024-07-05T15:01:09+01:00 debug: set required-scc annotation to privileged for node debug pods

/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 Jul 15, 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 Jul 15, 2024
@openshift-ci openshift-ci bot requested review from pliurh and pmtk July 15, 2024 04:15
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Jul 15, 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.

@pmtk
Copy link
Member

pmtk commented Jul 15, 2024

/lgtm

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

openshift-ci bot commented Jul 15, 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

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 Jul 15, 2024
@openshift-merge-bot openshift-merge-bot bot merged commit 48618a4 into release-4.15 Jul 15, 2024
@openshift-merge-bot openshift-merge-bot bot deleted the rebase-release-4.15-4.15.0-0.nightly-2024-07-14-093612_amd64-2024-07-14_arm64-2024-07-14 branch July 15, 2024 06:56
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