<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<br>
-----BEGIN PGP SIGNED MESSAGE-----<br>
Hash: SHA1<br>
<br>
Hi,<br>
<br>
I just post this if there is someone else stucked with the same
problem...<br>
<br>
<br>
<a class="moz-txt-link-freetext" href="https://bugzilla.redhat.com/show_bug.cgi?id=1067849">https://bugzilla.redhat.com/show_bug.cgi?id=1067849</a><br>
<br>
<br>
After a successful upgrade of oVirt 3.1 > 3.2.2, every vm up and
running and every function verified, I decide to even upgrade my
cluster compability level to 3.2 from earlier 3.1. When trying to
upgrade the Data Center to 3.2 I was adviced to even upgrade the
Cluster level to 3.2. When trying to do that I was adviced to put my
nodes in maint. mode so I did.<br>
Everything went OK according to event log in webadmin and now I put
the nodes back UP again. None of the nodes got the SPM role and just
keep switching over and over again trying to contend. As a result
the Data Center was in a no go state and down.<br>
<br>
It the log file I found "ImageIsNotLegalChain: Image is not a legal
chain: ('5d9cc5dc-7664-4624-8e72-479a7cec35f5',)" telling us that
the image should be a node in a chain of volumes. When looking in
the meta file we could not find a reference to a parent UUID.<br>
<br>
PUUID=00000000-0000-0000-0000-000000000000, this is a special value
for no-such-volume<br>
<br>
VOLTYPE=INTERNAL<br>
<br>
So, My vm was up and running earlier in oVirt 3.2.2 and it just
stopped working after I upgraded the compatibility level of the
cluster.<br>
<br>
If I moved the image out from the file structure of the data domain
everything should be happy but then I would miss my vm.<br>
So what I did was to change the VOLTYPE from "INTERNAL" to "LEAF".<br>
<br>
I puted one of the nodes in maint. mode.<br>
The last node I stopped vdsmd on.<br>
Then I stopped ovirt-engine on the management server.<br>
Changed the VOLTYPE from INTERNAL to LEAF.<br>
Started the ovirt-engine.<br>
Started the vdsmd on the first node<br>
<br>
After a short while it got the SPM role and the status of everything
was up.<br>
I started the vm with the affected image and checked it booted OK.<br>
I actived node 2<br>
<br>
Everything wen up and the log files are all happy.<br>
<br>
The affected image is an old image that was first created with ovirt
3.0 and then it has men exported and imported a couple of times.<br>
<br>
<br>
Reproducible: Always<br>
<br>
<br>
<br>
Expected Results:<br>
If there is bad images (wrong meta data) it should take care of that
and mark these. What we want is the Data center up and running.<br>
<br>
<br>
<br>
<br>
Regards //Ricky<br>
-----BEGIN PGP SIGNATURE-----<br>
Version: GnuPG v1.4.14 (GNU/Linux)<br>
Comment: Using GnuPG with Thunderbird - <a class="moz-txt-link-freetext" href="http://www.enigmail.net/">http://www.enigmail.net/</a><br>
<br>
iEYEARECAAYFAlMHCIAACgkQOap81biMC2PlkACfTsylAS/dxgEy7G7aK3RHvV2m<br>
7HAAnRwS8g30ob0sSkTJnk9jdlHIA6te<br>
=ulMJ<br>
-----END PGP SIGNATURE-----<br>
<br>
</body>
</html>