Skip to content

Conversation

@microshift-rebase-script
Copy link
Contributor

amd64: 4.20.0-0.nightly-2025-12-17-043535
arm64: 4.20.0-0.nightly-arm64-2025-12-17-223534
prow job: https://prow.ci.openshift.org/view/gs/origin-ci-test/logs/periodic-ci-openshift-microshift-release-4.20-periodics-rebase-on-nightlies/2001502933295828992

  • cluster-ingress-operator embedded-component fb7482e49c790206e370494221b7b02dc50bfd84 to 24ef5ae121b8f658b649bb555be827f114ead438

    • b272f60 2025-12-09T14:39:29+01:00 OCPBUGS-61858: Implement e2e test for HTTPKeepAliveTimeout
    • 5c90dcb 2025-12-09T14:39:22+01:00 OCPBUGS-61858: Implement HTTPKeepAliveTimeout tuning option
    • f3afe9a 2025-12-05T17:44:57+01:00 Add new NID team members to OWNERS
  • machine-config-operator embedded-component bb066c315eb491455d97d4307c0c6c3b9e7a4fc7 to 3eb8e48748919195aaa65b415c21b05f6287fc8f

    • 2499bc28 2025-12-10T12:08:40+02:00 add missing ports in contaiterport on the daemoset
    • 939701a5 2025-12-10T12:07:18+02:00 add a relevant svc to the crio port
    • 45e456a3 2025-12-10T12:05:50+02:00 Add hostIP 127.0.0.1 to machine-config-daemon port 8798

/label tide/merge-method-squash
/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 Dec 18, 2025
@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.20.0-0.nightly-2025-12-17-043535
arm64: 4.20.0-0.nightly-arm64-2025-12-17-223534
prow job: https://prow.ci.openshift.org/view/gs/origin-ci-test/logs/periodic-ci-openshift-microshift-release-4.20-periodics-rebase-on-nightlies/2001502933295828992

  • cluster-ingress-operator embedded-component fb7482e49c790206e370494221b7b02dc50bfd84 to 24ef5ae121b8f658b649bb555be827f114ead438

  • b272f60 2025-12-09T14:39:29+01:00 OCPBUGS-61858: Implement e2e test for HTTPKeepAliveTimeout

  • 5c90dcb 2025-12-09T14:39:22+01:00 OCPBUGS-61858: Implement HTTPKeepAliveTimeout tuning option

  • f3afe9a 2025-12-05T17:44:57+01:00 Add new NID team members to OWNERS

  • machine-config-operator embedded-component bb066c315eb491455d97d4307c0c6c3b9e7a4fc7 to 3eb8e48748919195aaa65b415c21b05f6287fc8f

  • 2499bc28 2025-12-10T12:08:40+02:00 add missing ports in contaiterport on the daemoset

  • 939701a5 2025-12-10T12:07:18+02:00 add a relevant svc to the crio port

  • 45e456a3 2025-12-10T12:05:50+02:00 Add hostIP 127.0.0.1 to machine-config-daemon port 8798

/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
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 Dec 18, 2025
@openshift-ci openshift-ci bot requested review from eslutsky and jerpeter1 December 18, 2025 05:03
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Dec 18, 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.

@ggiguash
Copy link
Contributor

/lgtm
/verified by ci

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

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

Details

In response to this:

/lgtm
/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 openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Dec 18, 2025
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Dec 18, 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 Dec 18, 2025
@openshift-merge-bot openshift-merge-bot bot merged commit 8a725ab into release-4.20 Dec 18, 2025
15 checks passed
@openshift-merge-bot openshift-merge-bot bot deleted the rebase-release-4.20-4.20.0-0.nightly-2025-12-17-043535_amd64-2025-12-17_arm64-2025-12-17 branch December 18, 2025 07:01
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