云学生 发表于 2016-4-15 20:32:12

求助!openstack kilo版本,cinder-volume没有启动

   检验cinder安装时,键入cinder service-list之后,只显示了cinder-scheduler服务,没有显示cinder-volume服务,于是查了一下block节点的日志,如下:
    2016-04-15 05:25:47.228 108769 INFO cinder.volume.manager Starting volume driver LVMVolumeDriver (2.0.0)
root@block1:/var/log/cinder# tail -20 cinder-volume.log
2016-04-15 05:26:29.916 109409 TRACE cinder.openstack.common.threadgroup   File "/usr/lib/python2.7/dist-packages/sqlalchemy/engine/base.py", line 874, in _execute_context
2016-04-15 05:26:29.916 109409 TRACE cinder.openstack.common.threadgroup   context)
2016-04-15 05:26:29.916 109409 TRACE cinder.openstack.common.threadgroup   File "/usr/lib/python2.7/dist-packages/sqlalchemy/engine/base.py", line 1024, in _handle_dbapi_exception
2016-04-15 05:26:29.916 109409 TRACE cinder.openstack.common.threadgroup   exc_info
2016-04-15 05:26:29.916 109409 TRACE cinder.openstack.common.threadgroup   File "/usr/lib/python2.7/dist-packages/sqlalchemy/util/compat.py", line 196, in raise_from_cause
2016-04-15 05:26:29.916 109409 TRACE cinder.openstack.common.threadgroup   reraise(type(exception), exception, tb=exc_tb)
2016-04-15 05:26:29.916 109409 TRACE cinder.openstack.common.threadgroup   File "/usr/lib/python2.7/dist-packages/sqlalchemy/engine/base.py", line 867, in _execute_context
2016-04-15 05:26:29.916 109409 TRACE cinder.openstack.common.threadgroup   context)
2016-04-15 05:26:29.916 109409 TRACE cinder.openstack.common.threadgroup   File "/usr/lib/python2.7/dist-packages/sqlalchemy/engine/default.py", line 324, in do_execute
2016-04-15 05:26:29.916 109409 TRACE cinder.openstack.common.threadgroup   cursor.execute(statement, parameters)
2016-04-15 05:26:29.916 109409 TRACE cinder.openstack.common.threadgroup   File "/usr/lib/python2.7/dist-packages/MySQLdb/cursors.py", line 174, in execute
2016-04-15 05:26:29.916 109409 TRACE cinder.openstack.common.threadgroup   self.errorhandler(self, exc, value)
2016-04-15 05:26:29.916 109409 TRACE cinder.openstack.common.threadgroup   File "/usr/lib/python2.7/dist-packages/MySQLdb/connections.py", line 36, in defaulterrorhandler
2016-04-15 05:26:29.916 109409 TRACE cinder.openstack.common.threadgroup   raise errorclass, errorvalue
2016-04-15 05:26:29.916 109409 TRACE cinder.openstack.common.threadgroup OperationalError: (OperationalError) (1054, "Unknown column 'volumes.instance_uuid' in 'field list'") 'SELECT volumes.created_at AS volumes_created_at, volumes.updated_at AS volumes_updated_at, volumes.deleted_at AS volumes_deleted_at, volumes.id AS volumes_id, volumes._name_id AS volumes__name_id, volumes.ec2_id AS volumes_ec2_id, volumes.user_id AS volumes_user_id, volumes.project_id AS volumes_project_id, volumes.snapshot_id AS volumes_snapshot_id, volumes.host AS volumes_host, volumes.size AS volumes_size, volumes.availability_zone AS volumes_availability_zone, volumes.instance_uuid AS volumes_instance_uuid, volumes.attached_host AS volumes_attached_host, volumes.mountpoint AS volumes_mountpoint, volumes.attach_time AS volumes_attach_time, volumes.status AS volumes_status, volumes.attach_status AS volumes_attach_status, volumes.migration_status AS volumes_migration_status, volumes.scheduled_at AS volumes_scheduled_at, volumes.launched_at AS volumes_launched_at, volumes.terminated_at AS volumes_terminated_at, volumes.display_name AS volumes_display_name, volumes.display_description AS volumes_display_description, volumes.provider_location AS volumes_provider_location, volumes.provider_auth AS volumes_provider_auth, volumes.provider_geometry AS volumes_provider_geometry, volumes.volume_type_id AS volumes_volume_type_id, volumes.source_volid AS volumes_source_volid, volumes.encryption_key_id AS volumes_encryption_key_id, volumes.deleted AS volumes_deleted, volumes.bootable AS volumes_bootable, volume_types_1.created_at AS volume_types_1_created_at, volume_types_1.updated_at AS volume_types_1_updated_at, volume_types_1.deleted_at AS volume_types_1_deleted_at, volume_types_1.deleted AS volume_types_1_deleted, volume_types_1.id AS volume_types_1_id, volume_types_1.name AS volume_types_1_name, volume_types_1.qos_specs_id AS volume_types_1_qos_specs_id, volume_metadata_1.created_at AS volume_metadata_1_created_at, volume_metadata_1.updated_at AS volume_metadata_1_updated_at, volume_metadata_1.deleted_at AS volume_metadata_1_deleted_at, volume_metadata_1.deleted AS volume_metadata_1_deleted, volume_metadata_1.id AS volume_metadata_1_id, volume_metadata_1.`key` AS volume_metadata_1_key, volume_metadata_1.value AS volume_metadata_1_value, volume_metadata_1.volume_id AS volume_metadata_1_volume_id, volume_admin_metadata_1.created_at AS volume_admin_metadata_1_created_at, volume_admin_metadata_1.updated_at AS volume_admin_metadata_1_updated_at, volume_admin_metadata_1.deleted_at AS volume_admin_metadata_1_deleted_at, volume_admin_metadata_1.deleted AS volume_admin_metadata_1_deleted, volume_admin_metadata_1.id AS volume_admin_metadata_1_id, volume_admin_metadata_1.`key` AS volume_admin_metadata_1_key, volume_admin_metadata_1.value AS volume_admin_metadata_1_value, volume_admin_metadata_1.volume_id AS volume_admin_metadata_1_volume_id \nFROM volumes LEFT OUTER JOIN volume_types AS volume_types_1 ON volumes.volume_type_id = volume_types_1.id AND volume_types_1.deleted = false LEFT OUTER JOIN volume_metadata AS volume_metadata_1 ON volume_metadata_1.volume_id = volumes.id AND volume_metadata_1.deleted = false LEFT OUTER JOIN volume_admin_metadata AS volume_admin_metadata_1 ON volume_admin_metadata_1.volume_id = volumes.id AND volume_admin_metadata_1.deleted = false \nWHERE volumes.deleted = false AND volumes.host = %s' ('block1@lvm',)

    请问有没有过来人遇到过类似的问题呀~~小弟新手,希望大家指导一下~~

xuanxufeng 发表于 2016-4-15 20:49:14

楼主数据库没有同步成功
Unknown column 'volumes.instance_uuid' in 'field list'

云学生 发表于 2016-4-15 20:51:58

xuanxufeng 发表于 2016-4-15 20:49
楼主数据库没有同步成功
Unknown column 'volumes.instance_uuid' in 'field list'

    数据库没有同步成功是指在块存储节点上吗?还是说在控制节点上?
    如果是指控制节点的话,我已经把cinder的数据库以及其他的有关cinder的表和记录删除并重新创建过了,但如果是指在块存储节点上的话,希望可以详细一点说一下,因为我看的教程没有说过需要在块存储节点上同步数据库

xuanxufeng 发表于 2016-4-15 20:54:53

云学生 发表于 2016-4-15 20:51
数据库没有同步成功是指在块存储节点上吗?还是说在控制节点上?
    如果是指控制节点的话,我已经 ...

都有的,去看看官方文档
这是Juno版的

openstack【juno】入门 【cinder篇】二十:cinder介绍及安装配置【控制节点】
http://www.aboutyun.com/forum.php?mod=viewthread&tid=11653



你找到对应kilo版即可

云学生 发表于 2016-4-15 20:59:07

xuanxufeng 发表于 2016-4-15 20:54
都有的,去看看官方文档
这是Juno版的



    这个主题帖我也有看过,不过他只写了在控制节点上同步数据库,没有涉及块存储节点上的同步操作。不知道你有没有其他的文档或者资料可以参考一下,我刚接触这个东西,希望你可以指导一下

bob007 发表于 2016-4-15 22:18:41

云学生 发表于 2016-4-15 20:59
这个主题帖我也有看过,不过他只写了在控制节点上同步数据库,没有涉及块存储节点上的同步操作。不知 ...

存储节点没有数据库。
但是他们之间是通信的,控制节点没有同步成功,造成的报上面错误。
建议多从原理角度去理解

云学生 发表于 2016-4-15 22:23:31

bob007 发表于 2016-4-15 22:18
存储节点没有数据库。
但是他们之间是通信的,控制节点没有同步成功,造成的报上面错误。
建议多从原理 ...

   我已经重新创建数据库同步数据库好多次了,块存储节点上的配置也检查过了,可是cinder-volume还是没有启动。就我现在的知识储备只能通过/var/log/cinder/cinder.log去看有可能出错的地方。可错误已经贴出来了,现在不知道该怎么调试了,请指导一下

Alkaloid0515 发表于 2016-4-16 07:22:59

云学生 发表于 2016-4-15 22:23
我已经重新创建数据库同步数据库好多次了,块存储节点上的配置也检查过了,可是cinder-volume还是没有 ...

把同步界面贴出来,或则去日志看看,同步成功了吗

云学生 发表于 2016-4-16 10:33:57

Alkaloid0515 发表于 2016-4-16 07:22
把同步界面贴出来,或则去日志看看,同步成功了吗

   同步信息检查过了,应该是同步成功了

lz19851224 发表于 2016-5-23 12:06:24

看看时间有没有同步,我装的K版的按照官方文档装基本上不会有错,有错也就是看看时间同步没有
页: [1] 2
查看完整版本: 求助!openstack kilo版本,cinder-volume没有启动