Multi-Node Lab in DevStack incorrect nova-manage path

Bug #1783576 reported by Mario Kostadincev
This bug affects 2 people
Affects Status Importance Assigned to Milestone

Bug Description

This bug tracker is for errors with the documentation, use the following as a template and remove or add fields as you see fit. Convert [ ] into [x] to check boxes:

- [ ] This doc is inaccurate in this way: ______
- [ ] This is a doc addition request.
- [x] I have a fix to the document that I can paste below including example: input and output.
current: for i in `seq 2 10`; do /opt/stack/nova/bin/nova-manage fixed reserve 10.4.128.$i; done
should be: for i in `seq 2 10`; do /usr/local/bin/nova-manage fixed reserve 10.4.128.$i; done

If you have a troubleshooting or support issue, use the following resources:

 - Ask OpenStack:
 - The mailing list:
 - IRC: 'openstack' channel on Freenode

Release: on 2018-07-12 11:39
SHA: 3b5477d6356a62d7d64a519a4b1ac99309d251c0

Revision history for this message
Dr. Jens Harbott (j-harbott) wrote :

Actually this command only made sense when running nova-network instead of Neutron, which isn't an option anymore. I'll do a test-run of the complete lab before putting up a patch.

Changed in devstack:
status: New → Triaged
importance: Undecided → Medium
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.