<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On Mon, Apr 11, 2016 at 9:37 AM, Richard Neuboeck <span dir="ltr"><<a href="mailto:hawk@tbi.univie.ac.at" target="_blank">hawk@tbi.univie.ac.at</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi Darryl,<br>
<br>
I'm still experimenting with my oVirt installation so I tried to<br>
recreate the problems you've described.<br>
<br>
My setup has three HA hosts for virtualization and three machines<br>
for the gluster replica 3 setup.<br>
<br>
I manually migrated the Engine from the initial install host (one)<br>
to host three. Then shut down host one manually and interrupted the<br>
fencing mechanisms so the host stayed down. This didn't bother the<br>
Engine VM at all.<br></blockquote><div><br></div><div>Did you move the host one to maintenance before shutting down?</div><div>Or is this a crash recovery test?</div><div><br></div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
To make things a bit more challenging I then shut down host three<br>
while running the Engine VM. Of course the Engine was down for some<br>
time until host two detected the problem. It started the Engine VM<br>
and everything seems to be running quite well without the initial<br>
install host.<br></blockquote><div><br></div><div>Thanks for the feedback!</div><div><br></div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
My only problem is that the HA agent on host two and three refuse to<br>
start after a reboot due to the fact that the configuration of the<br>
hosted engine is missing. I wrote another mail to <a href="mailto:users@ovirt.org">users@ovirt.org</a><br>
about that.<br></blockquote><div><br></div><div>This is weird. Martin, Simone can you please investigate on this?</div><div><br></div><div><br></div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
Cheers<br>
Richard<br>
<div class="HOEnZb"><div class="h5"><br>
On 04/08/2016 01:38 AM, Bond, Darryl wrote:<br>
> There seems to be a pretty severe bug with using hosted engine on gluster.<br>
><br>
> If the host that was used as the initial hosted-engine --deploy host goes away, the engine VM wil crash and cannot be restarted until the host comes back.<br></div></div></blockquote><div><br></div><div>is this an Hyperconverged setup?</div><div><br></div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="HOEnZb"><div class="h5">
><br>
> This is regardless of which host the engine was currently running.<br>
><br>
><br>
> The issue seems to be buried in the bowels of VDSM and is not an issue with gluster itself.<br></div></div></blockquote><div><br></div><div>Sahina, can you please investigate on this?</div><div><br></div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="HOEnZb"><div class="h5">
><br>
> The gluster filesystem is still accessable from the host that was running the engine. The issue has been submitted to bugzilla but the fix is some way off (4.1).<br>
><br>
><br>
> Can my hosted engine be converted to use NFS (using the gluster NFS server on the same filesystem) without rebuilding my hosted engine (ie change domainType=glusterfs to domainType=nfs)?</div></div></blockquote><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="HOEnZb"><div class="h5"><span style="color:rgb(34,34,34)"> </span></div></div></blockquote><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="HOEnZb"><div class="h5">
><br>
> What effect would that have on the hosted-engine storage domain inside oVirt, ie would the same filesystem be mounted twice or would it just break.<br>
><br>
><br>
> Will this actually fix the problem, does it have the same issue when the hosted engine is on NFS?<br>
><br>
><br>
> Darryl<br>
><br>
><br>
><br>
><br>
> ________________________________<br>
><br>
> The contents of this electronic message and any attachments are intended only for the addressee and may contain legally privileged, personal, sensitive or confidential information. If you are not the intended addressee, and have received this email, any transmission, distribution, downloading, printing or photocopying of the contents of this message or attachments is strictly prohibited. Any legal privilege or confidentiality attached to this message and attachments is not waived, lost or destroyed by reason of delivery to any person other than intended addressee. If you have received this message and are not the intended addressee you should notify the sender by return email and destroy all copies of the message and any attachments. Unless expressly attributed, the views expressed in this email do not necessarily represent the views of the company.<br>
> _______________________________________________<br>
> Users mailing list<br>
> <a href="mailto:Users@ovirt.org">Users@ovirt.org</a><br>
> <a href="http://lists.ovirt.org/mailman/listinfo/users" rel="noreferrer" target="_blank">http://lists.ovirt.org/mailman/listinfo/users</a><br>
><br>
<br>
<br>
</div></div><span class="HOEnZb"><font color="#888888">--<br>
/dev/null<br>
<br>
</font></span><br>_______________________________________________<br>
Users mailing list<br>
<a href="mailto:Users@ovirt.org">Users@ovirt.org</a><br>
<a href="http://lists.ovirt.org/mailman/listinfo/users" rel="noreferrer" target="_blank">http://lists.ovirt.org/mailman/listinfo/users</a><br>
<br></blockquote></div><br><br clear="all"><div><br></div>-- <br><div class="gmail_signature"><div dir="ltr"><div><div dir="ltr">Sandro Bonazzola<br>Better technology. Faster innovation. Powered by community collaboration.<br>See how it works at <a href="http://redhat.com" target="_blank">redhat.com</a><br></div></div></div></div>
</div></div>