On Sat, Jul 12, 2014 at 3:02 PM, Joop <jvdwege@xs4all.nl> wrote:

Just installed these packages on a test cluster and I'm having problems
migrating VMs :-(

Looking at the libvirt logs shows that there is a port conflict (49153)
when migrating. Looks like libvirt is using glusterfs ports for
migratiio and yes there is a BZ:
https://bugzilla.redhat.com/show_bug.cgi?id=1009100

This problem isn't there when using the std el6 qemu-kvm packages but I
need gluster AND migration so it seems I'm stuck until somebody 'fixes'
the build in jenkens.

Regards,

Joop

_______________________________________________
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Hi Joop,
what version of oVirt? The bug says solved in 3.5beta1, because that uses gluster 3.5.1 packages from here:
http://download.gluster.org/pub/gluster/glusterfs/LATEST/EPEL.repo/epel-6/x86_64/

There were bugs opened for both libvirt and glusterfs so that they could manage better ephemeral ports allocation if already taken by others.
They are all solved upstream, but not in CentOS 6.5 mainstream neither for libvirt (centOS) nor for gluster (epel) afaik.

As it is solved in glusterfs in 3.4.2qa4 upstream, you could try changing config file for gluster volumes as explained in this bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=987555

after you upgrade your gluster packages

You can also download packages using similar repo for 3.4.3/3.4.4

http://download.gluster.org/pub/gluster/glusterfs/3.4/3.4.3/EPEL.repo/
or
http://download.gluster.org/pub/gluster/glusterfs/3.4/3.4.4/EPEL.repo/
I successfully tried some months ago on F19 when there was similar problem.
I don't know if it would be any package conflict with current version of CentOS and/or ovirt 3.4 packages if you use them

Gianluca