Yes, the brick on vm04.storage.billy correctly resolves in the hosted-engine VM to 10.30.0.4, and that IP is set in the corresponding hosts' bond1 (linked to the "gluster" network interface I created in "Networks")

2016-10-14 13:06 GMT+02:00 knarra <knarra@redhat.com>:
On 10/14/2016 04:23 PM, Davide Ferrari wrote:
Hello

I'm seeing several ot these warnings:

2016-10-14 10:49:23,721 WARN  [org.ovirt.engine.core.vdsbroker.gluster.GlusterVolumesListReturnForXmlRpc] (DefaultQuartzScheduler7) [] Could not associate brick 'vm04.storage.billy:/gluster/ssd/data/brick' of volume '23f8f1ae-a3ac-47bf-8223-5b5f7c29e508' with correct network as no gluster network found in cluster '00000002-0002-0002-0002-000000000345'

I was reading this May thread

http://lists.ovirt.org/pipermail/users/2016-May/040069.html

but there is no final answer about how to solve this warning. As the other poster, I created the gluster network before installing ovirt (it's an hosted-engine installation) and I used DNS names to point to the bricks. DNS resolution is working correctly (every host has everthing in /etc/hosts).

I also created a non-VM network and assigned it to every host's bond1 (the gluster network)

How can I fix this?

TIA

--
Davide Ferrari
Senior Systems Engineer


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

Hi David,

    you should not be seeing this error once the network with gluster role is been attached to every host in the system. Could you please check if your bricks are having the ip of what your bond1 network has ?

Thanks

kasturi.




--
Davide Ferrari
Senior Systems Engineer