| 1 |
--- |
| 2 |
issues: |
| 3 |
- | |
| 4 |
When using ML2/OVN, during an upgrade procedure, the OVS system-id stored |
| 5 |
value can be changed. The ovn-controller service will create the "Chassis" |
| 6 |
and "Chassis_Private" registers based on this OVS system-id. If the |
| 7 |
ovn-controller process is not gracefully stopped, that could lead to the |
| 8 |
existence of duplicated "Chassis" and "Chassis_Private" registers in the |
| 9 |
OVN Southbound database. |
| 10 |
fixes: |
| 11 |
- | |
| 12 |
A new OVN maintenance method ``remove_duplicated_chassis_registers`` is |
| 13 |
added. This method will periodically check the OVN Southbound "Chassis" |
| 14 |
and "Chassis_Private" tables looking for duplicated registers. The older |
| 15 |
ones (based on the "Chassis_Private.nb_cfg_timestamp" value) will be |
| 16 |
removed when more than one register has the same hostname, that should |
| 17 |
be unique. |