ovn-chassis and ovn-central charms sync ovn packages from different repos, because of different versions in both of them: | ovn-22.03 | focal-updates | linux-any all
ovn-central (focal-updates/yoga/main): ovn-common | 22.03.2-0ubuntu0.22.04.1~cloud1 | yoga | focal-updates | linux-any all
ovn-chassis (focal-updates/ovn-22.03/main): ovn-common | 22.03.0-0ubuntu1~cloud0
This needs to be addressed, as during migration from ovs to ovn this causes the ovn-chassis to not be able to register with the central units with:
2023-08-10T07:28:24.235Z|02840|main|WARN|controller version - 22.03.0-20.21.0-58.3 mismatch with northd version - 22.03.2-20.21.0-61.4
The workaround is to use this to prevent the check, but if left there it's dangerous during future upgrades of ovn:
ovs-vsctl set open . external_ids:ovn-match-northd-version="false"
ovn-chassis and ovn-central charms sync ovn packages from different repos, because of different versions in both of them:
| ovn-22.03 | focal-updates | linux-any all
ovn-central (focal- updates/ yoga/main) : 0ubuntu0. 22.04.1~ cloud1 | yoga | focal-updates | linux-any all
ovn-common | 22.03.2-
ovn-chassis (focal- updates/ ovn-22. 03/main) : 0ubuntu1~ cloud0
ovn-common | 22.03.0-
This needs to be addressed, as during migration from ovs to ovn this causes the ovn-chassis to not be able to register with the central units with:
2023-08- 10T07:28: 24.235Z| 02840|main| WARN|controller version - 22.03.0- 20.21.0- 58.3 mismatch with northd version - 22.03.2- 20.21.0- 61.4
The workaround is to use this to prevent the check, but if left there it's dangerous during future upgrades of ovn:
ovs-vsctl set open . external_ ids:ovn- match-northd- version= "false"