[OVN] Regression when using ML2/OVN with Neutron DHCP agent
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
neutron |
In Progress
|
Critical
|
Lucas Alvares Gomes |
Bug Description
In an attempt to minimize the number of connections to the OVSDBs the ML2/OVN driver no longer connects to the OVN dbs if the Neutron worker is a RpcWorker [0].
This introduced a regression where when ML2/OVN is deployed along with the Neutron DHCP server (e.g for baremetal provisioning) the DHCP agent is no longer able to create the DHCP port and fails with the following error message:
2021-07-13 13:36:18.116 17 ERROR neutron.
2021-07-13 13:36:18.116 17 ERROR neutron.
2021-07-13 13:36:18.116 17 ERROR neutron.
2021-07-13 13:36:18.116 17 ERROR neutron.
2021-07-13 13:36:18.116 17 ERROR neutron.
2021-07-13 13:36:18.116 17 ERROR neutron.
2021-07-13 13:36:18.116 17 ERROR neutron.
2021-07-13 13:36:18.116 17 ERROR neutron.
See full traceback at: http://
[0] https:/
Hello:
In a "normal" deployment (without baremetal chassis) we don't use DHCP agents; this is why, as you commented, we removed the OVSDBs connectivity from other classes than WorkerService and MaintenanceWorker.
In this specific case, I think https:/ /review. opendev. org/c/openstack /neutron/ +/795781 is what you are looking for. This patch will allow you to define more server classes (RpcWorker in your case) that could have OVN IDL connectivity.
Does it work for you?
Regards.