<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<br>
<div class="moz-cite-prefix">On 26-03-2015 18:16, Christopher
Pereira wrote:<br>
</div>
<blockquote cite="mid:55147728.9030204@imatronix.cl" type="cite">Now,
how can I fix the "invalid lockspace"?
<br>
</blockquote>
hosted-engine start-pool + connect-storage + vm-start solved the
invalid lockspace problem and made it possible to restart the engine
VM, but the hosted-engine-setup is unable to resume:<br>
<blockquote>2015-03-26 21:56:42 DEBUG
otopi.plugins.ovirt_hosted_engine_setup.engine.add_host
add_host._wait_host_ready:189 VDSM host in non_responsive state<br>
2015-03-26 21:56:44 DEBUG
otopi.plugins.ovirt_hosted_engine_setup.engine.add_host
add_host._wait_host_ready:189 VDSM host in non_responsive state<br>
2015-03-26 21:56:46 DEBUG
otopi.plugins.ovirt_hosted_engine_setup.engine.add_host
add_host._wait_host_ready:189 VDSM host in non_responsive state<br>
[...]<br>
</blockquote>
Then, inside the web-manager, I tried to activate the host manually
and it seems like the engine stops VDSM:<br>
<blockquote>Mar 26 22:01:10 h2 systemd: Stopping Virtual Desktop
Server Manager...<br>
Mar 26 22:01:10 h2 journal: vdsm IOProcessClient ERROR IOProcess
failure<br>
Traceback (most recent call last):<br>
File "/usr/lib/python2.7/site-packages/ioprocess/__init__.py",
line 107, in _communicate<br>
raise Exception("FD closed")<br>
Exception: FD closed<br>
</blockquote>
And the engine-storage disappeared again.<br>
Then, since QEMU doesn't reopen the (invalid) file descriptors, the
VM can't be resumed (BZ 1058300).<br>
<br>
Is it normal that 1) the engine stops VDSM during activation and 2)
that VDSM stops or restarts the storage during shutdown?<br>
</body>
</html>