Devstack: Neutron did not start

Bug #1689483 reported by YujiAzama
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
networking-calico
Fix Released
Undecided
Nell Jerram

Bug Description

In Devstack deployment, Neutron did not start.

service_plugin in neutron.conf should be deleted.

The devstack log is shown below:

2017-05-09 03:49:16.667 | + lib/neutron-legacy:start_neutron_service_and_check:470 : echo 'Waiting for Neutron to start...'
2017-05-09 03:49:16.667 | Waiting for Neutron to start...
2017-05-09 03:49:16.669 | + lib/neutron-legacy:start_neutron_service_and_check:472 : local 'testcmd=wget --no-proxy -q -O- http://158.69.65.17:9696'
2017-05-09 03:49:16.670 | + lib/neutron-legacy:start_neutron_service_and_check:473 : test_with_retry 'wget --no-proxy -q -O- http://158.69.65.17:9696' 'Neutron did not start' 60
2017-05-09 03:49:16.672 | + functions-common:test_with_retry:2441 : local 'testcmd=wget --no-proxy -q -O- http://158.69.65.17:9696'
2017-05-09 03:49:16.674 | + functions-common:test_with_retry:2442 : local 'failmsg=Neutron did not start'
2017-05-09 03:49:16.676 | + functions-common:test_with_retry:2443 : local until=60
2017-05-09 03:49:16.678 | + functions-common:test_with_retry:2444 : local sleep=0.5
2017-05-09 03:49:16.680 | + functions-common:test_with_retry:2446 : time_start test_with_retry
2017-05-09 03:49:16.681 | + functions-common:time_start:2489 : local name=test_with_retry
2017-05-09 03:49:16.684 | + functions-common:time_start:2490 : local start_time=
2017-05-09 03:49:16.686 | + functions-common:time_start:2491 : [[ -n '' ]]
2017-05-09 03:49:16.688 | ++ functions-common:time_start:2494 : date +%s
2017-05-09 03:49:16.691 | + functions-common:time_start:2494 : _TIME_START[$name]=1494301756
2017-05-09 03:49:16.693 | + functions-common:test_with_retry:2447 : timeout 60 sh -c 'while ! wget --no-proxy -q -O- http://158.69.65.17:9696; do sleep 0.5; done'
2017-05-09 03:50:16.704 | + functions-common:test_with_retry:2448 : die 2448 'Neutron did not start'
2017-05-09 03:50:16.706 | + functions-common:die:186 : local exitcode=0
2017-05-09 03:50:16.709 | [Call Trace]
2017-05-09 03:50:16.709 | ./stack.sh:1272:start_neutron_service_and_check
2017-05-09 03:50:16.709 | /opt/stack/new/devstack/lib/neutron-legacy:473:test_with_retry
2017-05-09 03:50:16.709 | /opt/stack/new/devstack/functions-common:2448:die
2017-05-09 03:50:16.713 | [ERROR] /opt/stack/new/devstack/functions-common:2448 Neutron did not start
2017-05-09 03:50:17.717 | Error on exit

The neutron.conf is shown below:

[DEFAULT]
service_plugins = neutron.services.l3_router.l3_router_plugin.L3RouterPlugin,neutron.services.metering.metering_plugin.MeteringPlugin
rpc_state_report_workers = 0
api_workers = 2
notify_nova_on_port_data_changes = True
notify_nova_on_port_status_changes = True
auth_strategy = keystone
allow_overlapping_ips = True
debug = True
core_plugin = calico
transport_url = rabbit://stackrabbit:secretrabbit@158.69.65.17:5672/
logging_exception_prefix = ERROR %(name)s %(instance)s
logging_default_format_string = %(levelname)s %(name)s [-] %(instance)s%(color)s%(message)s
logging_context_format_string = %(levelname)s %(name)s [%(request_id)s %(project_name)s %(user_name)s] %(instance)s%(message)s
logging_debug_format_suffix = {{(pid=%(process)d) %(funcName)s %(pathname)s:%(lineno)d}}
bind_host = 0.0.0.0
use_syslog = False
state_path = /opt/stack/data/neutron

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to networking-calico (master)

Fix proposed to branch: master
Review: https://review.openstack.org/463498

Changed in networking-calico:
assignee: nobody → Neil Jerram (neil-jerram)
status: New → In Progress
Revision history for this message
Nell Jerram (neil-jerram) wrote :

Thanks Azama-san. Please note that at http://git.openstack.org/cgit/openstack/networking-calico/tree/devstack/plugin.sh#n160 we have (already):

      inidelete $NEUTRON_CONF DEFAULT service_plugins

So I think the problem is that the DevStack configuration for Neutron has just changed, so that it rewrites service_plugins after that point. I think it is configure_neutron_after_post_config that does that.

So I'm hoping this will be fixed by adding

Q_SERVICE_PLUGIN_CLASSES=

to the settings of the networking-calico plugin.

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to networking-calico (master)

Reviewed: https://review.openstack.org/463498
Committed: https://git.openstack.org/cgit/openstack/networking-calico/commit/?id=4234da5d475d116e310eda54bc370dd5a2e69e3b
Submitter: Jenkins
Branch: master

commit 4234da5d475d116e310eda54bc370dd5a2e69e3b
Author: Neil Jerram <email address hidden>
Date: Tue May 9 10:09:06 2017 +0100

    DevStack plugin: fix for recent neutron and devstack changes

    - Set variables so that configure_neutron_after_post_config does not set
      service_plugins. (What changed here has that neutron-legacy's setting
      of service_plugins was deferred. Previously neutron-legacy set some
      value, and then the networking-calico deleted that. Now
      neutron-legacy sets its value after the last time that the
      networking-calico plugin code has run.)

    - Don't use systemd, as our running of auto-bird-conf is not
      systemd-compatible yet.

    - Remove 'coverage=eventlet' declaration from .coveragerc.

    - Also disable q-metering, as we have no use for it.

    Change-Id: If08b226ce53051e50030ee961a9b05a62d44b204
    Closes-Bug: #1689483
    Closes-Bug: #1690101

Changed in networking-calico:
status: In Progress → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.