Skip to content

NO-ISSUE: rebase-release-4.19-4.19.0-0.nightly-2025-11-19-155716_amd64-2025-11-19_arm64-2025-11-19#5768

Merged
openshift-merge-bot[bot] merged 5 commits intorelease-4.19from
rebase-release-4.19-4.19.0-0.nightly-2025-11-19-155716_amd64-2025-11-19_arm64-2025-11-19
Nov 20, 2025
Merged

NO-ISSUE: rebase-release-4.19-4.19.0-0.nightly-2025-11-19-155716_amd64-2025-11-19_arm64-2025-11-19#5768
openshift-merge-bot[bot] merged 5 commits intorelease-4.19from
rebase-release-4.19-4.19.0-0.nightly-2025-11-19-155716_amd64-2025-11-19_arm64-2025-11-19

Conversation

@microshift-rebase-script
Copy link
Contributor

amd64: 4.19.0-0.nightly-2025-11-19-155716
arm64: 4.19.0-0.nightly-arm64-2025-11-19-155715
prow job: https://prow.ci.openshift.org/view/gs/origin-ci-test/logs/periodic-ci-openshift-microshift-release-4.19-periodics-rebase-on-nightlies/1991356145956032512

  • oc image-amd64 b61226dacc6e9eeadcc6103cbfc3c6b47fea5e99 to 581d48a297ae8c89a7dbefedd6694b1ab300c082

    • c4df4bc6 2025-11-14T11:09:17+01:00 fix(must-gather): do not set node affinity if nodename is set
  • oc image-arm64 b61226dacc6e9eeadcc6103cbfc3c6b47fea5e99 to 581d48a297ae8c89a7dbefedd6694b1ab300c082

    • c4df4bc6 2025-11-14T11:09:17+01:00 fix(must-gather): do not set node affinity if nodename is set

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

@microshift-rebase-script
Copy link
Contributor Author

/verified by automatic-rebase

@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-11-19-155716
arm64: 4.19.0-0.nightly-arm64-2025-11-19-155715
prow job: https://prow.ci.openshift.org/view/gs/origin-ci-test/logs/periodic-ci-openshift-microshift-release-4.19-periodics-rebase-on-nightlies/1991356145956032512

  • oc image-amd64 b61226dacc6e9eeadcc6103cbfc3c6b47fea5e99 to 581d48a297ae8c89a7dbefedd6694b1ab300c082

  • c4df4bc6 2025-11-14T11:09:17+01:00 fix(must-gather): do not set node affinity if nodename is set

  • oc image-arm64 b61226dacc6e9eeadcc6103cbfc3c6b47fea5e99 to 581d48a297ae8c89a7dbefedd6694b1ab300c082

  • c4df4bc6 2025-11-14T11:09:17+01:00 fix(must-gather): do not set node affinity if nodename is set

/label tide/merge-method-squash
/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 Nov 20, 2025
@openshift-ci-robot
Copy link

@microshift-rebase-script[bot]: Jira verification commands are restricted to collaborators for this repo.

Details

In response to this:

/verified by automatic-rebase

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. 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 Nov 20, 2025
@openshift-ci openshift-ci bot requested review from ggiguash and jogeo November 20, 2025 04:25
@ggiguash
Copy link
Contributor

/lgtm
/verified by ci

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

/test all

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Nov 20, 2025

[APPROVALNOTIFIER] This PR is APPROVED

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

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 Nov 20, 2025
@ggiguash
Copy link
Contributor

/verified by ci

@openshift-ci-robot openshift-ci-robot added the verified Signifies that the PR passed pre-merge verification criteria label Nov 20, 2025
@openshift-ci-robot
Copy link

@ggiguash: This PR has been marked as verified by ci.

Details

In response to this:

/verified by ci

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
Copy link
Contributor

openshift-ci bot commented Nov 20, 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.

@openshift-merge-bot openshift-merge-bot bot merged commit 432c430 into release-4.19 Nov 20, 2025
13 checks passed
@openshift-merge-bot openshift-merge-bot bot deleted the rebase-release-4.19-4.19.0-0.nightly-2025-11-19-155716_amd64-2025-11-19_arm64-2025-11-19 branch November 20, 2025 17:37
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. 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. verified Signifies that the PR passed pre-merge verification criteria

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants