Number of q-plugin and q-l3-plugin consumer is not equal

[Ksenia Svechnikova]

Steps to reproduce:
MOS 7.0 (#301)
1. Deploy MOS (3+1) with Neutron with DVR enabled.
2. Check number of consumers rabbitmqctl list_queues consumers name | grep plugin$

Actual results:

root@node-1:~# rabbitmqctl list_queues consumers name | grep plugin$
3 q-metering-plugin
15 q-reports-plugin
36 q-plugin
39 q-l3-plugin

There are 36 for q-plugin and 39 for q-l3-plugin

[Eugene Nikanorov (enikanorov)]

The root cause is in the difference of how rpc listeners are started.
core plugin (ml2) doesn't start rpc listeners in __init__ method, unlike l3_router plugin.

So for l3 queues we have rpc_workers+1 listener (+1 goes from parent process).
For cases when rpc_workers > 0, q-plugin is only consumed from rpc_workers, but not from the parent process.

This doesn't indicate any malfunction and we don't need to fix it.

[Inessa Vasilevskaya (ivasilevskaya)]

As Eugene pointed out, the number of consumers match expectations. Propose won't fix status.