oVirt 3.4.3-1 add glusterfs volume by ovirt-engine web bug

oVirt 3.4.3-1 的glusterfs volume管理接口可能有点问题, 不能直接通过oVirt engine来添加glusterfs volume.

目前建议手工管理glusterfs volume, 然后直接在Storage中新建glusterfs 的 domain.

on 172.16.3.150 and 172.16.3.40 exec # yum install glusterfs{,-server,-fuse,-geo-replication}
on 172.16.3.150 and 172.16.3.40 exec # chkconfig glusterd on
on 172.16.3.150 and 172.16.3.40 exec # glusterd
on 172.16.3.150 and 172.16.3.40 exec # mkdir -p /data02/gfs2
on 172.16.3.150 exec # gluster peer probe 172.16.3.40

然后使用ovirt-engine管理平台添加volume.


报错 : 

错误日志如下 :

[root@176 ovirt-engine]# cd /var/log/ovirt-engine
[root@176 ovirt-engine]# less engine.log
2014-08-06 11:55:17,956 ERROR [org.ovirt.engine.core.bll.gluster.CreateGlusterVolumeCommand] (ajp--127.0.0.1-8702-6) [dfc3063] Command org.ovirt.engine.core.bll.gluster.CreateGlusterVolumeCommand throw Vdc Bll exception. With error message VdcBLLException: org.ovirt.engine.core.vdsbroker.vdsbroker.VDSNetworkException: org.apache.xmlrpc.XmlRpcException: <type 'exceptions.Exception'>:method "glusterVolumeCreate" is not supported (Failed with error VDS_NETWORK_ERROR and code 5022)
2014-08-06 11:55:17,960 INFO  [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (ajp--127.0.0.1-8702-6) [dfc3063] Correlation ID: dfc3063, Job ID: 66227433-dffd-49ed-a30b-03254eda5ca8, Call Stack: null, Custom Event ID: -1, Message: Creation of Gluster Volume gfs2 failed.
2014-08-06 11:55:17,963 INFO  [org.ovirt.engine.core.bll.gluster.CreateGlusterVolumeCommand] (ajp--127.0.0.1-8702-6) [dfc3063] Lock freed to object EngineLock [exclusiveLocks= key: 00000001-0001-0001-0001-00000000015d value: GLUSTER
, sharedLocks= ]
2014-08-06 11:55:21,967 INFO  [org.ovirt.engine.core.vdsbroker.gluster.GlusterVolumesListVDSCommand] (DefaultQuartzScheduler_Worker-47) [db14d82] START, GlusterVolumesListVDSCommand(HostName = 150, HostId = 44379bb8-e87b-4e00-a18e-5df43922da82), log id: 69aacb0a
2014-08-06 11:55:21,974 ERROR [org.ovirt.engine.core.vdsbroker.gluster.GlusterVolumesListVDSCommand] (DefaultQuartzScheduler_Worker-47) [db14d82] Command GlusterVolumesListVDSCommand(HostName = 150, HostId = 44379bb8-e87b-4e00-a18e-5df43922da82) execution failed. Exception: VDSNetworkException: org.apache.xmlrpc.XmlRpcException: <type 'exceptions.Exception'>:method "glusterVolumesList" is not supported
2014-08-06 11:55:21,975 INFO  [org.ovirt.engine.core.vdsbroker.gluster.GlusterVolumesListVDSCommand] (DefaultQuartzScheduler_Worker-47) [db14d82] FINISH, GlusterVolumesListVDSCommand, log id: 69aacb0a
2014-08-06 11:55:21,976 ERROR [org.ovirt.engine.core.bll.gluster.GlusterSyncJob] (DefaultQuartzScheduler_Worker-47) [db14d82] Error while refreshing Gluster lightweight data of cluster Default!: org.ovirt.engine.core.common.errors.VdcBLLException: VdcBLLException: org.ovirt.engine.core.vdsbroker.vdsbroker.VDSNetworkException: org.apache.xmlrpc.XmlRpcException: <type 'exceptions.Exception'>:method "glusterVolumesList" is not supported (Failed with error VDS_NETWORK_ERROR and code 5022)
        at org.ovirt.engine.core.bll.VdsHandler.handleVdsResult(VdsHandler.java:116) [bll.jar:]
        at org.ovirt.engine.core.bll.VDSBrokerFrontendImpl.RunVdsCommand(VDSBrokerFrontendImpl.java:33) [bll.jar:]
        at org.ovirt.engine.core.bll.gluster.GlusterJob.runVdsCommand(GlusterJob.java:65) [bll.jar:]
        at org.ovirt.engine.core.bll.gluster.GlusterSyncJob.fetchVolumes(GlusterSyncJob.java:406) [bll.jar:]
        at org.ovirt.engine.core.bll.gluster.GlusterSyncJob.fetchVolumes(GlusterSyncJob.java:392) [bll.jar:]
        at org.ovirt.engine.core.bll.gluster.GlusterSyncJob.refreshVolumeData(GlusterSyncJob.java:363) [bll.jar:]
        at org.ovirt.engine.core.bll.gluster.GlusterSyncJob.refreshClusterData(GlusterSyncJob.java:107) [bll.jar:]
        at org.ovirt.engine.core.bll.gluster.GlusterSyncJob.refreshLightWeightData(GlusterSyncJob.java:86) [bll.jar:]
        at sun.reflect.GeneratedMethodAccessor38.invoke(Unknown Source) [:1.7.0_65]
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) [rt.jar:1.7.0_65]
        at java.lang.reflect.Method.invoke(Method.java:606) [rt.jar:1.7.0_65]
        at org.ovirt.engine.core.utils.timer.JobWrapper.execute(JobWrapper.java:60) [scheduler.jar:]
        at org.quartz.core.JobRunShell.run(JobRunShell.java:213) [quartz.jar:]
        at org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java:557) [quartz.jar:]
时间: 2024-11-02 13:46:48

oVirt 3.4.3-1 add glusterfs volume by ovirt-engine web bug的相关文章

oVirt 3.4.3-1 cann&#039;t create disk image in GlusterFS DATA STORAGE BUG

前面刚遇到一个不能使用gluster的bug,  http://blog.163.com/digoal@126/blog/static/16387704020147623132332/ 现在又一个, 现在这个是我手工创建的glusterfs volume, 然后在ovirt的storage中新建一个domain, 使用DATA/GlusterFS挂载, 挂载成功了. 但是在后面就出问题了, 创建虚拟机时, 如果选择使用GlusterFS的domain, 新建disk image会失败. 有其他的

GlusterFS cann&#039;t active in oVirt because gluster&#039;s brick directory &amp; subd&#039;s permission problem not vdsm.kvm 755

今天在ovirt中使用glusterfs时, 发现一点问题, gfs deactive后就无法激活了, 查看日志. /var/log/ovirt-engine/engine.log 2014-08-08 08:26:09,087 ERROR [org.ovirt.engine.core.bll.storage.GLUSTERFSStorageHelper] (org.ovirt.thread.pool-6-thread-50) [d59bd20] The connection with deta

use glusterfs in oVirt

使用glusterfs前, 请先阅读 1. http://blog.163.com/digoal@126/blog/static/163877040201476115823746/ 2. http://blog.163.com/digoal@126/blog/static/16387704020147623132332/ 3. http://blog.163.com/digoal@126/blog/static/16387704020147632024869/ 4. http://wiki.ov

oVirt usage attention

汇总一下oVirt的使用注意事项. 1. 数据库相关 http://blog.163.com/digoal@126/blog/static/1638770402014628114756319/ http://blog.163.com/digoal@126/blog/static/163877040201462942137640/ 1.1 建议配置ovirt engine时, 数据库用户提前改成超级用户 1.2 建议数据库的owner是连接用户 1.3 不建议自建schema, 建议使用publi

oVirt engine 3.4 installed on CentOS 6.x x64

oVirt是RHEV的上游开源产品, 管理也和RHEV非常相似, 主打KVM的虚拟机管理平台. 相比OpenStack更加轻量化. 本文先介绍一下oVirt engine在CentOS 6.x x64平台下的安装. 除了数据库我们使用自己编译的PostgreSQL 9.3.5, 因为从依赖安装的版本实在太老了. 其他都使用依赖安装. 导入yum源 # wget http://resources.ovirt.org/pub/yum-repo/ovirt-release34.rpm # rpm -i

oVirt 3.4.3-1 LiveCD ISO based on CentOS 6.5

因为从ovirt yum安装部署ovirt, 由于engine-setup更新包后导致ovirt-engine url无法打开, 可能是更新后的BUG, 数据库日志也报了大量的函数不存在的错误.  准备试一试oVirt打包的LiveCD ISO, 可以下载3.4.2或者最新的3.4.3-1 http://resources.ovirt.org/pub/ovirt-3.4/iso/ 3.4.3-1的版本是基于CentOS 6.5封装的. 因为oVirt首页也只有3.4.2的release note

oVirt Reports Portal 3.4 added to ovirt-engine

配置完oVirt engine后, 可以进行用户管理和虚拟化平台的管理, 但是无法生成报告. 如图, 点击Reports Portal会告诉你没有安装report application. 安装ovirt engine可参考昨天发的一篇文章. http://blog.163.com/digoal@126/blog/static/1638770402014628114756319/ engine report建议在engine配置前就安装, 那么只需engine-setup时可以直接配置. 现在的

oVirt host deploy

前面介绍了oVirt engine和report的部署, 参考 :  http://blog.163.com/digoal@126/blog/static/1638770402014628114756319/ http://blog.163.com/digoal@126/blog/static/163877040201462942137640/ 这里要介绍一下使用ovirt engine管理平台进行oVirt宿主机的部署. oVirt的架构介绍参考 :  http://www.ovirt.org

获取计算机硬件信息的VB.NET代码范例

得到显示器分辨率    本文相关代码如下:Dim X As Short = System.Windows.Forms.Screen.PrimaryScreen.Bounds.WidthDim Y As Short = System.Windows.Forms.Screen.PrimaryScreen.Bounds.HeightMsgBox("您的显示器分辨率是:" & X & " X " & Y) 得到特殊文件夹的路径    本文相关代码如下