<p dir="ltr">I see I have a very unfortunate typo in my previous mail. As supported by the vm-status output I attached, I had set --mode=global (not none) in step 1.</p>
<p dir="ltr">I am not the only one experiencing this. I can reproduce it easily. It appears that shutting down vdsm causes the HA services to incorrectly think the system has come out of Global Maintenance and restart the engine.</p>
<p dir="ltr">-Bob</p>
<div class="gmail_quote">On Jun 18, 2014 5:06 AM, "Federico Simoncelli" <<a href="mailto:fsimonce@redhat.com">fsimonce@redhat.com</a>> wrote:<br type="attribution"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
----- Original Message -----<br>
> From: "Bob Doolittle" <<a href="mailto:bob@doolittle.us.com">bob@doolittle.us.com</a>><br>
> To: "Doron Fediuck" <<a href="mailto:dfediuck@redhat.com">dfediuck@redhat.com</a>>, "Andrew Lau" <<a href="mailto:andrew@andrewklau.com">andrew@andrewklau.com</a>><br>
> Cc: "users" <<a href="mailto:users@ovirt.org">users@ovirt.org</a>>, "Federico Simoncelli" <<a href="mailto:fsimonce@redhat.com">fsimonce@redhat.com</a>><br>
> Sent: Saturday, June 14, 2014 1:29:54 AM<br>
> Subject: Re: [ovirt-users] Can HA Agent control NFS Mount?<br>
><br>
><br>
> But there may be more going on. Even if I stop vdsmd, the HA services,<br>
> and libvirtd, and sleep 60 seconds, I still see a lock held on the<br>
> Engine VM storage:<br>
><br>
> daemon 6f3af037-d05e-4ad8-a53c-61627e0c2464.xion2.smar<br>
> p -1 helper<br>
> p -1 listener<br>
> p -1 status<br>
> s 003510e8-966a-47e6-a5eb-3b5c8a6070a9:1:/rhev/data-center/mnt/<a href="http://xion2.smartcity.net" target="_blank">xion2.smartcity.net</a>\:_export_VM__NewDataDomain/003510e8-966a-47e6-a5eb-3b5c8a6070a9/dom_md/ids:0<br>
> s hosted-engine:1:/rhev/data-center/mnt/xion2\:_export_vm_he1/18eeab54-e482-497f-b096-11f8a43f94f4/ha_agent/hosted-engine.lockspace:0<br>
<br>
This output shows that the lockspaces are still acquired. When you put hosted-engine<br>
in maintenance they must be released.<br>
One by directly using rem_lockspace (since it's the hosted-engine one) and the other<br>
one by stopMonitoringDomain.<br>
<br>
I quickly looked at the ovirt-hosted-engine* projects and I haven't found anything<br>
related to that.<br>
<br>
--<br>
Federico<br>
</blockquote></div>