From: "Gianluca Cecchi" <gianluca.cecchi(a)gmail.com>
To: "Alon Bar-Lev" <alonbl(a)redhat.com>
Cc: "users" <users(a)ovirt.org>
Sent: Sunday, April 6, 2014 11:57:27 AM
Subject: Re: [Users] Upgrading dwh and reports from 3.3.4 to 3.4.0?
On Sun, Apr 6, 2014 at 10:26 AM, Alon Bar-Lev <alonbl(a)redhat.com> wrote:
>
>
> ----- Original Message -----
>> From: "Gianluca Cecchi" <gianluca.cecchi(a)gmail.com>
>> To: "Alon Bar-Lev" <alonbl(a)redhat.com>
>> Cc: "users" <users(a)ovirt.org>
>> Sent: Sunday, April 6, 2014 10:57:42 AM
>> Subject: Re: [Users] Upgrading dwh and reports from 3.3.4 to 3.4.0?
>>
>> On Sun, Apr 6, 2014 at 2:13 AM, Alon Bar-Lev <alonbl(a)redhat.com> wrote:
>>
>> >
>> > This is a progress... :)
>>
>> I have not understood in what sense, but I trust you...
>>
>> >
>> > Now... do you have anything at:
>> >
>> >
/usr/share/jasperreports-server/buildomatic/build_conf/default/master.properties
>> >
>> > Do you have:
>> >
>> > /var/lib/ovirt-engine-reports/build-conf/master.properties
>>
>> yes see below. Note that I didn't complete the engine-setup process
>> But if this influences only my reports/dwh installation and not engine
>> itself is ok for me to run it again....
>> I suppose in case I have to drop before my preexisting reports/dwh
>> rdbms and so loose my previous data?
>
> OK, this is a bug, as the
> /var/lib/ovirt-engine-reports/build-conf/master.properties should been
> left only on success, while I see that if fail it is left, I will open a
> bug.
>
> Please remove /var/lib/ovirt-engine-reports/build-conf and re-run setup
> should attempt to upgrade again.
>
> Thanks,
> Alon
ok, done. I see your opened bugzilla entry.
Now:
[ INFO ] Stage: Setup validation
During execution engine service will be stopped (OK, Cancel) [OK]:
[ INFO ] Cleaning stale zombie tasks
--== CONFIGURATION PREVIEW ==--
Engine database name : engine
Engine database secured connection : False
Engine database host : localhost
Engine database user name : engine
Engine database host name validation : False
Engine database port : 5432
NFS setup : True
Firewall manager : iptables
Update Firewall : True
Configure WebSocket Proxy : True
Host FQDN :
tekkaman.localdomain.local
NFS mount point : /ISO
DWH installation : True
DWH database name : ovirt_engine_history
DWH database secured connection : False
DWH database host : localhost
DWH database user name : engine_history
DWH database host name validation : False
DWH database port : 5432
Reports installation : True
Reports database name : ovirtenginereports
Reports database secured connection : False
Reports database host : localhost
Reports database user name : engine_reports
Reports database host name validation : False
Reports database port : 5432
Please confirm installation settings (OK, Cancel) [OK]:
[ INFO ] Cleaning async tasks and compensations
[ INFO ] Checking the Engine database consistency
[ INFO ] Stage: Transaction setup
[ INFO ] Stopping engine service
[ INFO ] Stopping dwh service
[ INFO ] Stopping websocket-proxy service
[ INFO ] Stage: Misc configuration
[ INFO ] Stage: Package installation
[ INFO ] Stage: Misc configuration
[ INFO ] Backing up database localhost:engine to
'/var/lib/ovirt-engine/backups/engine-20140406105216.IjEVb2.sql'.
[ INFO ] Updating Engine database schema
[ INFO ] Backing up database localhost:ovirt_engine_history to
'/var/lib/ovirt-engine-dwh/backups/dwh-20140406105234.jk3lc9.sql'.
[ INFO ] Creating/refreshing DWH database schema
[ INFO ] Exporting data out of Jasper
[ INFO ] Regenerating Jasper's build configuration files
[ ERROR ] Failed to execute stage 'Misc configuration': Command
'./js-ant' failed to execute
[ INFO ] Yum Performing yum transaction rollback
[ INFO ] Rolling back database schema
[ INFO ] Clearing Engine database engine
[ INFO ] Restoring Engine database engine
[ INFO ] Rolling back DWH database schema
[ INFO ] Clearing DWH database ovirt_engine_history
[ INFO ] Restoring DWH database ovirt_engine_history
[ INFO ] Stage: Clean up
Log file is located at
/var/log/ovirt-engine/setup/ovirt-engine-setup-20140406105032.log
[ INFO ] Stage: Pre-termination
[ INFO ] Stage: Termination
[ ERROR ] Execution of setup failed
we come back with the problem you outlined with
BUILD FAILED
Target "gen-config-ce" does not exist in the project "buildomatic".
in setup log
see here:
https://drive.google.com/file/d/0BwoPbcrMv8mvM29QdXU2UUlHRHc/edit?usp=sha...
I suppose I have to remove again build-conf before proceedings with
other suggestions...
You need to remove and apply this[1] to fix that problem, I thought you applied it.
[1]