Hello,

I can confirm hosted engine itself is stopping glusterd service on the node1, 

- Is it possible to remove the pending task from DB - as I am able to halt the engine vm from failing by stopping ovirt-engine service via ssh?

- Is it possible to stop gluster service on the cluster ( without having GUI access) so that engine will not manage host gluster service?



On Tue, Dec 4, 2018 at 2:22 PM Abhishek Sahni <abhishek.sahni1991@gmail.com> wrote:
Corrections,

Hello Sahina, 

[root@node2 ~]# hosted-engine --get-shared-config mnt_options --type=he_shared


mnt_options : , type : he_shared


[root@node2 ~]# 


[root@node2 ~]# hosted-engine --set-shared-config mnt_options backup-volfile-servers=192.168.2.2:192.168.2.3  --type=he_shared

[root@node2 ~]# hosted-engine --get-shared-config mnt_options --type=he_shared

mnt_options : backup-volfile-servers=192.168.2.2:192.168.2.3, type : he_shared

I have restarted the broker and agent on node2 and try to start HE vm but still it is not starting, seems like bricks are still not getting mounted from backup-volfile-servers.

Thanks in advance,

On Tue, Dec 4, 2018 at 2:19 PM Abhishek Sahni <abhishek.sahni1991@gmail.com> wrote:
Hello Sahina, 

[root@node2 ~]# hosted-engine --get-shared-config mnt_options --type=he_shared


mnt_options : , type : he_shared


[root@node2 ~]# 


[root@node2 ~]# hosted-engine --set-shared-config mnt_options backup-volfile-servers=192.168.2.1:192.168.2.1  --type=he_shared

[root@node2 ~]# hosted-engine --get-shared-config mnt_options --type=he_shared

mnt_options : backup-volfile-servers=192.168.2.1:192.168.2.1, type : he_shared

I have restarted the broker and agent on node2 and try to start HE vm but still it is starting, seems like bricks are still not getting mounted from backup-volfile-servers.

Thanks in advance,









--

ABHISHEK SAHNI

Mob : +91-990-701-5143




--

ABHISHEK SAHNI

Mob : +91-990-701-5143