worlddump shouldn't depend on LOGDIR
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
devstack |
Fix Released
|
Medium
|
Rick Harris |
Bug Description
I saw the following when running devstack:
Requirement already up-to-date: pip in /usr/local/
Cleaning up...
+ pip_install -U setuptools
++ set +o
++ grep xtrace
+ local 'xtrace=set -o xtrace'
+ set +o xtrace
+ sudo PIP_DOWNLOAD_
Traceback (most recent call last):
File "/usr/local/
from pkg_resources import load_entry_point
File "/usr/lib/
parse_
File "/usr/lib/
raise DistributionNot
pkg_resources.
++ err_trap
++ local r=1
++ set +o xtrace
stack.sh failed
Error on exit
usage: worlddump.py [-h] [-d DIR]
worlddump.py: error: argument -d/--dir: expected one argument
Although the error is related to pip versioning, the final result shows worlddump being executed incorrectly, since in the code it depends on $LOGDIR (which I'm guessing is setup after the requirements are figured out?)
if [[ $r -ne 0 ]]; then
echo "Error on exit"
fi
Is there a way to move this check earlier? or make it not depend on $LOGDIR?
stack.sh needs a bit of a reorg re ordering things like this...logging needs to be brought up much earlier.