Skip to content

Conversation

@openshift-cherrypick-robot

This is an automated cherry-pick of #2427

/assign trozet

flavio-fernandes and others added 7 commits January 29, 2025 12:53
Signed-off-by: Flavio Fernandes <ffernandes@nvidia.com>
Signed-off-by: Flavio Fernandes <ffernandes@nvidia.com>
ShallowClone has to copy all factories.

Signed-off-by: Patryk Diak <pdiak@redhat.com>
Commit 6dda0b5 ("factory: Bump the event queue size to 1K.")
increased the event queue size to 1K events.  However, in combination
with fe17136 ("factory: Reduce contention on informer locks.")
which configures 201 internal informers this might end up using too much
memory in cases when controllers cannot consume events as fast as
they're queued by the kube API.

For each kubernetes API object type we consume:
  N_internal_informers x N_queues x N_events x sizeof(event)
memory.

That currently translates to:
  N_internal_informers = 201
  N_queues = 15
  N_events = 1000
  sizeof(event) = 32B
  => ~92MB of memory per object type

Given that ovn-kubernetes processes need to be informed about multiple
object types this can grow to a significantly large number when
controllers that are supposed to consume events from the internal
informer queues are slow.

Reduce the queue size, making it 100, in order to lower the worst case
scenario memory usage:
  N_internal_informers = 201
  N_queues = 15
  N_events = 100
  sizeof(event) = 32B
  => ~9.2MB of memory per object type

Signed-off-by: Dumitru Ceara <dceara@redhat.com>
Signed-off-by: Patryk Diak <pdiak@redhat.com>
Previously, if a new NAD was added to an existing network after a pod
referencing it, the pod would never start. This is fixed by reconciling
pending pods when the secondary network controller reconciles a new NAD.

Signed-off-by: Patryk Diak <pdiak@redhat.com>
Fixes NPE seen at:
openshift#2427 (comment)

Certain network types may not have a pod handler or retry framework for
cluster manager.

Signed-off-by: Tim Rozet <trozet@redhat.com>
@openshift-ci-robot
Copy link
Contributor

openshift-ci-robot commented Jan 29, 2025

@openshift-cherrypick-robot: Ignoring requests to cherry-pick non-bug issues: SDN-4930

Details

In response to this:

This is an automated cherry-pick of #2427

/assign trozet

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 abhat and tssurya January 29, 2025 12:54
@trozet
Copy link
Contributor

trozet commented Jan 29, 2025

/label backport-risk-assessed

@openshift-ci openshift-ci bot added the backport-risk-assessed Indicates a PR to a release branch has been evaluated and considered safe to accept. label Jan 29, 2025
@trozet
Copy link
Contributor

trozet commented Jan 29, 2025

/approve

@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, 2025
@jluhrsen
Copy link
Contributor

not worried about these jobs as the failures did not seem related to this PR, but at least one is required and I think the others should pass anyway. let's re-run:

/test 4.18-upgrade-from-stable-4.17-e2e-gcp-ovn-rt-upgrade
/test e2e-aws-ovn-single-node-techpreview
/test e2e-metal-ipi-ovn-ipv6-techpreview
/test okd-scos-e2e-aws-ovn

two flakes:

  1. e2e-metal-ipi-ovn-techpreview

when using openshift ovn-kubernetes created using UserDefinedNetwork is isolated from the default network with L2 primary UDN

  1. e2e-azure-ovn-techpreview

when using openshift ovn-kubernetes created using NetworkAttachmentDefinitions is isolated from the default network with L3 primary UDN

@jluhrsen
Copy link
Contributor

jluhrsen commented Jan 29, 2025

/retitle [release-4.18] OCPBUGS-48710, SDN-4930: Downstream Merge [01-28-2025]

@openshift-ci openshift-ci bot changed the title [release-4.18] SDN-4930: Downstream Merge [01-28-2025] [release-4.18] OCPBUGS-48710, SDN-4930: Downstream Merge [01-28-2025] Jan 29, 2025
@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, 2025
@openshift-ci-robot
Copy link
Contributor

openshift-ci-robot commented Jan 29, 2025

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

7 validation(s) were run on this bug
  • bug is open, matching expected state (open)
  • bug target version (4.18.0) matches configured target version for branch (4.18.0)
  • bug is in the state ASSIGNED, which is one of the valid states (NEW, ASSIGNED, POST)
  • release note type set to "Release Note Not Required"
  • dependent bug Jira Issue OCPBUGS-48709 is in the state Verified, which is one of the valid states (MODIFIED, ON_QA, VERIFIED)
  • dependent Jira Issue OCPBUGS-48709 targets the "4.19.0" version, which is one of the valid target versions: 4.19.0
  • bug has dependents

Requesting review from QA contact:
/cc @anuragthehatter

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

This pull request references SDN-4930 which is a valid jira issue.

Details

In response to this:

This is an automated cherry-pick of #2427

/assign trozet

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-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. label Jan 29, 2025
@jluhrsen
Copy link
Contributor

/lgtm
/hold
will gate on this hold but gonna try to get all other labels here now

@openshift-ci openshift-ci bot added do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. lgtm Indicates that a PR is ready to be merged. labels Jan 29, 2025
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Jan 29, 2025

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: jluhrsen, openshift-cherrypick-robot, trozet

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

@asood-rh
Copy link
Contributor

/label cherry-pick-approved

@openshift-ci openshift-ci bot added the cherry-pick-approved Indicates a cherry-pick PR into a release branch has been approved by the release branch manager. label Jan 29, 2025
@jluhrsen
Copy link
Contributor

/test e2e-aws-ovn-single-node-techpreview
/test 4.18-upgrade-from-stable-4.17-e2e-gcp-ovn-rt-upgrade

@jluhrsen
Copy link
Contributor

/test e2e-aws-ovn-single-node-techpreview

@jluhrsen
Copy link
Contributor

/hold cancel

@openshift-ci openshift-ci bot removed the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Jan 30, 2025
@openshift-ci-robot
Copy link
Contributor

/retest-required

Remaining retests: 0 against base HEAD b41a3ab and 2 for PR HEAD 51322a0 in total

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Jan 30, 2025

@openshift-cherrypick-robot: 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/e2e-metal-ipi-ovn-ipv6-techpreview 51322a0 link false /test e2e-metal-ipi-ovn-ipv6-techpreview
ci/prow/security 51322a0 link false /test security

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 f3d89b2 into openshift:release-4.18 Jan 30, 2025
37 of 39 checks passed
@openshift-ci-robot
Copy link
Contributor

@openshift-cherrypick-robot: Jira Issue OCPBUGS-48710: All pull requests linked via external trackers have merged:

Jira Issue OCPBUGS-48710 has been moved to the MODIFIED state.

Details

In response to this:

This is an automated cherry-pick of #2427

/assign trozet

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

[ART PR BUILD NOTIFIER]

Distgit: ovn-kubernetes-base
This PR has been included in build ose-ovn-kubernetes-base-container-v4.18.0-202501301232.p0.gf3d89b2.assembly.stream.el9.
All builds following this will include this PR.

@openshift-bot
Copy link
Contributor

[ART PR BUILD NOTIFIER]

Distgit: ovn-kubernetes-microshift
This PR has been included in build ovn-kubernetes-microshift-container-v4.18.0-202501301232.p0.gf3d89b2.assembly.stream.el9.
All builds following this will include this PR.

@openshift-bot
Copy link
Contributor

[ART PR BUILD NOTIFIER]

Distgit: ose-ovn-kubernetes
This PR has been included in build ose-ovn-kubernetes-container-v4.18.0-202501301232.p0.gf3d89b2.assembly.stream.el9.
All builds following this will include this PR.

@openshift-merge-robot
Copy link
Contributor

Fix included in accepted release 4.18.0-0.nightly-2025-06-26-034047

@openshift-merge-robot
Copy link
Contributor

Fix included in accepted release 4.18.0-0.nightly-2025-10-23-005402

@openshift-merge-robot
Copy link
Contributor

Fix included in accepted release 4.18.0-0.nightly-2025-12-24-222251

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.

Projects

None yet

Development

Successfully merging this pull request may close these issues.