devstack-failing-due-to-no-neutron-configs

Bug #1532941 reported by Devdatta Kulkarni
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Solum
Invalid
High
Unassigned

Bug Description

Creating a devstack environment is failing in stack.sh as there are no neutron configuration files getting created.

==> devstack: 2016-01-11 20:12:05.486 | + is_service_enabled neutron
==> devstack: 2016-01-11 20:12:05.488 | + return 0
==> devstack: 2016-01-11 20:12:05.488 | + echo_summary 'Configuring Neutron'
==> devstack: 2016-01-11 20:12:05.489 | + [[ -t 3 ]]
==> devstack: 2016-01-11 20:12:05.489 | + echo -e Configuring Neutron
==> devstack: 2016-01-11 20:12:05.489 | + configure_neutron
==> devstack: 2016-01-11 20:12:05.489 | + _configure_neutron_common
==> devstack: 2016-01-11 20:12:05.489 | + _create_neutron_conf_dir
==> devstack: 2016-01-11 20:12:05.489 | + sudo install -d -o vagrant /etc/neutron
==> devstack: 2016-01-11 20:12:05.494 | + cp /opt/stack/neutron/etc/neutron.conf /etc/neutron/neutron.conf
==> devstack: 2016-01-11 20:12:05.495 | cp: cannot stat '/opt/stack/neutron/etc/neutron.conf': No such file or directory
==> devstack: 2016-01-11 20:12:05.495 | + exit_trap
==> devstack: 2016-01-11 20:12:05.496 | + local r=1
==> devstack: 2016-01-11 20:12:05.496 | ++ jobs -p
==> devstack: 2016-01-11 20:12:05.497 | + jobs=
==> devstack: 2016-01-11 20:12:05.497 | + [[ -n '' ]]
==> devstack: 2016-01-11 20:12:05.497 | + kill_spinner
==> devstack: 2016-01-11 20:12:05.497 | + '[' '!' -z '' ']'
==> devstack: 2016-01-11 20:12:05.497 | + [[ 1 -ne 0 ]]
==> devstack: 2016-01-11 20:12:05.497 | + echo 'Error on exit'
==> devstack: 2016-01-11 20:12:05.497 | Error on exit
==> devstack: 2016-01-11 20:12:05.497 | + [[ -z /opt/stack/logs ]]
==> devstack: 2016-01-11 20:12:05.497 | + /home/vagrant/devstack/tools/worlddump.py -d /opt/stack/logs
==> devstack: 2016-01-11 20:13:03.644 | + exit 1

If we look inside '/opt/stack/neutron/etc' there are no configuration files.

Solution:

There is a README in there that describes how to create these files. Once the specified commands in README are run, we get a bunch of .conf.sample files created. We need to change their names from '.conf.sample' to '.conf' files.
We need to include the above steps in our devstack setup script/steps.

Revision history for this message
Devdatta Kulkarni (devdatta-kulkarni) wrote :

We haven't run into this issue with the steps outlined in
https://github.com/devdattakulkarni/solum-provenance/blob/master/steps-to-enable-solum-with-devstack

Marking this bug as Invalid.

Changed in solum:
status: New → Invalid
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.