Manually Adding Magnum to Devstack fails on copying magnum.conf.sample

Bug #1604560 reported by Stephen Watson
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Magnum
Invalid
Undecided
Stephen Watson

Bug Description

See document here: http://docs.openstack.org/developer/magnum/dev/dev-manual-devstack.html

This setup guide runs into failures during the "Configure Magnum" section when trying to run
# copy sample config and modify it as necessary
sudo cp etc/magnum/magnum.conf.sample /etc/magnum/magnum.conf

The failure is due to ~/magnum/etc/magnum/magnum.conf.sample not existing until "tox -edocs" or "tox -egenconfig" is run in the magnum base directory first. I verified that both commands generate the sample file and fix the problem, and configuring via the text as-is after running tox continues just fine.

Revision history for this message
Stephen Watson (stephen-watson) wrote :

Spoke with Murali on IRC and the bug fix should also mention installing dependencies (in my case pip was required and not yet installed)

Changed in magnum:
assignee: nobody → Stephen Watson (stephen-watson)
Revision history for this message
Stephen Watson (stephen-watson) wrote :

Realized I was on mitaka branch from a previous setting. Disregard this filing

Changed in magnum:
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.