Hi All,
Thanks to the list help I'm now able to add hosts to my setup of
ovirt-3.2-nightlies on Fed17. Procedure in short:
install Fed17 from bfo.iso, so that I have minimal install, fix
networking-scripts, add danken virt repo en ovirt repo, yum update and
to minimize host add time yum install vdsm.
Sofar this has worked very well for 3 hosts. Now I would like to move 2
of those hosts to a Gluster enabled cluster. Putting them in maintanance
and then move them to the gluster cluster works for 1 of them and the
next gives an error. So remove the host and re-add it to the Gluster
cluster. Works OK, installs glusterfs and vdsm-gluster packages. Reboot
and detecting by mgmt works OK too.
Next step is on both hosts:
mkdir /gluster-data
chown -R 36:36 /gluster-data
gluster peer status --> no peers.
And then through the webadmin add a volume named gluster-data with paths
to st01:/gluster-data and st02:/gluster-data in replication mode, click
add --> Error
gluster peer status on both st01/2 shows the other server as connected,
gluster volume list --> gluster-data and gluster volume info gives more
info about the just entered info in the webadmin but I can't get an OK
there, cancelling the volume add gives me no volume in the webinterface.
Error in the vdsm.log on the storage hosts is:
MainProcess|Thread-153::DEBUG::2012-12-27
22:30:51,882::misc::84::Storage.Misc.excCmd::(<lambda>)
'/usr/sbin/gluster --mode=script volume info --xml' (cwd None)
MainProcess|Thread-153::DEBUG::2012-12-27
22:30:51,955::misc::84::Storage.Misc.excCmd::(<lambda>) SUCCESS: <err> =
''; <rc> = 0
MainProcess|Thread-153::ERROR::2012-12-27
22:30:51,956::supervdsmServer::80::SuperVdsm.ServerCallback::(wrapper)
Error in wrapper
Traceback (most recent call last):
File "/usr/share/vdsm/supervdsmServer.py", line 78, in wrapper
return func(*args, **kwargs)
File "/usr/share/vdsm/supervdsmServer.py", line 313, in wrapper
return func(*args, **kwargs)
File "/usr/share/vdsm/gluster/cli.py", line 45, in wrapper
return func(*args, **kwargs)
File "/usr/share/vdsm/gluster/cli.py", line 431, in volumeInfo
raise ge.GlusterXmlErrorException(err=[etree.tostring(xmltree)])
GlusterXmlErrorException: XML error
error: <cliOutput><opRet>0</opRet><opErrno>0</opErrno><opErrstr
/><volInfo><volumes><volume><name>gluster-data</name><id>aafc9a0b-1b17-4e1f-b441-7f9dfdb874db</id><type>2</type><status>0</status><brickCount>2</brickCount><distCount>2</distCount><stripeCount>1</stripeCount><replicaCount>2</replicaCount><transport>0</transport><bricks><brick>st01.nieuwland.nl:/gluster-data</brick><brick>st02.nieuwland.nl:/gluster-data</brick></bricks><optCount>0</optCount><options
/></volume><count>1</count></volumes></volInfo></cliOutput>
Thread-153::ERROR::2012-12-27
22:30:51,969::BindingXMLRPC::925::vds::(wrapper) vdsm exception occured
Traceback (most recent call last):
File "/usr/share/vdsm/BindingXMLRPC.py", line 914, in wrapper
res = f(*args, **kwargs)
File "/usr/share/vdsm/gluster/api.py", line 32, in wrapper
rv = func(*args, **kwargs)
File "/usr/share/vdsm/gluster/api.py", line 56, in volumesList
return {'volumes': self.svdsmProxy.glusterVolumeInfo(volumeName)}
File "/usr/share/vdsm/supervdsm.py", line 77, in __call__
return callMethod()
File "/usr/share/vdsm/supervdsm.py", line 68, in <lambda>
**kwargs)
File "<string>", line 2, in glusterVolumeInfo
File "/usr/lib64/python2.7/multiprocessing/managers.py", line 773, in
_callmethod
raise convert_to_error(kind, result)
GlusterXmlErrorException: XML error
error: <cliOutput><opRet>0</opRet><opErrno>0</opErrno><opErrstr
/><volInfo><volumes><volume><name>gluster-data</name><id>aafc9a0b-1b17-4e1f-b441-7f9dfdb874db</id><type>2</type><status>0</status><brickCount>2</brickCount><distCount>2</distCount><stripeCount>1</stripeCount><replicaCount>2</replicaCount><transport>0</transport><bricks><brick>st01.nieuwland.nl:/gluster-data</brick><brick>st02.nieuwland.nl:/gluster-data</brick></bricks><optCount>0</optCount><options
/></volume><count>1</count></volumes></volInfo></cliOutput>
versions:
rpm -aq | grep vdsm
vdsm-4.10.3-0.50.gitc6625ce.fc17.x86_64
vdsm-gluster-4.10.3-0.50.gitc6625ce.fc17.noarch
vdsm-xmlrpc-4.10.3-0.50.gitc6625ce.fc17.noarch
vdsm-cli-4.10.3-0.50.gitc6625ce.fc17.noarch
vdsm-python-4.10.3-0.50.gitc6625ce.fc17.x86_64
# rpm -aq | grep libvirt
libvirt-daemon-driver-qemu-0.10.1-2.fc17.x86_64
libvirt-daemon-driver-interface-0.10.1-2.fc17.x86_64
libvirt-daemon-driver-nwfilter-0.10.1-2.fc17.x86_64
libvirt-daemon-driver-libxl-0.10.1-2.fc17.x86_64
libvirt-client-0.10.1-2.fc17.x86_64
libvirt-daemon-driver-network-0.10.1-2.fc17.x86_64
libvirt-daemon-driver-lxc-0.10.1-2.fc17.x86_64
libvirt-lock-sanlock-0.10.1-2.fc17.x86_64
libvirt-daemon-driver-secret-0.10.1-2.fc17.x86_64
libvirt-daemon-driver-nodedev-0.10.1-2.fc17.x86_64
libvirt-daemon-config-network-0.10.1-2.fc17.x86_64
libvirt-daemon-driver-storage-0.10.1-2.fc17.x86_64
libvirt-0.10.1-2.fc17.x86_64
libvirt-python-0.10.1-2.fc17.x86_64
libvirt-daemon-0.10.1-2.fc17.x86_64
libvirt-daemon-driver-xen-0.10.1-2.fc17.x86_64
libvirt-daemon-config-nwfilter-0.10.1-2.fc17.x86_64
libvirt-daemon-driver-uml-0.10.1-2.fc17.x86_64
qemu-img-1.2.0-25.fc17.x86_64
qemu-common-1.2.0-25.fc17.x86_64
qemu-kvm-1.2.0-25.fc17.x86_64
qemu-kvm-tools-1.2.0-25.fc17.x86_64
ipxe-roms-qemu-20120328-1.gitaac9718.fc17.noarch
qemu-system-x86-1.2.0-25.fc17.x86_64
Other logs are available but don't know whether they are needed. Didn't
see anything obvious in the gluster logs. The commands for the gluster
volume creating are done on st01 according to .cmd_log_history.
Joop
_______________________________________________
Users mailing list
[email protected]
http://lists.ovirt.org/mailman/listinfo/users
