<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<p>Hello,</p>
<p>I also see from the logs that all your Storage-Domains that work
are mounted as nfsVersion='V4' but
ovirt-nfs.netsec:/ovirt/hosted-engine is mounted as
nfsVersion='null'.</p>
<p>Bye<br>
</p>
<br>
<div class="moz-cite-prefix">Am 22.07.2016 um 16:17 schrieb Simone
Tiraboschi:<br>
</div>
<blockquote
cite="mid:CAN8-ONoS0cGbN3BBib32sUgEmiaCKg-_J4HJiTPDvJSjQ4RCyw@mail.gmail.com"
type="cite">
<pre wrap="">On Fri, Jul 22, 2016 at 3:47 PM, Robert Story <a class="moz-txt-link-rfc2396E" href="mailto:rstory@tislabs.com"><rstory@tislabs.com></a> wrote:
</pre>
<blockquote type="cite">
<pre wrap="">Hello,
I'm in the process of upgrading from 3.5.x to 3.6.x. My hosted engine and
hosts in the primary cluster are all upgraded and appear to be running fine.
I have a second cluster of 2 machines which are just regular hosts, without
the hosted-engine. Both have been marked non-operational, with the
following messages logged about every 5 minutes:
Failed to connect Host perses to Storage Pool Default
Host perses cannot access the Storage Domain(s) hosted_storage attached to the Data Center Default. Setting Host state to Non-Operational.
Host perses reports about one of the Active Storage Domains as Problematic.
Failed to connect Host perses to Storage Servers
Failed to connect Host perses to the Storage Domains hosted_storage.
I could see the normal storage/iso/export domains mounted on the host, and
the VMs running on the host are fine.
</pre>
</blockquote>
<pre wrap="">
In 3.5 only the hosts involved in hosted-engine have to access the
hosted-engine storage domain.
With 3.6 we introduced the capabilities to manage the engine VM from
the engine itself so the engine has to import in the hosted-engine
storage domain.
This means that all the hosts in the datacenter that contains the
cluster with the hosted-engine hosts have now to be able to connect
the hosted-engine storage domain.
Can you please check the ACL on the storage server (NFS or iSCSI) that
you use to expose the hosted-engine storage domain?
</pre>
<blockquote type="cite">
<pre wrap="">I shut down the VMs on one host, put it in maintenance mode, installed 3.6
repo and ran yum update. All went well, but when I activated the host, same
deal.
I've attached the engine log snippet for the activation attempt.
Robert
--
Senior Software Engineer @ Parsons
_______________________________________________
Users mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Users@ovirt.org">Users@ovirt.org</a>
<a class="moz-txt-link-freetext" href="http://lists.ovirt.org/mailman/listinfo/users">http://lists.ovirt.org/mailman/listinfo/users</a>
</pre>
</blockquote>
<pre wrap="">_______________________________________________
Users mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Users@ovirt.org">Users@ovirt.org</a>
<a class="moz-txt-link-freetext" href="http://lists.ovirt.org/mailman/listinfo/users">http://lists.ovirt.org/mailman/listinfo/users</a>
</pre>
</blockquote>
<br>
<div class="moz-signature">-- <br>
<p>
</p>
<table border="0" cellpadding="0" cellspacing="0">
<tbody>
<tr>
<td colspan="3"><img
src="cid:part1.28604224.8B5314B3@databay.de" height="30"
border="0" width="151"></td>
</tr>
<tr>
<td valign="top"> <font face="Verdana, Arial, sans-serif"
size="-1"><br>
<b>Ralf Schenk</b><br>
fon +49 (0) 24 05 / 40 83 70<br>
fax +49 (0) 24 05 / 40 83 759<br>
mail <a href="mailto:rs@databay.de"><font
color="#FF0000"><b>rs@databay.de</b></font></a><br>
</font> </td>
<td width="30"> </td>
<td valign="top"> <font face="Verdana, Arial, sans-serif"
size="-1"><br>
<b>Databay AG</b><br>
Jens-Otto-Krag-Straße 11<br>
D-52146 Würselen<br>
<a href="http://www.databay.de"><font color="#FF0000"><b>www.databay.de</b></font></a>
</font> </td>
</tr>
<tr>
<td colspan="3" valign="top"> <font face="Verdana, Arial,
sans-serif" size="1"><br>
Sitz/Amtsgericht Aachen • HRB:8437 • USt-IdNr.: DE
210844202<br>
Vorstand: Ralf Schenk, Dipl.-Ing. Jens Conze, Aresch
Yavari, Dipl.-Kfm. Philipp Hermanns<br>
Aufsichtsratsvorsitzender: Wilhelm Dohmen </font> </td>
</tr>
</tbody>
</table>
<hr color="#000000" noshade="noshade" size="1" width="100%">
</div>
</body>
</html>