Skip to content

NO-ISSUE: rebase-release-4.17-4.17.0-0.nightly-2026-01-26-142731_amd64-2026-01-26_arm64-2026-01-29#6164

Merged
openshift-merge-bot[bot] merged 5 commits intorelease-4.17from
rebase-release-4.17-4.17.0-0.nightly-2026-01-26-142731_amd64-2026-01-26_arm64-2026-01-29
Jan 29, 2026
Merged

NO-ISSUE: rebase-release-4.17-4.17.0-0.nightly-2026-01-26-142731_amd64-2026-01-26_arm64-2026-01-29#6164
openshift-merge-bot[bot] merged 5 commits intorelease-4.17from
rebase-release-4.17-4.17.0-0.nightly-2026-01-26-142731_amd64-2026-01-26_arm64-2026-01-29

Conversation

@microshift-rebase-script
Copy link
Contributor

amd64: 4.17.0-0.nightly-2026-01-26-142731
arm64: 4.17.0-0.nightly-arm64-2026-01-29-002739
prow job: https://prow.ci.openshift.org/view/gs/origin-ci-test/logs/periodic-ci-openshift-microshift-release-4.17-rebase-on-nightlies/2016723224418586624

  • ovn-kubernetes image-arm64 fc112155baeb6423e0b9969e08bb1160d736f43f to a7f14dd8b75e92fff6fcac2093641e0d1d4b6c48
    • 3b6ba1c9 2026-01-21T22:11:00+08:00 Fix conntrack reconciliation to use service port instead of endpoint port

/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.17.0-0.nightly-2026-01-26-142731
arm64: 4.17.0-0.nightly-arm64-2026-01-29-002739
prow job: https://prow.ci.openshift.org/view/gs/origin-ci-test/logs/periodic-ci-openshift-microshift-release-4.17-rebase-on-nightlies/2016723224418586624

  • ovn-kubernetes image-arm64 fc112155baeb6423e0b9969e08bb1160d736f43f to a7f14dd8b75e92fff6fcac2093641e0d1d4b6c48
  • 3b6ba1c9 2026-01-21T22:11:00+08:00 Fix conntrack reconciliation to use service port instead of endpoint port

/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 Jan 29, 2026
@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 Jan 29, 2026
@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 requested review from jogeo and pliurh January 29, 2026 04:13
@pacevedom
Copy link
Contributor

/retest

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Jan 29, 2026

@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 Jan 29, 2026
@pacevedom
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 Jan 29, 2026
@openshift-ci-robot
Copy link

@pacevedom: 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 Jan 29, 2026

[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 Jan 29, 2026
@openshift-merge-bot openshift-merge-bot bot merged commit af2a6fe into release-4.17 Jan 29, 2026
21 checks passed
@openshift-merge-bot openshift-merge-bot bot deleted the rebase-release-4.17-4.17.0-0.nightly-2026-01-26-142731_amd64-2026-01-26_arm64-2026-01-29 branch January 29, 2026 08:47
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