[ovirt-users] oVirt 4.1.5 Finally GlusterFS via lbgfapi

[Denis Chaplygin]

Hello!

On Fri, Aug 25, 2017 at 11:05 AM, Ralf Schenk <rs at databay.de> wrote:

>
> I replayed migration (10:38:02 local time) and recorded vdsm.log of source
> and destination as attached. I can't find anything in the gluster logs that
> shows an error. One information: my FQDN glusterfs.rxmgmt.databay.de
> points to all the gluster hosts:
>
> glusterfs.rxmgmt.databay.de. 84600 IN   A       172.16.252.121
> glusterfs.rxmgmt.databay.de. 84600 IN   A       172.16.252.125
> glusterfs.rxmgmt.databay.de. 84600 IN   A       172.16.252.127
> glusterfs.rxmgmt.databay.de. 84600 IN   A       172.16.252.122
> glusterfs.rxmgmt.databay.de. 84600 IN   A       172.16.252.124
> glusterfs.rxmgmt.databay.de. 84600 IN   A       172.16.252.123
> glusterfs.rxmgmt.databay.de. 84600 IN   A       172.16.252.126
> glusterfs.rxmgmt.databay.de. 84600 IN   A       172.16.252.128
>
> I double checked all gluster hosts. They all are configured the same
> regarding "option rpc-auth-allow-insecure on" No iptables rules on the
> host.
>

Do you use 'glusterfs.rxmgmt.databay.de" as a storage domain host name? I'm
not a gluster guru, but i'm afraid that some internal gluster client code
may go crazy, when it receives different address or several ip addresses
every time. Is it possible to try with separate names? You can create a
storage domain using 172.16.252.121 for example and it should work
bypassing your DNS. If it is possible to make that, could you please do
that and retry live migration?
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ovirt.org/pipermail/users/attachments/20170825/a37e4a1d/attachment.html>