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 1980269 - [ovsdbapp] KeyError raised after ovs probe inactivity
Summary: [ovsdbapp] KeyError raised after ovs probe inactivity
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: python-ovsdbapp
Version: 16.2 (Train)
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
: ---
Assignee: Jakub Libosvar
QA Contact: Toni Freger
: 1987671 (view as bug list)
Depends On:
Blocks: 1940824
TreeView+ depends on / blocked
Reported: 2021-07-08 08:34 UTC by Ales Musil
Modified: 2023-07-13 01:11 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed:
Target Upstream Version:

Attachments (Terms of Use)

Description Ales Musil 2021-07-08 08:34:49 UTC
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

Comment 3 Timothy Redaelli 2021-11-05 11:11:24 UTC
*** Bug 1987671 has been marked as a duplicate of this bug. ***

Note You need to log in before you can comment on or make changes to this bug.