Re: [ovirt-users] Could not associate brick

2016-10-14 Thread Davide Ferrari
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 : > On 10/14/2016 04:23 PM, Davide Ferrari wrote

Re: [ovirt-users] Could not associate brick

2016-10-14 Thread knarra
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/bric

[ovirt-users] Could not associate brick

2016-10-14 Thread Davide Ferrari
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'