Description of problem:
Right now, puppet/services/neutron-api.yaml sets "neutron::servers::api_workers" and "neutron::servers::rpc_workers" from the t-h-t param "NeutronWorkers".
In the case of OVN, we do not need rpc workers at all (unless dhcp agent is used).
We should introduce a new t-h-t param for rpc_workers.
Version-Release number of selected component (if applicable):
How reproducible:
Steps to Reproduce:
1.
2.
3.
Actual results:
Expected results:
Additional info:
In OSP13 puddle : 13.0-RHEL-7/2018-11-07.3/
I saw in neutron.conf
# Number of RPC worker processes for service. (integer value)
#rpc_workers = 1
rpc_workers=4
[root@controller-0 ~]# rpm -qa | grep python-networking-ovn
python-networking-ovn-4.0.3-1.el7ost.noarch
Is part of default deployment is it ok?
Comment 6Daniel Alvarez Sanchez
2018-11-11 13:55:11 UTC
Patches are merged upstream in master and under review in stable/rocky on THT. Changing the component now
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
https://access.redhat.com/errata/RHBA-2019:0448