<html dir="ltr">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
<style id="owaParaStyle" type="text/css">P {margin-top:0;margin-bottom:0;}</style>
</head>
<body ocsi="0" fpstyle="1">
<div style="direction: ltr;font-family: Tahoma;color: #000000;font-size: 10pt;">Hello,<br>
<br>
We are on ovirt 3.3.1 and I just filed BZ 1039835 because our master <br>
storage domain could not be activated any longer after some NFS failure <br>
tests (pulling cables, modifying /etc/exports, ...). <br>
<br>
This bug seems to happen from time to time. Several BZ and mailing list<br>
entries suggest that the logic to track the domain version in critical<br>
situations is not yet perfect. <br>
<br>
I was able to clean the situation with a SQL modification in the database <br>
"update storage_pool set master_domain_version=...;"<br>
<br>
As it may be interesting for others could someone clarify if there might<br>
be an issue with atomic operations. Admins may have enough headaches <br>
to get the NFS up and running after some kind of failure. So Ovirt should <br>
not be one of them.<br>
<br>
Markus<br>
<br>
<br>
</div>
</body>
</html>