3:10 a.m.
This is a multi-part message in MIME format.
--------------000900020607080304050108
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Specifically, if do the following:
* Enter global maintenance (hosted-engine --set-maintenance-mode
--mode=global)
* init 0 the engine
* systemctl stop ovirt-ha-agent ovirt-ha-broker libvirtd vdmsd
and then run "sanlock client status" I see:
# sanlock client status
daemon c715b5de-fd98-4146-a0b1-e9801179c768.xion2.smar
p -1 helper
p -1 listener
p -1 status
s
003510e8-966a-47e6-a5eb-3b5c8a6070a9:1:/rhev/data-center/mnt/xion2.smartcity.net\:_export_VM__NewDataDomain/003510e8-966a-47e6-a5eb-3b5c8a6070a9/dom_md/ids:0
s
18eeab54-e482-497f-b096-11f8a43f94f4:1:/rhev/data-center/mnt/xion2\:_export_vm_he1/18eeab54-e482-497f-b096-11f8a43f94f4/dom_md/ids:0
s
hosted-engine:1:/rhev/data-center/mnt/xion2\:_export_vm_he1/18eeab54-e482-497f-b096-11f8a43f94f4/ha_agent/hosted-engine.lockspace:0
Waiting a few minutes does not change this state.
The earlier data I shared which showed HostedEngine was with a different
test scenario.
-Bob
On 06/18/2014 07:53 AM, Bob Doolittle wrote:
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.
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.
-Bob
On Jun 18, 2014 5:06 AM, "Federico Simoncelli" <fsimonce(a)redhat.com
<mailto:fsimonce@redhat.com>> wrote:
----- Original Message -----
> From: "Bob Doolittle" <bob(a)doolittle.us.com
<mailto:bob@doolittle.us.com>>
> To: "Doron Fediuck" <dfediuck(a)redhat.com
<mailto:dfediuck@redhat.com>>, "Andrew Lau"
<andrew(a)andrewklau.com
<mailto:andrew@andrewklau.com>>
> Cc: "users" <users(a)ovirt.org <mailto:users@ovirt.org>>,
"Federico Simoncelli" <fsimonce(a)redhat.com
<mailto:fsimonce@redhat.com>>
> Sent: Saturday, June 14, 2014 1:29:54 AM
> Subject: Re: [ovirt-users] Can HA Agent control NFS Mount?
>
>
> But there may be more going on. Even if I stop vdsmd, the HA
services,
> and libvirtd, and sleep 60 seconds, I still see a lock held on the
> Engine VM storage:
>
> daemon 6f3af037-d05e-4ad8-a53c-61627e0c2464.xion2.smar
> p -1 helper
> p -1 listener
> p -1 status
> s
003510e8-966a-47e6-a5eb-3b5c8a6070a9:1:/rhev/data-center/mnt/xion2.smartc...
<http://xion2.smartcity.net>\:_export_VM__NewDataDomain/003510e8-966a-4...
> s
hosted-engine:1:/rhev/data-center/mnt/xion2\:_export_vm_he1/18eeab54-e482-497f-b096-11f8a43f94f4/ha_agent/hosted-engine.lockspace:0
This output shows that the lockspaces are still acquired. When you
put hosted-engine
in maintenance they must be released.
One by directly using rem_lockspace (since it's the hosted-engine
one) and the other
one by stopMonitoringDomain.
I quickly looked at the ovirt-hosted-engine* projects and I
haven't found anything
related to that.
--
Federico
--------------000900020607080304050108
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: 7bit
<html>
<head>
<meta content="text/html; charset=UTF-8"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
Specifically, if do the following:<br>
<ul>
<li>Enter global maintenance (hosted-engine --set-maintenance-mode
--mode=global)</li>
<li>init 0 the engine</li>
<li>systemctl stop ovirt-ha-agent ovirt-ha-broker libvirtd vdmsd</li>
</ul>
<br>
and then run "sanlock client status" I see:<br>
<br>
<pre># sanlock client status
daemon c715b5de-fd98-4146-a0b1-e9801179c768.xion2.smar
p -1 helper
p -1 listener
p -1 status
s
003510e8-966a-47e6-a5eb-3b5c8a6070a9:1:/rhev/data-center/mnt/xion2.smartcity.net\:_export_VM__NewDataDomain/003510e8-966a-47e6-a5eb-3b5c8a6070a9/dom_md/ids:0
s
18eeab54-e482-497f-b096-11f8a43f94f4:1:/rhev/data-center/mnt/xion2\:_export_vm_he1/18eeab54-e482-497f-b096-11f8a43f94f4/dom_md/ids:0
s
hosted-engine:1:/rhev/data-center/mnt/xion2\:_export_vm_he1/18eeab54-e482-497f-b096-11f8a43f94f4/ha_agent/hosted-engine.lockspace:0
</pre>
<br>
Waiting a few minutes does not change this state.<br>
<br>
The earlier data I shared which showed HostedEngine was with a
different test scenario.<br>
<br>
-Bob<br>
<br>
<div class="moz-cite-prefix">On 06/18/2014 07:53 AM, Bob Doolittle
wrote:<br>
</div>
<blockquote
cite="mid:CA+4jJ+se2odydTJySxvwMaA3G7zOUZsZdWDFE6ajFFDMVwiA9A@mail.gmail.com"
type="cite">
<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 moz-do-not-send="true"
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
moz-do-not-send="true"
href="mailto:bob@doolittle.us.com">bob@doolittle.us.com</a>><br>
> To: "Doron Fediuck" <<a
moz-do-not-send="true"
href="mailto:dfediuck@redhat.com">dfediuck@redhat.com</a>>,
"Andrew Lau" <<a moz-do-not-send="true"
href="mailto:andrew@andrewklau.com">andrew@andrewklau.com</a>><br>
> Cc: "users" <<a moz-do-not-send="true"
href="mailto:users@ovirt.org">users@ovirt.org</a>>,
"Federico Simoncelli" <<a moz-do-not-send="true"
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
moz-do-not-send="true" 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>
</blockquote>
<br>
</body>
</html>
--------------000900020607080304050108--