Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at

Bug 1987669

Summary: [ovsdbapp] KeyError raised after ovs probe inactivity
Product: Red Hat OpenStack Reporter: Timothy Redaelli <tredaelli>
Component: python-ovsdbappAssignee: Terry Wilson <twilson>
Status: NEW --- QA Contact: Toni Freger <tfreger>
Severity: urgent Docs Contact:
Priority: high    
Version: 16.2 (Train)   
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Timothy Redaelli 2021-11-05 11:06:50 UTC
+++ This bug was initially created as a clone of Bug #1980269 +++

Description of problem:
The call to ovsdbapp command that changes component in ovn DB fails with 
KeyError: UUID('x-y-z'), this happens right after:
ERROR   (Thread-3) [ovsdbapp.backend.ovs_idl.vlog] ssl: no response to inactivity probe after 5 seconds, disconnecting (reconnect:123)

It seems that the connection is disrupted and the ovsdbapp internal state 
is corrupted. It only happens one time after restarting ovirt-provider-ovn 
which uses ovsdbapp to communicate with ovn database. The ovn network is actually created even if we get the key error. 

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

How reproducible:

Steps to Reproduce:
1. systemctl restart ovirt-provider-ovn
2. Run

Actual results:
Fails with KeyError: UUID('x-y-z')

Expected results:
Should pass