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-main-4.19.0-0.nightly-2025-01-19-211100_amd64-2025-01-19_arm64-2025-01-20 #4434

Conversation

microshift-rebase-script[bot]
Copy link
Contributor

amd64: 4.19.0-0.nightly-2025-01-19-211100
arm64: 4.19.0-0.nightly-arm64-2025-01-20-000530
prow job: https://prow.ci.openshift.org/view/gs/origin-ci-test/logs/periodic-ci-openshift-microshift-main-rebase-on-nightlies/1881190123744268288

  • cluster-csi-snapshot-controller-operator embedded-component 9dceffb866318acb2bb77182095a18b6f397416f to a68ffe82329d198f79508daeb6c63c6bc2a4e19a

    • 0878bc0 2025-01-08T17:39:03+01:00 Support HCP labels
  • cluster-network-operator embedded-component 722d631aab15ac726c45ad8d2d148843f3ec165b to a967bf84a777795ff47f199c5200341809d250b1

    • 91b8a78 2025-01-13T20:32:09+01:00 Fix user-defined-networks-namespace-label binding
    • 69a1624 2024-12-11T16:53:20+00:00 Add host isolation mounts to ovnkube-node
  • router image-amd64 7a688b0eab5a27fe13988a21022c774cdeb964b2 to 20f7f41430f7c660438c32532ccd7b453b014b68

    • ee12f18 2025-01-09T11:22:57-05:00 OCPBUGS-47761: Update default_pub_keys.pem to use SHA256
  • router image-arm64 7a688b0eab5a27fe13988a21022c774cdeb964b2 to 20f7f41430f7c660438c32532ccd7b453b014b68

    • ee12f18 2025-01-09T11:22:57-05:00 OCPBUGS-47761: Update default_pub_keys.pem to use SHA256

/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.19.0-0.nightly-2025-01-19-211100
arm64: 4.19.0-0.nightly-arm64-2025-01-20-000530
prow job: https://prow.ci.openshift.org/view/gs/origin-ci-test/logs/periodic-ci-openshift-microshift-main-rebase-on-nightlies/1881190123744268288

  • cluster-csi-snapshot-controller-operator embedded-component 9dceffb866318acb2bb77182095a18b6f397416f to a68ffe82329d198f79508daeb6c63c6bc2a4e19a

  • 0878bc0 2025-01-08T17:39:03+01:00 Support HCP labels

  • cluster-network-operator embedded-component 722d631aab15ac726c45ad8d2d148843f3ec165b to a967bf84a777795ff47f199c5200341809d250b1

  • 91b8a78 2025-01-13T20:32:09+01:00 Fix user-defined-networks-namespace-label binding

  • 69a1624 2024-12-11T16:53:20+00:00 Add host isolation mounts to ovnkube-node

  • router image-amd64 7a688b0eab5a27fe13988a21022c774cdeb964b2 to 20f7f41430f7c660438c32532ccd7b453b014b68

  • ee12f18 2025-01-09T11:22:57-05:00 OCPBUGS-47761: Update default_pub_keys.pem to use SHA256

  • router image-arm64 7a688b0eab5a27fe13988a21022c774cdeb964b2 to 20f7f41430f7c660438c32532ccd7b453b014b68

  • ee12f18 2025-01-09T11:22:57-05:00 OCPBUGS-47761: Update default_pub_keys.pem to use SHA256

/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 Jan 20, 2025
@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 Jan 20, 2025
@openshift-ci openshift-ci bot requested review from agullon and eslutsky January 20, 2025 04:45
Copy link
Contributor

openshift-ci bot commented Jan 20, 2025

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

@pmtk
Copy link
Member

pmtk commented Jan 20, 2025

/lgtm

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

openshift-ci bot commented Jan 20, 2025

[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 Jan 20, 2025
@openshift-merge-bot openshift-merge-bot bot merged commit d2cdaaa into main Jan 20, 2025
12 checks passed
@openshift-merge-bot openshift-merge-bot bot deleted the rebase-main-4.19.0-0.nightly-2025-01-19-211100_amd64-2025-01-19_arm64-2025-01-20 branch January 20, 2025 08:23
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