On Thursday 03 April 2014 13:05:36 Roy Golan wrote: > On Wed 02 Apr 2014 04:48:12 PM IDT, Stefan Wendler wrote: >> On Wednesday 02 April 2014 16:16:34 Roy Golan wrote: >>> an upgrade to 3.3 should have run an upgrade script [1] and update all >>> vms with 6 to 0 (the new internal id of other) >>> >>> can you run this sql [2] to see if it did ran? >>> >>> [1] 03_03_0660_alter_os_type_unassigned_to_other.sql >>> [2] psql engine engine -c "select * from schema_version where script >>> ilike '%unassigned%';" >> The query [2] returns "0 rows" > this upgrade is from 3.3.4 to 3.4 i think. did you ever upgraded from > 3.2 to 3.3? if yes then we need that upgrade log. AFAIR we started with 3.3 on our production environment. Yes this is from 3.3.4 to 3.4. We had 3.3.0 before and I upgraded to 3.3.4 before going to 3.4 > more directions - did you anytime override the osinfo files or added > some custom ones? please paste the content of > /etc/ovirt-engine/osinfo.conf.d and > /usr/share/ovirt-engine/conf/osinfo-defaults.properties /usr/share/ovirt-engine/conf/osinfo-defaults.properties of the centos rpm with the one from the current sources. But it didn't work before that. I just replaced them to check if this would fix it. Until then I never heard of this osinfo file so I never changed/replaced it before. > if non of this has relevant results than its totally safe to run the > script above mentioned [1] This is the distribution of "os-types" in our database: engine=# select count(*), os from vm_static group by os order by os; count | os -------+------ 5 | 0 3 | 1 1 | 4 46 | 5 1 | 11 1 | 12 1 | 16 1 | 1501 (8 rows) So it wouldn't make much sense to execute the "03_03_0660_alter_os_type_unassigned_to_other.sql" ?

Regarding the config I send you a link to the tgz with all files. I don't want to put the link public because it is my private server with not so much bandwith ;) Cheers, Stefan