Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
The FDP team is no longer accepting new bugs in Bugzilla. Please report your issues under FDP project in Jira. Thanks.

Bug 2232516

Summary: "openvswitch: cpu_id mismatch with handler threads" every couple of seconds
Product: Red Hat Enterprise Linux Fast Datapath Reporter: Chen <cchen>
Component: openvswitch2.17Assignee: Michael Santana <msantana>
Status: CLOSED EOL QA Contact: ovs-qe
Severity: medium Docs Contact:
Priority: unspecified    
Version: RHEL 8.0CC: ctrautma, echaudro, jhsiao, msantana, ralongi
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2024-10-08 17:49:14 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Chen 2023-08-17 08:30:17 UTC 
Description of problem:

Aug 17 07:33:32 XXXX kernel: openvswitch: cpu_id mismatch with handler threads
Aug 17 07:33:37 XXXX kernel: openvswitch: cpu_id mismatch with handler threads
Aug 17 07:33:37 XXXX kernel: openvswitch: cpu_id mismatch with handler threads
Aug 17 07:33:37 XXXX kernel: openvswitch: cpu_id mismatch with handler threads

Version-Release number of selected component (if applicable):

OpenShift 4.11.41
openvswitch2.17-2.17.0-88.el8fdp.x86_64

How reproducible:

100% in customer's node

Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

I noticed we have similar bug [1] but the version in this bug should be newer than the one in [1] 

[1] https://bugzilla.redhat.com/show_bug.cgi?id=2102449
Comment 5 Michael Santana 2023-08-31 07:14:57 UTC 
Hi Chen,

Yes, we would need some info from customer,

First we would like to restart the ovs-vswitchd process. We would like to capture the logs when OVS starts up. One of the logs OVS captures is the number of CPUs it detected and how it is going to decide how many threads it will create. Unfortunately those logs were lost due to log rotate which is why we need to restart OVS to see those logs when OVS starts. The logs should be located at /var/log/openvswitch/ovs-vswitchd.log

We are looking for logs that look like this:
2021-09-20T01:15:32.751Z|00032|ofproto_dpif_upcall|INFO|Overriding n-handler-threads to 24, setting n-revalidator-threads to 7
2021-09-20T01:15:32.751Z|00033|ofproto_dpif_upcall|INFO|Starting 31 threads


Some house keeping item questions to make sure we are all on the same page

* The customer should be running in dispatch mode according to the OVS version, but please double check. Run "ovs-appctl dpif-netlink/dispatch-mode"

* Is there any affinity, or system tunning, or isolated cores? Not any that I could see from the sos report, but just double checking

* Did anything change in the customer environment before seeing all these dispatch log messages?


Assuming that there is no affinity and no tunning or isolated cores, ovs-vswitchd should create 28 handler threads which is the number of cores on the system

Now, this is is a bit of a mad man's ramblings: it is strange that the number actual handler threads created is 17, which is the next prime after the number 14
Comment 7 ovs-bot 2024-10-08 17:49:14 UTC 
This bug did not meet the criteria for automatic migration and is being closed.
If the issue remains, please open a new ticket in https://issues.redhat.com/browse/FDP
Comment 8 Red Hat Bugzilla 2025-02-06 04:25:24 UTC 
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 120 days