Skip to content

Conversation

@microshift-rebase-script
Copy link
Contributor

amd64: 4.19.0-0.nightly-2025-06-15-192624
arm64: 4.19.0-0.nightly-arm64-2025-06-15-225924
prow job: https://prow.ci.openshift.org/view/gs/origin-ci-test/logs/periodic-ci-openshift-microshift-release-4.19-rebase-on-nightlies/1934461272821075968

  • openshift-controller-manager embedded-component 8be524d728d03e61ee029ad2f7229ca97c93f87f to af43fe68a7d862959a797b66307a1277fffbc9df

    • dabcff4 2025-06-10T11:00:27+02:00 Set node-pullsecrets volume to read-only to protect image pull credentials
  • operator-framework-olm embedded-component 358b7053a231876cda29cf4d822e3e702389b117 to 4a6530a4cf4e8e81d8f04923f36dd36023f45902

/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 Jun 16, 2025
@openshift-ci-robot
Copy link

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

Details

In response to this:

amd64: 4.19.0-0.nightly-2025-06-15-192624
arm64: 4.19.0-0.nightly-arm64-2025-06-15-225924
prow job: https://prow.ci.openshift.org/view/gs/origin-ci-test/logs/periodic-ci-openshift-microshift-release-4.19-rebase-on-nightlies/1934461272821075968

  • openshift-controller-manager embedded-component 8be524d728d03e61ee029ad2f7229ca97c93f87f to af43fe68a7d862959a797b66307a1277fffbc9df

  • dabcff4 2025-06-10T11:00:27+02:00 Set node-pullsecrets volume to read-only to protect image pull credentials

  • operator-framework-olm embedded-component 358b7053a231876cda29cf4d822e3e702389b117 to 4a6530a4cf4e8e81d8f04923f36dd36023f45902

  • 4bbf010a 2025-06-11T14:11:48-05:00 reduce cache expiriry frequency (USHIFT-3733: add management annotation to topolvm pods #3591)

  • e4efee43 2025-06-10T08:05:31-04:00 operatorgroup: ensure clusterroleselectors in clusterrole aggregation rules are sorted (OCPBUGS-36587: Filter ip family in router service controller #3593)

/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 Jun 16, 2025
@openshift-ci openshift-ci bot requested review from copejon and ggiguash June 16, 2025 04:27
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Jun 16, 2025

@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.

Copy link
Contributor

@pacevedom pacevedom left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Jun 16, 2025
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Jun 16, 2025

[APPROVALNOTIFIER] This PR is APPROVED

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

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 Jun 16, 2025
@openshift-merge-bot openshift-merge-bot bot merged commit 911d209 into release-4.19 Jun 16, 2025
13 checks passed
@openshift-merge-bot openshift-merge-bot bot deleted the rebase-release-4.19-4.19.0-0.nightly-2025-06-15-192624_amd64-2025-06-15_arm64-2025-06-15 branch June 16, 2025 06:55
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