-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi,

I just post this if there is someone else stucked with the same problem...


https://bugzilla.redhat.com/show_bug.cgi?id=1067849


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.
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.

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.

PUUID=00000000-0000-0000-0000-000000000000,  this is a special value for no-such-volume

VOLTYPE=INTERNAL

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.

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.
So what I did was to change the VOLTYPE from "INTERNAL" to "LEAF".

I puted one of the nodes in maint. mode.
The last node I stopped vdsmd on.
Then I stopped ovirt-engine on the management server.
Changed the VOLTYPE from INTERNAL to LEAF.
Started the ovirt-engine.
Started the vdsmd on the first node

After a short while it got the SPM role and the status of everything was up.
I started the vm with the affected image and checked it booted OK.
I actived node 2

Everything wen up and the log files are all happy.

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.


Reproducible: Always



Expected Results:
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.




Regards //Ricky
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.14 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iEYEARECAAYFAlMHCIAACgkQOap81biMC2PlkACfTsylAS/dxgEy7G7aK3RHvV2m
7HAAnRwS8g30ob0sSkTJnk9jdlHIA6te
=ulMJ
-----END PGP SIGNATURE-----