Public bug reported: Ubuntu is carrying a patch nova-manage_flagfile_location.patch, for quite some time. (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) ProcVersionSignature: User Name 3.0.0-12.19-server 3.0.4 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 Ec2AvailabilityZone: nova 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) ** Affects: nova (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug ec2-images oneiric -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nova in Ubuntu. https://bugs.launchpad.net/bugs/870405 Title: nova-manage providing filename to default_flagfile breaks devstack To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nova/+bug/870405/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs