Re: [ovirt-users] Unable to reactivate host after reboot due to failed Gluster probe

On 01/29/2015 04:26 PM, Jan Siml wrote: Hello, finally I got the nodes online. What helps was probing the not needed peer node-04 (no brick) from one of the other cluster nodes. When the node becames a Gluster peer, I am able to activate any oVirt node which serves bricks. Therefore I assum

Re: [ovirt-users] Unable to reactivate host after reboot due to failed Gluster probe

Hello, finally I got the nodes online. What helps was probing the not needed peer node-04 (no brick) from one of the other cluster nodes. When the node becames a Gluster peer, I am able to activate any oVirt node which serves bricks. Therefore I assume, the error message which the UI returns

Re: [ovirt-users] Unable to reactivate host after reboot due to failed Gluster probe

Hello, when looking into engine.log, I can see, that "gluster probe" returned errno 107. But I can't figure out why: 2015-01-29 10:40:03,546 ERROR [org.ovirt.engine.core.bll.InitVdsOnUpCommand] (DefaultQuartzScheduler_Worker-59) [5977aac5] Could not peer probe the gluster server node-03. Er

[ovirt-users] Unable to reactivate host after reboot due to failed Gluster probe

Hello, we have a strange behavior within an oVirt cluster. Version is 3.5.1, engine is running on EL6 machine and hosts are using EL7 as operating system. The cluster uses a GlusterFS backed storage domain amongst others. Three of four hosts are peers in the Gluster cluster (3 bricks, 3 repli