Bug 2228643

Summary: ovs-vswitchd crashed with ''ovs|00002|util(pmd-xxx)|EMER|../lib/conntrack.c:1063: assertion conn->conn_type == CT_CONN_TYPE_DEFAULT failed in conn_update_state()'
Product: Red Hat OpenStack Reporter: Keigo Noha <knoha>
Component: openvswitchAssignee: RHOSP:NFV_Eng <rhosp-nfv-int>
Status: CLOSED ERRATA QA Contact: Eran Kuris <ekuris>
Severity: high Docs Contact:
Priority: high    
Version: 17.1 (Wallaby)CC: apevec, bcafarel, cfontain, chrisw, ekuris, emacchi, eshulman, fleitner, gurpsing, hakhande, jmarti, jschluet, lhh, lsvaty, mariel, mblue, mburns, mdemaced, migawa, mori, mschindl, pgrist, rhosp-nfv-int, vchundur, zgreenbe
Target Milestone: z2Keywords: Triaged
Target Release: 17.1Flags: vchundur: needinfo+
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: openvswitch3.1-3.1.0-52.el9fdp Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
: 2247348 (view as bug list) Environment:
Last Closed: 2024-01-16 14:30:09 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:
Bug Depends On: 2230449    
Bug Blocks: 2222869, 2247348    

Description Keigo Noha 2023-08-03 00:56:53 UTC
Description of problem:
ovs-vswitchd crashed with ''ovs|00002|util(pmd-xxx)|EMER|../lib/conntrack.c:1063: assertion conn->conn_type == CT_CONN_TYPE_DEFAULT failed in conn_update_state()'

The crash happened repeatedly and it blocks the network communication of VMs.

Version-Release number of selected component (if applicable):
openvswitch3.1-3.1.0-14.el9fdp.x86_64

How reproducible:
Frequently happens

Steps to Reproduce:
1. Deploy RHOSP17.1 Beta
2. Deploy OCP4.12 IPI
3. While the OCP IPI installation, ovs-vswitchd crashes.

Actual results:
ovs-vswitchd crashed

Expected results:
ovs-vswitchd doesn't crash.

Additional info:
The similar issue is reported at https://www.mail-archive.com/ovs-discuss@openvswitch.org/msg08945.html

Comment 59 Ziv Greenberg 2023-12-07 14:04:41 UTC
Hi,

I was able to verify the proposed fix.
The OCP 4.12 cluster has been installed successfully by using ovs-dpdk as a main management network for the nodes.


[stack@undercloud-0 ~]$ cat core_puddle_version
RHOS-17.1-RHEL-9-20231122.n.1


[root@computeovndpdksriov-0 ~]# rpm -qa | grep openvswitch3
openvswitch3.1-3.1.0-54.el9fdp.x86_64


[root@computeovndpdksriov-0 ~]# ovs-vsctl --version
ovs-vsctl (Open vSwitch) 3.1.3


[stack@undercloud-0 ~]$ oc get clusterversion
NAME      VERSION                              AVAILABLE   PROGRESSING   SINCE   STATUS
version   4.12.0-0.nightly-2023-12-07-042643   True        False         4h56m   Cluster version is 4.12.0-0.nightly-2023-12-07-042643


Thanks
Ziv

Comment 60 Ziv Greenberg 2023-12-07 14:05:24 UTC
Hi,

I was able to verify the proposed fix.
The OCP 4.12 cluster has been installed successfully by using ovs-dpdk as a main management network for the nodes.


[stack@undercloud-0 ~]$ cat core_puddle_version
RHOS-17.1-RHEL-9-20231122.n.1


[root@computeovndpdksriov-0 ~]# rpm -qa | grep openvswitch3
openvswitch3.1-3.1.0-54.el9fdp.x86_64


[root@computeovndpdksriov-0 ~]# ovs-vsctl --version
ovs-vsctl (Open vSwitch) 3.1.3


[stack@undercloud-0 ~]$ oc get clusterversion
NAME      VERSION                              AVAILABLE   PROGRESSING   SINCE   STATUS
version   4.12.0-0.nightly-2023-12-07-042643   True        False         4h56m   Cluster version is 4.12.0-0.nightly-2023-12-07-042643


Thanks
Ziv

Comment 61 Ziv Greenberg 2023-12-07 14:05:35 UTC
Hi,

I was able to verify the proposed fix.
The OCP 4.12 cluster has been installed successfully by using ovs-dpdk as a main management network for the nodes.


[stack@undercloud-0 ~]$ cat core_puddle_version
RHOS-17.1-RHEL-9-20231122.n.1


[root@computeovndpdksriov-0 ~]# rpm -qa | grep openvswitch3
openvswitch3.1-3.1.0-54.el9fdp.x86_64


[root@computeovndpdksriov-0 ~]# ovs-vsctl --version
ovs-vsctl (Open vSwitch) 3.1.3


[stack@undercloud-0 ~]$ oc get clusterversion
NAME      VERSION                              AVAILABLE   PROGRESSING   SINCE   STATUS
version   4.12.0-0.nightly-2023-12-07-042643   True        False         4h56m   Cluster version is 4.12.0-0.nightly-2023-12-07-042643


Thanks
Ziv

Comment 68 errata-xmlrpc 2024-01-16 14:30:09 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (Red Hat OpenStack Platform 17.1.2 bug fix and enhancement advisory), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2024:0209

Comment 69 Red Hat Bugzilla 2024-06-07 04:25:10 UTC
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 120 days