nova-manage providing filename to default_flagfile breaks devstack
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
nova (Ubuntu) |
Fix Released
|
Low
|
Scott Moser |
Bug Description
Ubuntu is carrying a patch nova-manage_
(timestamp: Tue 2010-11-23 12:17:09 +0100)
I've just noticed that if you try to run out of a source directory with that patch applied and without specifying --flagfile, that you will essentially get no flag file. This is different than the default case, where running like './bin/nova' will use './bin/nova.conf'.
Obviously the ./bin/nova.conf path is somewhat silly, but many dev scripts (devstack, nova.sh) expect that that file will be used when invoking nova.
As a result, I can't run 'devstack' right now.
ProblemType: Bug
DistroRelease: Ubuntu 11.10
Package: nova-common (not installed)
ProcVersionSign
Uname: Linux 3.0.0-12-server x86_64
ApportVersion: 1.23-0ubuntu2
Architecture: amd64
Date: Sat Oct 8 00:37:00 2011
Ec2AMI: ami-000000ac
Ec2AMIManifest: FIXME
Ec2Availability
Ec2InstanceType: m1.large
Ec2Kernel: unavailable
Ec2Ramdisk: unavailable
ProcEnviron:
PATH=(custom, user)
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: nova
UpgradeStatus: No upgrade log present (probably fresh install)
I suggest we replace the current 'nova-manage_ flagfile_ location. patch' with this one.
We should also try to get this upstream.
The change here is basically to try to use /etc/nova/nova.conf only if it exists and is readable.
While that still will break you if you're running nova-manage from a source tree as root on a system with nova installed, i find that scenario unlikely.