When i create an instance with Flavor m1.tiny i get status Active, but when i choose Flavor m1.smal i get an error status, why ?
Malek,
You need to check the Scheduler and Compute logs to determine the exact cause. I think it might be because the available Compute host(s) does not have the necessary resources to spawn a m1.small instance.
You've missed something in your config, whether it's missing the creation of Cinder DataBase or you're config is wrong and not pointing to the right DB I can't say for sure. But the error message:
2013-04-30 12:22:38 19977 TRACE cinder ProgrammingError: (ProgrammingError) (1146, "Table 'cinder.volumes' doesn't exist")
is a bit suspect.
Hi :)
I've installed OpenStack manually with de OpenStack guide for a single node installation. Finally, i think that the problem is with cinder. I can't create a volume with cinder, it always shows an error status when i run cinder list. I'm really stuck and I can not move forward: ( Please i need help.
Here is the cinder-api.log :
2013-04-30 12:20:26 6728 AUDIT cinder.service [-] SIGTERM received
2013-04-30 12:20:26 6728 INFO cinder.wsgi [-] WSGI server has stopped.
2013-04-30 12:22:36 19850 AUDIT cinder.api.openstack.volume.extensions [-] Initializing extension manager.
2013-04-30 12:22:36 19850 DEBUG cinder.api.openstack.extensions [-] Loading extension cinder.api.openstack.volume.contrib.standardextensions loadextension /usr/lib/python2.7/dist-packages/cinder/api/openstack/extensions.py:251
2013-04-30 12:22:36 19850 DEBUG cinder.api.openstack.extensions [-] Calling extension factory cinder.api.openstack.volume.contrib.standardextensions loadextension /usr/lib/python2.7/dist-packages/cinder/api/openstack/extensions.py:257
2013-04-30 12:22:36 19850 DEBUG cinder.api.openstack.extensions [-] Loading extension cinder.api.openstack.volume.contrib.typesextraspecs.Typesextraspecs loadextension /usr/lib/python2.7/dist-packages/cinder/api/openstack/extensions.py:251
2013-04-30 12:22:36 19850 DEBUG cinder.api.openstack.extensions [-] Calling extension factory cinder.api.openstack.volume.contrib.typesextraspecs.Typesextraspecs loadextension /usr/lib/python2.7/dist-packages/cinder/api/openstack/extensions.py:257
2013-04-30 12:22:36 19850 DEBUG cinder.api.openstack.extensions [-] Ext name: TypesExtraSpecs checkextension /usr/lib/python2.7/dist-packages/cinder/api/openstack/extensions.py:230
2013-04-30 12:22:36 19850 DEBUG cinder.api.openstack.extensions [-] Ext alias: os-types-extra-specs checkextension /usr/lib/python2.7/dist-packages/cinder/api/openstack/extensions.py:231
2013-04-30 12:22:36 19850 DEBUG cinder.api.openstack.extensions [-] Ext description: Types extra specs support checkextension /usr/lib/python2.7/dist-packages/cinder/api/openstack/extensions.py:233
2013-04-30 12:22:36 19850 DEBUG cinder.api.openstack.extensions [-] Ext namespace: http://docs.openstack.org/volume/ext/types-extra-specs/api/v1 checkextension /usr/lib/python2.7/dist-packages/cinder/api/openstack/extensions.py:234
2013-04-30 12:22:36 19850 DEBUG cinder.api.openstack.extensions [-] Ext updated: 2011-08-24T00:00:00+00:00 checkextension /usr/lib/python2.7/dist-packages/cinder/api/openstack/extensions.py:235
2013-04-30 12:22:36 19850 AUDIT cinder.api.openstack.extensions [-] Loaded extension: os-types-extra-specs
2013-04-30 12:22:36 19850 DEBUG cinder.api.openstack.extensions [-] Loading extension cinder.api.openstack.volume.contrib.adminactions.Adminactions loadextension /usr/lib/python2.7/dist-packages/cinder/api/openstack/extensions.py:251
2013-04-30 12:22:36 19850 DEBUG cinder.api.openstack.extensions [-] Calling extension factory cinder.api.openstack.volume.contrib.adminactions.Adminactions loadextension /usr/lib/python2.7/dist-packages/cinder/api/openstack/extensions.py:257
2013-04-30 12:22:36 19850 DEBUG cinder.api.openstack.extensions [-] Ext name: AdminActions checkextension /usr/lib/python2.7/dist-packages/cinder/api/openstack/extensions.py:230
2013-04-30 12:22:36 19850 DEBUG cinder.api.openstack.extensions [-] Ext ...I suggest you to add a new question as the original question was answered already. Also this is not a forum: don't add a new question where there should be an answer. And finally think about using http://paste.openstack.org to paste long log messages. I'm closing this question now.
Answering to your first question:
May be your compute host doesn't have sufficient resources to provision a VM. just check your scheduler and compute logs as suggested by Umesh.
Answering to your second question :
I think their is some problem with your cinder configuration please check cinder.conf
Here I am providing the sample cinder.conf
[DEFAULT]
logdir = /var/log/cinder
state_path = /var/lib/cinder
lock_path = /var/lib/cinder/tmp
volumes_dir = /etc/cinder/volumes
iscsi_helper = tgtadm
sql_connection = postgresql://cinder:cinder@localhost/cinder
rootwrap_config = /etc/cinder/rootwrap.conf
api_paste_config = /etc/cinder/api-paste.ini
volume_name_template = volume-%s
volume_group = cinder-volumes
verbose = True
auth_strategy = keystone
iscsi_ip_address = < ip-addr >
[keystone_authtoken]
admin_tenant_name = %SERVICE_TENANT_NAME%
admin_user = %SERVICE_USER%
admin_password = %SERVICE_PASSWORD%
auth_host = 127.0.0.1
auth_port = 35357
auth_protocol = http
signing_dirname = /tmp/keystone-signing-cinder
Asked: 2013-04-24 15:58:08 -0600
Seen: 1,636 times
Last updated: Apr 30 '13