nova-manage couldnot work normally in devstack

You have to point it at the proper flagfile, which means: nova-manage
--flagfile=/opt/stack/nova/bin/nova.conf service list. We should probably
modify devstack to put the conf in /etc/nova/nova.conf so this isn't
necessary.
On Nov 13, 2011 6:45 AM, "Alan LQC" <email address hidden>
wrote:

> New question #178615 on OpenStack Compute (nova):
> https://answers.launchpad.net/nova/+question/178615
>
> I haved successfully installed the devstack by running the script
> stack.sh, which was downloaded at http://devstack.org/
> And I can access openstack endpoints (Horizon and Keystone), which means
> working correctly as the README.md said.
>
> Now when I enter the command "nova-manage service list", it returns the
> error just as follows:
>
> stack@monster:~/devstack$ nova-manage service list
> Command failed, please check log for more info
> 2011-11-13 22:39:58,873 CRITICAL nova [-] (OperationalError) no such
> table: services u'SELECT services.created_at AS services_created_at,
> services.updated_at AS services_updated_at, services.deleted_at AS
> services_deleted_at, services.deleted AS services_deleted, services.id AS
> services_id, services.host AS services_host, services.binary AS
> services_binary, services.topic AS services_topic, services.report_count AS
> services_report_count, services.disabled AS services_disabled,
> services.availability_zone AS services_availability_zone \nFROM services
> \nWHERE services.deleted = ?' (False,)
>
> At first, I wanted to check the log so that I could solve the problem by
> myself. However, I couldnot find the log anywhere.
> Could anyone show me the way to solve that problem, and I am hoping for
> your reply soon. Thank you with the best wishes!
>
> --
> You received this question notification because you are a member of Nova
> Core, which is an answer contact for OpenStack Compute (nova).
>