OCPBUGS-98619: Bump frr-k8s MAX_FDS from 1024 to 65536 by jcaamano · Pull Request #3054 · openshift/cluster-network-operator

jcaamano · 2026-07-15T09:49:06Z

bfdd opens 5 (2 IPv4 + 3 IPv6) UDP sockets against each VRF even if BFD has not been explicitly enabled on them. When using RouteAdvertisements with OVN-K CUDNs, this limits the scalability to ~200 of them assuming a default file descriptor limit of 1024. Bump it to 65536 which is in any case a much more reasonable limit for production network daemons.

bfdd opens 5 (2 IPv4 + 3 IPv6) UDP sockets against each VRF even if BFD has not been explicitly enabled on them. When using RouteAdvertisements with OVN-K CUDNs, this limits the scalability to ~200 of them assuming a default file descriptor limit of 1024. Bump it to 65536 which is in any case a much more reasonable limit for production network daemons. Signed-off-by: Jaime Caamaño Ruiz <jcaamano@redhat.com>

openshift-ci-robot · 2026-07-15T09:49:13Z

@jcaamano: This pull request references Jira Issue OCPBUGS-98619, which is invalid:

expected the bug to target the "5.0.0" version, but no target version was set

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

The bug has been updated to refer to the pull request using the external bug tracker.

Details

In response to this:

bfdd opens 5 (2 IPv4 + 3 IPv6) UDP sockets against each VRF even if BFD has not been explicitly enabled on them. When using RouteAdvertisements with OVN-K CUDNs, this limits the scalability to ~200 of them assuming a default file descriptor limit of 1024. Bump it to 65536 which is in any case a much more reasonable limit for production network daemons.

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-merge-bot · 2026-07-15T09:49:22Z

Pipeline controller notification
This repo is configured to use the pipeline controller. Second-stage tests will be triggered either automatically or after lgtm label is added, depending on the repository configuration. The pipeline controller will automatically detect which contexts are required and will utilize /test Prow commands to trigger the second stage.

For optional jobs, comment /test ? to see a list of all defined jobs. To trigger manually all jobs from second stage use /pipeline required command.

This repository is configured in: LGTM mode

coderabbitai · 2026-07-15T09:49:25Z

Walkthrough

The FRR-K8s startup configuration now actively sets MAX_FDS to 65536 and documents the need for higher limits when BFD uses multiple sockets per VRF.

Changes

FRR-K8s startup configuration

Layer / File(s)	Summary
Configure startup file descriptor limit `bindata/network/frr-k8s/config.yaml`	The `daemons` startup configuration enables `MAX_FDS=65536` and adds comments describing BFD’s file descriptor usage in high-scale production environments.

Estimated code review effort: 1 (Trivial) | ~2 minutes

Caution

Pre-merge checks failed

Please resolve all errors before merging. Addressing warnings is optional.

Ignore

❌ Failed checks (4 errors)

Check name	Status	Explanation	Resolution
Pr Quality	❌ Error	Small change, but the PR body is only a paragraph; it lacks explicit Why/What/Testing sections and CI verification details.	Rewrite the PR body with Why, What, and automated Testing/CI lanes; add user impact and rollback notes if applicable.
Commit Message Quality	❌ Error	The sole PR commit has a good body, but its subject isn’t component-prefixed as required (`Bump frr-k8s...` instead of `frr-k8s: ...`).	Rewrite the commit subject with a component prefix, e.g. `frr-k8s: Bump MAX_FDS from 1024 to 65536`, and keep the rationale body unchanged.
Unit Tests For Go Changes	❌ Error	bindata/network/frr-k8s/config.yaml changed, but no *_test.go files were added or modified in the PR.	Add or update corresponding tests, or document why tests are unnecessary in 'How to verify it' and then use '`@coderabbitai` ignore pre-merge checks' if appropriate.
Title check	❌ Error	The title is related, but it does not use imperative mood or the required component prefix.	Use an imperative, component-scoped title such as `frr-k8s: Bump MAX_FDS from 1024 to 65536`.

✅ Passed checks (20 passed)

Check name	Status	Explanation
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.
E2e Tests For Feature Changes	✅ Passed	Only bindata/network/frr-k8s/config.yaml changed; no pkg/cmd Go behavior change, so the E2E requirement doesn’t apply.
Rbac Least Privilege	✅ Passed	Only bindata/network/frr-k8s/config.yaml changed, updating a ConfigMap; no ClusterRole/Role rules were added or modified.
Docs For Feature And Behavior Changes	✅ Passed	Commit only updates bindata/network/frr-k8s/config.yaml to raise MAX_FDS; no docs/ files were added or modified, and this is a bug fix/internal config change.
Stale Project Docs And Config	✅ Passed	No docs/AGENTS/ARCHITECTURE or .coderabbit.yaml reference the old MAX_FDS value or any renamed frr-k8s paths; only the config manifest changed.
Go And Test Code Quality	✅ Passed	Only bindata/network/frr-k8s/config.yaml changed; no Go or test code was added or modified, so the Go/Test checks do not apply.
Ai-Generated Code Smell	✅ Passed	Only a small config update and explanatory comments were added; no verbose code, auto-generated tests, or AI-tool references were found.
Stable And Deterministic Test Names	✅ Passed	Diff only touches bindata/network/frr-k8s/config.yaml; no tests or Ginkgo titles changed, so the check is not applicable.
Test Structure And Quality	✅ Passed	No Ginkgo test files or test logic changed; PR only updates bindata/network/frr-k8s/config.yaml, so the test-quality check is not applicable.
Microshift Test Compatibility	✅ Passed	Only a FRR ConfigMap was changed; no new Ginkgo tests, contexts, or OpenShift API usage were added, so MicroShift compatibility is not implicated.
Single Node Openshift (Sno) Test Compatibility	✅ Passed	PASS: The PR only changes bindata/network/frr-k8s/config.yaml to raise MAX_FDS; no new Ginkgo tests or SNO-sensitive assumptions were added.
Topology-Aware Scheduling Compatibility	✅ Passed	Only MAX_FDS in a ConfigMap changed; no nodeSelector, affinity, anti-affinity, replicas, or topology-spread settings were added.
Ote Binary Stdout Contract	✅ Passed	Only bindata/network/frr-k8s/config.yaml changed; no process-level code or stdout writes were introduced.
Ipv6 And Disconnected Network Test Compatibility	✅ Passed	Only bindata/network/frr-k8s/config.yaml changed; no Ginkgo e2e tests or network-using code were added.
No-Weak-Crypto	✅ Passed	The PR only changes frr-k8s MAX_FDS/commentary; no weak-crypto primitives, custom crypto, or secret comparisons appear in the diff.
Container-Privileges	✅ Passed	Only bindata/network/frr-k8s/config.yaml changed, and it contains no privileged, hostPID/Network/IPC, SYS_ADMIN, root, or allowPrivilegeEscalation=true settings.
No-Sensitive-Data-In-Logs	✅ Passed	The PR only changes a config comment and MAX_FDS value; no new logging or exposed sensitive data appears in the diff.
Description check	✅ Passed	The description clearly matches the MAX_FDS increase and the scalability rationale.

✨ Finishing Touches

🧪 Generate unit tests (beta)

Create PR with unit tests

_{Comment @coderabbitai help to get the list of available commands.}

jcaamano · 2026-07-15T09:50:11Z

/jira refresh

openshift-ci-robot · 2026-07-15T09:50:16Z

@jcaamano: This pull request references Jira Issue OCPBUGS-98619, which is valid. The bug has been moved to the POST state.

3 validation(s) were run on this bug

bug is open, matching expected state (open)
bug target version (5.0.0) matches configured target version for branch (5.0.0)
bug is in the state New, which is one of the valid states (NEW, ASSIGNED, POST)

Details

In response to this:

/jira refresh

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.

venkataanil

I have tested with this change and able to create 250 CUDNs (i.e 250 VRFs on a worker node). Without this change, bfdd is crashing with below error for the same number of 250 CUDNs (i.e 250 VRFs)

2026/07/15 03:53:59 BFD: [XCQPZ-40HX4] echov6-socket: socket: Too many open files
2026/07/15 03:53:59 BFD: bfdd/bfd_packet.c:2140: bp_initv6_socket(): assertion (!"echov6-socket: socket: %s") failed
BFD: Received signal 6 at 1784087639 (si_addr 0x3e60000db44, PC 0x7f42a12be4bc); aborting...
BFD: /usr/lib64/frr/libfrr.so.0(zlog_backtrace_sigsafe+0x71) [0x7f42a1534d11]
BFD: /usr/lib64/frr/libfrr.so.0(zlog_signal+0xf5) [0x7f42a1534f15]
BFD: /usr/lib64/frr/libfrr.so.0(+0x101a55) [0x7f42a156fa55]
BFD: /lib64/libc.so.6(+0x3fc60) [0x7f42a1270c60]
BFD: /lib64/libc.so.6(+0x8d4bc) [0x7f42a12be4bc]
BFD: /lib64/libc.so.6(raise+0x16) [0x7f42a1270bb6]
BFD: /lib64/libc.so.6(abort+0xd3) [0x7f42a125a873]
BFD: /usr/lib64/frr/libfrr.so.0(_zlog_assert_failed+0xed) [0x7f42a159f05d]
BFD: /usr/libexec/frr/bfdd(bp_initv6_socket+0xe9) [0x55d104bcb2c9]
BFD: /usr/libexec/frr/bfdd(+0x274a8) [0x55d104bc44a8]
BFD: /usr/lib64/frr/libfrr.so.0(vrf_enable+0x59) [0x7f42a1586959]
BFD: /usr/lib64/frr/libfrr.so.0(+0x128a7b) [0x7f42a1596a7b]
BFD: /usr/lib64/frr/libfrr.so.0(+0x13ad3c) [0x7f42a15a8d3c]
BFD: /usr/lib64/frr/libfrr.so.0(event_call+0x9f) [0x7f42a1585ccf]
BFD: /usr/lib64/frr/libfrr.so.0(frr_run+0xd8) [0x7f42a152b798]
BFD: /usr/libexec/frr/bfdd(main+0x1e2) [0x55d104bb5a02]
BFD: /lib64/libc.so.6(+0x2a610) [0x7f42a125b610]
BFD: /lib64/libc.so.6(__libc_start_main+0x80) [0x7f42a125b6c0]
BFD: /usr/libexec/frr/bfdd(_start+0x25) [0x55d104bb5dd5]
BFD: in thread zclient_read scheduled from lib/zclient.c:4959 zclient_event()

fedepaol · 2026-07-15T09:57:53Z

/lgtm

openshift-merge-bot · 2026-07-15T09:58:30Z

Scheduling required tests:
/test e2e-aws-ovn-upgrade-ipsec
/test e2e-gcp-ovn-techpreview

Scheduling tests matching the pipeline_run_if_changed or not excluded by pipeline_skip_if_only_changed parameters:
/test frrk8s-e2e
/test e2e-aws-ovn-fdp-qe
/test e2e-aws-ovn-hypershift-conformance
/test e2e-aws-ovn-serial-1of2
/test e2e-aws-ovn-serial-2of2
/test e2e-aws-ovn-upgrade
/test e2e-aws-ovn-windows
/test e2e-azure-ovn-upgrade
/test e2e-gcp-ovn
/test e2e-gcp-ovn-upgrade
/test e2e-metal-ipi-ovn-dualstack-bgp
/test e2e-metal-ipi-ovn-dualstack-bgp-local-gw
/test e2e-metal-ipi-ovn-ipv6
/test e2e-metal-ipi-ovn-ipv6-ipsec
/test e2e-ovn-ipsec-step-registry
/test hypershift-e2e-aks

venkataanil · 2026-07-15T10:48:43Z

/verified by @venkataanil

openshift-ci-robot · 2026-07-15T10:48:54Z

@venkataanil: This PR has been marked as verified by @venkataanil.

Details

In response to this:

/verified by @venkataanil

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.

jtaleric · 2026-07-15T11:33:02Z

/lgtm

openshift-ci · 2026-07-15T11:33:34Z

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: fedepaol, jcaamano, jtaleric, venkataanil

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:

~~bindata/network/frr-k8s/OWNERS~~ [fedepaol,jcaamano]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

openshift-merge-bot · 2026-07-20T23:14:44Z

/retest-required

Remaining retests: 0 against base HEAD 22c1bf1 and 2 for PR HEAD 79bbb49 in total

openshift-merge-bot · 2026-07-21T18:13:36Z

/retest-required

Remaining retests: 0 against base HEAD d7ac0bd and 1 for PR HEAD 79bbb49 in total

jcaamano · 2026-07-22T08:29:38Z

/retest

jcaamano · 2026-07-22T08:49:47Z

/test all

jcaamano · 2026-07-22T08:51:02Z

/override ci/prow/e2e-aws-ovn-upgrade-ipsec
/override ci/prow/e2e-metal-ipi-ovn-ipv6-ipsec
/override ci/prow/e2e-ovn-ipsec-step-registry

openshift-ci · 2026-07-22T08:53:33Z

@jcaamano: Overrode contexts on behalf of jcaamano: ci/prow/e2e-aws-ovn-upgrade-ipsec, ci/prow/e2e-metal-ipi-ovn-ipv6-ipsec, ci/prow/e2e-ovn-ipsec-step-registry

Details

In response to this:

/override ci/prow/e2e-aws-ovn-upgrade-ipsec
/override ci/prow/e2e-metal-ipi-ovn-ipv6-ipsec
/override ci/prow/e2e-ovn-ipsec-step-registry

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.

jcaamano · 2026-07-22T23:41:44Z

/override ci/prow/e2e-aws-ovn-upgrade-ipsec
/override ci/prow/e2e-metal-ipi-ovn-ipv6-ipsec
/override ci/prow/e2e-ovn-ipsec-step-registry

openshift-ci · 2026-07-22T23:42:01Z

@jcaamano: Overrode contexts on behalf of jcaamano: ci/prow/e2e-aws-ovn-upgrade-ipsec, ci/prow/e2e-metal-ipi-ovn-ipv6-ipsec, ci/prow/e2e-ovn-ipsec-step-registry

Details

In response to this:

/override ci/prow/e2e-aws-ovn-upgrade-ipsec
/override ci/prow/e2e-metal-ipi-ovn-ipv6-ipsec
/override ci/prow/e2e-ovn-ipsec-step-registry

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.

jcaamano · 2026-07-22T23:42:51Z

/retest-required

openshift-merge-bot · 2026-07-23T05:58:52Z

/retest-required

Remaining retests: 0 against base HEAD 4f6fb6b and 2 for PR HEAD 79bbb49 in total

jcaamano · 2026-07-23T08:29:05Z

/override ci/prow/e2e-aws-ovn-fdp-qe

https://github.com/openshift/openshift-tests-private/pull/30074

openshift-ci · 2026-07-23T08:54:37Z

@jcaamano: Overrode contexts on behalf of jcaamano: ci/prow/e2e-aws-ovn-fdp-qe

Details

In response to this:

/override ci/prow/e2e-aws-ovn-fdp-qe

https://github.com/openshift/openshift-tests-private/pull/30074

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.

jcaamano · 2026-07-23T11:29:06Z

/override ci/prow/e2e-aws-ovn-fdp-qe

openshift-ci · 2026-07-23T11:30:56Z

@jcaamano: Overrode contexts on behalf of jcaamano: ci/prow/e2e-aws-ovn-fdp-qe

Details

In response to this:

/override ci/prow/e2e-aws-ovn-fdp-qe

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.

jcaamano · 2026-07-23T11:36:04Z

/retest-required

openshift-merge-bot · 2026-07-23T16:56:44Z

/retest-required

Remaining retests: 0 against base HEAD a9eba93 and 1 for PR HEAD 79bbb49 in total

jcaamano · 2026-07-23T21:47:09Z

/retest-required

openshift-ci · 2026-07-24T01:20:33Z

@jcaamano: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name	Commit	Details	Required	Rerun command
ci/prow/5.0-upgrade-from-stable-4.22-e2e-aws-ovn-upgrade	`79bbb49`	link	false	`/test 5.0-upgrade-from-stable-4.22-e2e-aws-ovn-upgrade`
ci/prow/5.0-upgrade-from-stable-4.22-e2e-gcp-ovn-upgrade	`79bbb49`	link	false	`/test 5.0-upgrade-from-stable-4.22-e2e-gcp-ovn-upgrade`

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.

jcaamano · 2026-07-24T10:50:45Z

/override ci/prow/e2e-gcp-ovn-techpreview

A job that we don't own with a 50% pass rate (periodic) cannot really be required. The problems cannot possibly be related to this change.
https://sippy.dptools.openshift.org/sippy-ng/jobs/5.0/analysis?filters=%7B%22items%22%3A%5B%7B%22columnField%22%3A%22name%22%2C%22operatorValue%22%3A%22equals%22%2C%22value%22%3A%22periodic-ci-openshift-release-main-ci-5.0-e2e-gcp-ovn-techpreview%22%7D%5D%7D

openshift-ci · 2026-07-24T10:51:40Z

@jcaamano: Overrode contexts on behalf of jcaamano: ci/prow/e2e-gcp-ovn-techpreview

Details

In response to this:

/override ci/prow/e2e-gcp-ovn-techpreview

A job with a 50% pass rate cannot really be required. The problems cannot possibly be related to this change.

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.

jcaamano · 2026-07-24T14:01:37Z

/retest-required

openshift-ci-robot · 2026-07-24T14:41:37Z

@jcaamano: Jira Issue Verification Checks: Jira Issue OCPBUGS-98619
✔️ This pull request was pre-merge verified.
✔️ All associated pull requests have merged.
✔️ All associated, merged pull requests were pre-merge verified.

Jira Issue OCPBUGS-98619 has been moved to the MODIFIED state and will move to the VERIFIED state when the change is available in an accepted nightly payload. 🕓

Details

In response to this:

bfdd opens 5 (2 IPv4 + 3 IPv6) UDP sockets against each VRF even if BFD has not been explicitly enabled on them. When using RouteAdvertisements with OVN-K CUDNs, this limits the scalability to ~200 of them assuming a default file descriptor limit of 1024. Bump it to 65536 which is in any case a much more reasonable limit for production network daemons.

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.

jcaamano · 2026-07-24T14:53:51Z

/cherry-pick release-4.22

openshift-cherrypick-robot · 2026-07-24T14:54:41Z

@jcaamano: new pull request created: #3090

Details

In response to this:

/cherry-pick release-4.22

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.

arkadeepsen · 2026-07-24T16:48:20Z

/jira backport release-4.21,release-4.20

openshift-ci-robot · 2026-07-24T16:48:23Z

@arkadeepsen: Missing required branches for backport chain:

release-4.22 OR openshift-4.22,

Details

In response to this:

/jira backport release-4.21,release-4.20

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.

arkadeepsen · 2026-07-24T16:49:41Z

/jira backport release-4.22,release-4.21,release-4.20

openshift-ci-robot · 2026-07-24T16:52:04Z

@arkadeepsen: The following backport issues have been created:

Jira Issue OCPBUGS-99744 for branch release-4.22
Jira Issue OCPBUGS-99747 for branch release-4.21
Jira Issue OCPBUGS-99749 for branch release-4.20

Queuing cherrypicks to the requested branches to be created after this PR merges:
/cherrypick release-4.22
/cherrypick release-4.21
/cherrypick release-4.20

Details

In response to this:

/jira backport release-4.22,release-4.21,release-4.20

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-cherrypick-robot · 2026-07-24T16:52:48Z

@openshift-ci-robot: new pull request created: #3091

Details

In response to this:

@arkadeepsen: The following backport issues have been created:

Jira Issue OCPBUGS-99744 for branch release-4.22

Jira Issue OCPBUGS-99747 for branch release-4.21

Jira Issue OCPBUGS-99749 for branch release-4.20

Queuing cherrypicks to the requested branches to be created after this PR merges:
/cherrypick release-4.22
/cherrypick release-4.21
/cherrypick release-4.20

In response to this:

/jira backport release-4.22,release-4.21,release-4.20

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.

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.

openshift-cherrypick-robot · 2026-07-24T16:53:30Z

@openshift-ci-robot: new pull request created: #3092

Details

In response to this:

@arkadeepsen: The following backport issues have been created:

Jira Issue OCPBUGS-99744 for branch release-4.22

Jira Issue OCPBUGS-99747 for branch release-4.21

Jira Issue OCPBUGS-99749 for branch release-4.20

Queuing cherrypicks to the requested branches to be created after this PR merges:
/cherrypick release-4.22
/cherrypick release-4.21
/cherrypick release-4.20

In response to this:

/jira backport release-4.22,release-4.21,release-4.20

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.

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.

openshift-cherrypick-robot · 2026-07-24T16:54:11Z

@openshift-ci-robot: new pull request could not be created: failed to create pull request against openshift/cluster-network-operator#release-4.22 from head openshift-cherrypick-robot:cherry-pick-3054-to-release-4.22: status code 422 not one of [201], body: {"message":"Validation Failed","errors":[{"resource":"PullRequest","code":"custom","message":"A pull request already exists for openshift-cherrypick-robot:cherry-pick-3054-to-release-4.22."}],"documentation_url":"https://docs.github.com/rest/pulls/pulls#create-a-pull-request","status":"422"}

Details

In response to this:

@arkadeepsen: The following backport issues have been created:

Jira Issue OCPBUGS-99744 for branch release-4.22

Jira Issue OCPBUGS-99747 for branch release-4.21

Jira Issue OCPBUGS-99749 for branch release-4.20

Queuing cherrypicks to the requested branches to be created after this PR merges:
/cherrypick release-4.22
/cherrypick release-4.21
/cherrypick release-4.20

In response to this:

/jira backport release-4.22,release-4.21,release-4.20

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.

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.

openshift-ci-robot added jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. labels Jul 15, 2026

openshift-ci Bot requested review from marty-power and miheer July 15, 2026 09:49

openshift-ci Bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Jul 15, 2026

openshift-ci-robot added the jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. label Jul 15, 2026

openshift-ci-robot removed the jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. label Jul 15, 2026

venkataanil approved these changes Jul 15, 2026

View reviewed changes

openshift-ci Bot assigned fedepaol Jul 15, 2026

openshift-ci Bot added the lgtm Indicates that a PR is ready to be merged. label Jul 15, 2026

openshift-ci-robot added the verified Signifies that the PR passed pre-merge verification criteria label Jul 15, 2026

openshift-ci Bot assigned jtaleric Jul 15, 2026

openshift-ci Bot removed the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Jul 22, 2026

openshift-merge-bot Bot merged commit 5c7f864 into openshift:master Jul 24, 2026
29 of 31 checks passed

openshift-cherrypick-robot mentioned this pull request Jul 24, 2026

[release-4.22] OCPBUGS-99744: Bump frr-k8s MAX_FDS from 1024 to 65536 #3090

Merged

openshift-cherrypick-robot mentioned this pull request Jul 24, 2026

[release-4.20] OCPBUGS-99749: Bump frr-k8s MAX_FDS from 1024 to 65536 #3091

Open

openshift-cherrypick-robot mentioned this pull request Jul 24, 2026

[release-4.21] OCPBUGS-99747: Bump frr-k8s MAX_FDS from 1024 to 65536 #3092

Open

Uh oh!

Conversation

jcaamano commented Jul 15, 2026

Uh oh!

openshift-ci-robot commented Jul 15, 2026

Uh oh!

openshift-merge-bot Bot commented Jul 15, 2026

Uh oh!

coderabbitai Bot commented Jul 15, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Walkthrough

Changes

Pre-merge checks failed

❌ Failed checks (4 errors)

Uh oh!

jcaamano commented Jul 15, 2026

Uh oh!

openshift-ci-robot commented Jul 15, 2026

Uh oh!

venkataanil left a comment

Choose a reason for hiding this comment

Uh oh!

fedepaol commented Jul 15, 2026

Uh oh!

openshift-merge-bot Bot commented Jul 15, 2026

Uh oh!

venkataanil commented Jul 15, 2026

Uh oh!

openshift-ci-robot commented Jul 15, 2026

Uh oh!

jtaleric commented Jul 15, 2026

Uh oh!

openshift-ci Bot commented Jul 15, 2026

Uh oh!

openshift-merge-bot Bot commented Jul 20, 2026

Uh oh!

openshift-merge-bot Bot commented Jul 21, 2026

Uh oh!

jcaamano commented Jul 22, 2026

Uh oh!

jcaamano commented Jul 22, 2026

Uh oh!

jcaamano commented Jul 22, 2026

Uh oh!

openshift-ci Bot commented Jul 22, 2026

Uh oh!

jcaamano commented Jul 22, 2026

Uh oh!

openshift-ci Bot commented Jul 22, 2026

Uh oh!

jcaamano commented Jul 22, 2026

Uh oh!

openshift-merge-bot Bot commented Jul 23, 2026

Uh oh!

jcaamano commented Jul 23, 2026

Uh oh!

openshift-ci Bot commented Jul 23, 2026

Uh oh!

jcaamano commented Jul 23, 2026

Uh oh!

openshift-ci Bot commented Jul 23, 2026

Uh oh!

jcaamano commented Jul 23, 2026

Uh oh!

openshift-merge-bot Bot commented Jul 23, 2026

Uh oh!

jcaamano commented Jul 23, 2026

Uh oh!

openshift-ci Bot commented Jul 24, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

jcaamano commented Jul 24, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

openshift-ci Bot commented Jul 24, 2026

Uh oh!

jcaamano commented Jul 24, 2026

Uh oh!

Uh oh!

openshift-ci-robot commented Jul 24, 2026

coderabbitai Bot commented Jul 15, 2026 •

edited

Loading

openshift-ci Bot commented Jul 24, 2026 •

edited

Loading

jcaamano commented Jul 24, 2026 •

edited

Loading