yahoo-eng-team team mailing list archive
-
yahoo-eng-team team
-
Mailing list archive
-
Message #02201
[Bug 1169439] Re: nova-manage unable to open database
Thanks, it was the file permissions
** Changed in: nova
Status: New => Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1169439
Title:
nova-manage unable to open database
Status in OpenStack Compute (Nova):
Invalid
Bug description:
I'm following the http://docs.openstack.org/trunk/openstack-
compute/install/apt/content/compute-verifying-install.html guide to
install nova.
"nova-manage --debug service list" gives me this error:
2013-04-16 08:30:49 DEBUG nova.utils [req-3bb016b7-0b18-4440-9248-2802391617cc None None] backend <module 'nova.db.sqlalchemy.api' from '/usr/lib/python2.7/dist-packages/nova/db/sqlalchemy/api.pyc'> __get_backend /usr/lib/python2.7/dist-packages/nova/utils.py:506
Command failed, please check log for more info
2013-04-16 08:30:49 CRITICAL nova [req-3bb016b7-0b18-4440-9248-2802391617cc None None] (OperationalError) unable to open database file None None
If I run "nova-manage config list" then the only sql_connection line is:
sql_connection = sqlite:////usr/lib/python2.7/dist-packages/nova.sqlite
even if in my /etc/nova/nova.conf I have
sql_connection=mysql://nova:f00bar@192.168.206.130/nova
It's funny that previously to "nova-manage --debug service list" I ran
"nova-manage db sync" which connected to the mysql database and filled
it up nicely.
"nova-manage version":
2012.2.2-dev (2012.2.2-LOCALBRANCH:LOCALREVISION)
My /etc/nova/nova.conf is the one from the installation guide:
[DEFAULT]
# LOGS/STATE
verbose=True
logdir=/var/log/nova
state_path=/var/lib/nova
lock_path=/var/lock/nova
rootwrap_config=/etc/nova/rootwrap.conf
# SCHEDULER
compute_scheduler_driver=nova.scheduler.filter_scheduler.FilterScheduler
# VOLUMES
volume_driver=nova.volume.driver.ISCSIDriver
volume_group=nova-volumes
volume_name_template=volume-%s
iscsi_helper=tgtadm
# DATABASE
sql_connection=mysql://nova:f00bar@192.168.206.130/nova
# COMPUTE
libvirt_type=qemu
compute_driver=libvirt.LibvirtDriver
instance_name_template=instance-%08x
api_paste_config=/etc/nova/api-paste.ini
# COMPUTE/APIS: if you have separate configs for separate services
# this flag is required for both nova-api and nova-compute
allow_resize_to_same_host=True
# APIS
osapi_compute_extension=nova.api.openstack.compute.contrib.standard_extensions
ec2_dmz_host=192.168.206.130
s3_host=192.168.206.130
# RABBITMQ
rabbit_host=192.168.206.130
# GLANCE
image_service=nova.image.glance.GlanceImageService
glance_api_servers=192.168.206.130:9292
# NETWORK
network_manager=nova.network.manager.FlatDHCPManager
force_dhcp_release=True
dhcpbridge_flagfile=/etc/nova/nova.conf
firewall_driver=nova.virt.libvirt.firewall.IptablesFirewallDriver
# Change my_ip to match each host
my_ip=192.168.206.130
public_interface=eth0
vlan_interface=eth0
flat_network_bridge=br100
flat_interface=eth0
fixed_range=''
# NOVNC CONSOLE
novncproxy_base_url=http://192.168.206.130:6080/vnc_auto.html
# Change vncserver_proxyclient_address and vncserver_listen to match each compute host
vncserver_proxyclient_address=192.168.206.130
vncserver_listen=192.168.206.130
# AUTHENTICATION
auth_strategy=keystone
To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1169439/+subscriptions