On 10/12/13 08:50 AM, Michal Skrivanek wrote:
On Dec 9, 2013, at 17:20 , Tomas Jelinek <tjelinek@redhat.com> wrote:
----- Original Message -----
From: "Frank Wall" <fw@moov.de> To: "Tomas Jelinek" <tjelinek@redhat.com> Cc: "oVirt Users" <users@ovirt.org> Sent: Monday, December 9, 2013 3:56:21 PM Subject: Re: [Users] Strange UI bug: tab "VM" unusable / oVirt 3.3.1+
Hi Tomas,
On 2013-12-09 14:22, Tomas Jelinek wrote:
2: spiceSupportMatrix.get(osId) returned null. [...] I would guess this is the issue. To verify this could you please paste here the content of all .../osinfo.conf.d/*.properties and also the result of "select os, vm_name from vm_static" DB query so we can find which value is not there. you're right. I did a lookup in the database and compared the values to the entries in /etc/ovirt-engine/osinfo.conf.d/*.properties. I noticed that the "os" ID 6 is assigned multiple times, but not defined in a .properties file (anymore).
A quick check in the Admin Portal confirms this: open "Edit Virtual Machine" => Operating System: null
I can't remember what "os" ID 6 was in previous releases. Anyway, since I used this to classify my FreeBSD VMs, I've setup a new file defining it:
# cat /etc/ovirt-engine/osinfo.conf.d/freebsd.properties # FreeBSD(6, OsType.BSD, false), os.freebsd.id.value = 6 os.freebsd.name.value = FreeBSD os.freebsd.derivedFrom.value = other os.freebsd.description.value = FreeBSD Operating System os.freebsd.family.value = BSD
This fixed my issue, but I still would like to know why ID 6 was silently removed in 3.3.1 :-) Maybe it should be re-added in 3.3.2 to avoid this UI breakage for other people. Awesome!
So I had a look into the history of the osinfo-defaults.properties and the "6" used to be "Other": # Other(6, OsType.Other, false) os.Other.id.value = 6 os.Other.name.value = Other os.Other.derivedFrom.value = Unassigned
and it disappeared in this patch: http://gerrit.ovirt.org/#/c/16679/11
@Roy: Any reason this has been removed?
The removal is correct, we have two different "Other" types (Other, Unassigned) which didn't make sense, but this [1] upgrade script should have taken care of that Is it possible the upgrade went wrong?
Thanks, michal
[1] http://gerrit.ovirt.org/#/c/16679/11/packaging/dbscripts/upgrade/03_03_0660_...
Hi Frank can you run this so we would know if the script ever ran on your env? psql engine postgres -c "select * from schema_version where version ='03030660';"
Thanks - Frank
_______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users