command for running stack.sh is wrong while installing tacker from master branch
Bug #1598694 reported by
Ashi Kansal
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| tacker |
Fix Released
|
Low
|
Ashi Kansal | ||
Bug Description
At the following link:
http://
At section: Install via Devstack
-> Install from master
step 3:
Run stack.sh:
$ stack.sh
is incorrect
Following error found:
stack.sh: command not found
| Changed in openstack-manuals: | |
| assignee: | nobody → Ashi Kansal (ashi-kansal) |
| status: | New → In Progress |
| Changed in openstack-manuals: | |
| importance: | Undecided → Low |
| affects: | openstack-manuals → tacker |
| Changed in tacker: | |
| milestone: | none → newton-2 |
| Changed in tacker: | |
| status: | In Progress → Fix Committed |
| Changed in tacker: | |
| status: | Fix Committed → In Progress |
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Fix merged to tacker (master) | #1 |
| Changed in tacker: | |
| status: | In Progress → Fix Released |
Revision history for this message
| Doug Hellmann (doug-hellmann) wrote Fix included in openstack/tacker 0.4.0 | #2 |
To post a comment you must log in.
Reviewed: https:/
Committed: https:/
Submitter: Jenkins
Branch: master
commit 63bd600aa7a16e0
Author: ashi kansal <email address hidden>
Date: Mon Jul 4 11:37:43 2016 +0530
Corrected execution step for devstack
Execution of devstack script may not start on some
machines because some of the machine may not have
current directory in PATH variables. Correction
has been made to start the script independent of
the environment.
Change-Id: Ib7f9b691a9567f
Closes-Bug: #1598694