yahoo-eng-team team mailing list archive

[Rodolfo Alonso <2073613@xxxxxxxxxxxxxxxxxx>]

Public bug reported:

Since [1], present in OVN 21.03.0, the maintenance method "remove_duplicated_chassis_registers" is no longer needed. If ovn-controller is not stopped correctly, it will leave Chassis/Chassis_private in the SB database. However, ovn-controller no longer will try to reuse the stale records but will try to create new ones. If the stale records have no been manually deleted and ovn-controller tries to register a new Chassis with the same values, the DB will throw the following error:
"""
ovsdb_idl|WARN|transaction error: {"details":"Transaction causes multiple rows in \"Encap\" table to have identical values (geneve and \"172.19.0.100\") for index on columns \"type\" and \"ip\".  First row, with UUID ed386b5a-8900-4815-9cc2-3cd7154a3799, was inserted by this transaction.  Second row, with UUID de9b4bc7-eedb-489f-849f-d3dd55e14350, existed in the database before this transaction and was not modified by the transaction.","error":"constraint violation"}
"""

Because the minimum version tested and supported is 22.03, we can drop
this method as it won't be possible anymore to have two
Chassis/Chassis_Private registers pointing to the same host.

[1]https://github.com/ovn-
org/ovn/commit/fc359bfe934290baeeeed1bc78a3f2a919421fa3

** Affects: neutron
     Importance: Low
         Status: Confirmed

** Changed in: neutron
   Importance: Undecided => Low

** Changed in: neutron
       Status: New => Confirmed

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/2073613

Title:
  [OVN] Maintenance method "remove_duplicated_chassis_registers" is no
  longer needed

Status in neutron:
  Confirmed

Bug description:
  Since [1], present in OVN 21.03.0, the maintenance method "remove_duplicated_chassis_registers" is no longer needed. If ovn-controller is not stopped correctly, it will leave Chassis/Chassis_private in the SB database. However, ovn-controller no longer will try to reuse the stale records but will try to create new ones. If the stale records have no been manually deleted and ovn-controller tries to register a new Chassis with the same values, the DB will throw the following error:
  """
  ovsdb_idl|WARN|transaction error: {"details":"Transaction causes multiple rows in \"Encap\" table to have identical values (geneve and \"172.19.0.100\") for index on columns \"type\" and \"ip\".  First row, with UUID ed386b5a-8900-4815-9cc2-3cd7154a3799, was inserted by this transaction.  Second row, with UUID de9b4bc7-eedb-489f-849f-d3dd55e14350, existed in the database before this transaction and was not modified by the transaction.","error":"constraint violation"}
  """

  Because the minimum version tested and supported is 22.03, we can drop
  this method as it won't be possible anymore to have two
  Chassis/Chassis_Private registers pointing to the same host.

  [1]https://github.com/ovn-
  org/ovn/commit/fc359bfe934290baeeeed1bc78a3f2a919421fa3

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/2073613/+subscriptions