yahoo-eng-team team mailing list archive

[Ebbex <1687896@xxxxxxxxxxxxxxxxxx>]

Public bug reported:

I'm running neutron-api under uwsgi, but noticed it's not doing any rpc stuff,
so I figure that's what "neutron-rpc-server" is for. But it fails to start on
configuration that works under the normal "neutron-server".

Traceback (most recent call last):
  File "/usr/local/bin/neutron-rpc-server", line 10, in <module>
    sys.exit(main_rpc_eventlet())
  File "/opt/stack/neutron/neutron/cmd/eventlet/server/__init__.py", line 23, in main_rpc_eventlet
    server.boot_server(rpc_eventlet.eventlet_rpc_server)
  File "/opt/stack/neutron/neutron/server/__init__.py", line 42, in boot_server
    server_func()
  File "/opt/stack/neutron/neutron/server/rpc_eventlet.py", line 33, in eventlet_rpc_server
    rpc_workers_launcher = service.start_rpc_workers()
  File "/opt/stack/neutron/neutron/service.py", line 269, in start_rpc_workers
    rpc_workers = _get_rpc_workers()
  File "/opt/stack/neutron/neutron/service.py", line 163, in _get_rpc_workers
    if not plugin.rpc_workers_supported():
AttributeError: 'NoneType' object has no attribute 'rpc_workers_supported'

In neutron/neutron/service.py:
from neutron_lib.plugins import directory

def _get_rpc_workers():
    plugin = directory.get_plugin()
    service_plugins = directory.get_plugins().values()

I'm not sure what directory.get_plugin() does or how it works, but it doesn't
return anything of use apparently.


You should be able to reproduce quite easily by running

neutron-server --config-file neutron.conf
neutron-rpc-server --config-file neutron.conf

** Affects: neutron
     Importance: Undecided
         Status: New

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1687896

Title:
  neutron-rpc-server fails to start on configuration that works under
  neutron-server

Status in neutron:
  New

Bug description:
  I'm running neutron-api under uwsgi, but noticed it's not doing any rpc stuff,
  so I figure that's what "neutron-rpc-server" is for. But it fails to start on
  configuration that works under the normal "neutron-server".

  Traceback (most recent call last):
    File "/usr/local/bin/neutron-rpc-server", line 10, in <module>
      sys.exit(main_rpc_eventlet())
    File "/opt/stack/neutron/neutron/cmd/eventlet/server/__init__.py", line 23, in main_rpc_eventlet
      server.boot_server(rpc_eventlet.eventlet_rpc_server)
    File "/opt/stack/neutron/neutron/server/__init__.py", line 42, in boot_server
      server_func()
    File "/opt/stack/neutron/neutron/server/rpc_eventlet.py", line 33, in eventlet_rpc_server
      rpc_workers_launcher = service.start_rpc_workers()
    File "/opt/stack/neutron/neutron/service.py", line 269, in start_rpc_workers
      rpc_workers = _get_rpc_workers()
    File "/opt/stack/neutron/neutron/service.py", line 163, in _get_rpc_workers
      if not plugin.rpc_workers_supported():
  AttributeError: 'NoneType' object has no attribute 'rpc_workers_supported'

  In neutron/neutron/service.py:
  from neutron_lib.plugins import directory

  def _get_rpc_workers():
      plugin = directory.get_plugin()
      service_plugins = directory.get_plugins().values()

  I'm not sure what directory.get_plugin() does or how it works, but it doesn't
  return anything of use apparently.

  
  You should be able to reproduce quite easily by running

  neutron-server --config-file neutron.conf
  neutron-rpc-server --config-file neutron.conf

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1687896/+subscriptions