devstack-failing-due-to-no-neutron-configs
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_
==> devstack: 2016-01-11 20:12:05.489 | + _create_
==> 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/
==> devstack: 2016-01-11 20:12:05.495 | cp: cannot stat '/opt/stack/
==> 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: 2016-01-11 20:13:03.644 | + exit 1
If we look inside '/opt/stack/
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.
We haven't run into this issue with the steps outlined in /github. com/devdattakul karni/solum- provenance/ blob/master/ steps-to- enable- solum-with- devstack
https:/
Marking this bug as Invalid.