Re: [Users] Strange UI bug: tab "VM" unusable / oVirt 3.3.1+
On 10/12/13 03:29 PM, Michal Skrivanek wrote:
> On 10 Dec 2013, at 15:26, Frank Wall <fw(a)moov.de> wrote:
>
> Hi Roy,
>
>> On 2013-12-10 8:24, Roy Golan wrote:
>> 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';"
> engine=# select * from schema_version where version ='03030660';
> -[ RECORD 1 ]+---------------------------------------------------------
> id | 246
> version | 03030660
> script | upgrade/03_03_0660_add_enabled_column_to_policy_unit.sql
> checksum | 5e791c91f298ca662f275e21524e9e30
> installed_by | engine
> started_at | 2013-09-02 20:43:54.8651
> ended_at | 2013-09-02 20:43:54.900773
> state | INSTALLED
> current | f
> comment |
>
>
> Though I'm pretty sure the upgrade process (using `engine-setup`) did not report
any error. While grepping through all recent upgrade logs I cannot find any invocation of
03_03_0660_alter_os_type_unassigned_to_other.sql.
So it did run. It was supposed to change the id. Is it possible you so ehow overwrote it
manually or anything like that?
no it didn't. look at the script name. and Frank
says he can't find the
name in the log.
Something is wrong at this env since the script
upgrade/03_03_0660_add_enabled_column_to_policy_unit.sql
in the git repo is 03_03_0690 while 03_03_0660 should be the osinfo
script.
how was this engine installed, upgraded in time? nightly or with
official releases?
Please also try to "ls /usr/share/ovirt-engine/dbscripts/upgrade | grep
unassigned" so we would know if you have the script at all.
>
> Thanks
> - Frank