1:06 a.m.
On Mon, Mar 27, 2017 at 7:35 PM, Davide Ferrari <davide(a)billymob.com> wrote:
Sorry for hijacking the thread but, in my case, I have a separate
VLAN for
gluster intercommunication and that VLAN is not accessible from the hosted
engine. Maybe that's the problem?
Yep - that's likely to be it, if you have identified the brick using an
FQDN instead of ip address.
2017-03-27 12:14 GMT+02:00 Sahina Bose <sabose(a)redhat.com>:
>
>
> On Mon, Mar 27, 2017 at 2:06 PM, Davide Ferrari <davide(a)billymob.com>
> wrote:
>
>> I have the same error (warning) and in my case the answer is yes to both
>> questions.
>>
>
> Which IP address does "spfy-hw01" resolve to from engine.
> Is it the same IP address that you see in Networks sub-tab under hosts-
> for network associated with "gluster"
>
> The engine tries to associate the brick info returned from gluster CLI
> using the following logic:
> i) check if the ip/hostname in <server-ip>:<brick-directory> matches
that
> of host
> ii) check the IP address that hostname in brick resolves to - and match
> it against any of the interface associated with host that has gluster
> network tagged to it
>
>
>
>> 2017-03-27 10:12 GMT+02:00 Sahina Bose <sabose(a)redhat.com>:
>>
>>> Is "spfy-hw01" resolvable from engine? Have you associated network
>>> named "gluster" to interface associated with "spfy-hw01"
under "Setup
>>> Host Network" of host?
>>>
>>> On Sat, Mar 25, 2017 at 5:56 PM, Arsène Gschwind <
>>> arsene.gschwind(a)unibas.ch> wrote:
>>>
>>>> Hi,
>>>>
>>>> I do have a recuring warning in engine.log and i'm not able to
figure
>>>> out what is wrong in my setup.
>>>>
>>>> 2017-03-25 10:13:12,391+01 WARN [org.ovirt.engine.core.vdsbrok
>>>> er.gluster.GlusterVolumesListReturn] (DefaultQuartzScheduler4)
>>>> [e02bacbc-75ab-4c48-81c0-e3d64e4bd3e9] Could not associate brick
>>>> 'spfy-hw01:/gluster/engine/brick' of volume
>>>> 'af169181-d72e-4325-9947-d7dd09e512f0' with correct network as
no
>>>> gluster network found in cluster '00000002-0002-0002-0002-00000
>>>> 00002a6'
>>>> 2017-03-25 10:13:12,394+01 WARN [org.ovirt.engine.core.vdsbrok
>>>> er.gluster.GlusterVolumesListReturn] (DefaultQuartzScheduler4)
>>>> [e02bacbc-75ab-4c48-81c0-e3d64e4bd3e9] Could not associate brick
>>>> 'spfy-hw02:/gluster/engine/brick' of volume
>>>> 'af169181-d72e-4325-9947-d7dd09e512f0' with correct network as
no
>>>> gluster network found in cluster '00000002-0002-0002-0002-00000
>>>> 00002a6'
>>>> 2017-03-25 10:13:12,397+01 WARN [org.ovirt.engine.core.vdsbrok
>>>> er.gluster.GlusterVolumesListReturn] (DefaultQuartzScheduler4)
>>>> [e02bacbc-75ab-4c48-81c0-e3d64e4bd3e9] Could not associate brick
>>>> 'spfy-hw03:/gluster/engine/brick' of volume
>>>> 'af169181-d72e-4325-9947-d7dd09e512f0' with correct network as
no
>>>> gluster network found in cluster '00000002-0002-0002-0002-00000
>>>> 00002a6'
>>>>
>>>> My setup:
>>>>
>>>> - oVirt 4.1.0
>>>> - gluster 3.8.10-1.el7
>>>>
>>>> I've setup a gluster network and dedicated to gluster:
>>>>
>>>> [image: gluster]
>>>>
>>>> Could someone explain why I do have this warning and how to resolve
>>>> the problem .
>>>>
>>>> Thanks a lot
>>>>
>>>> rgds,
>>>>
>>>> Arsène
>>>> --
>>>>
>>>>
>>>> _______________________________________________
>>>> Users mailing list
>>>> Users(a)ovirt.org
>>>> http://lists.ovirt.org/mailman/listinfo/users
>>>>
>>>>
>>>
>>> _______________________________________________
>>> Users mailing list
>>> Users(a)ovirt.org
>>> http://lists.ovirt.org/mailman/listinfo/users
>>>
>>>
>>
>>
>> --
>> Davide Ferrari
>> Senior Systems Engineer
>>
>
>
--
Davide Ferrari
Senior Systems Engineer
