neutron

  1. Bug #1935888
  2. Comment #3

Comment 3 for bug 1935888

Revision history for this message
Rodolfo Alonso (rodolfo-alonso-hernandez) wrote :

Hi zhangtongjian:

I had the same question as Terry. Reviewing the links you provided, I think what you are saying is that in the maintenance worker, spawned once by all servers, creates one single OVN client, with one unique OVN NB IDL instance.

In "DBInconsistenciesPeriodics", we set a lock named "ovn_db_inconsistencies_periodics". This class methods check the lock status but not the OvnNbSynchronizer" class, sharing the same NB_IDL. Because of that, you see the txn.NOT_LOCKED errors in some servers.

Is that what you are reporting?

Regards.