[Users] Upgrading dwh and reports from 3.3.4 to 3.4.0?

[Gianluca Cecchi]

On Sat, Apr 5, 2014 at 10:43 PM, Alon Bar-Lev <alonbl at redhat.com> wrote:

>>
>> If I try to run engine-setup again I get
>>
>> [root at tekkaman ~]# engine-setup
>> [ INFO  ] Stage: Initializing
>> [ INFO  ] Stage: Environment setup
>>           Configuration files:
>> ['/etc/ovirt-engine-setup.conf.d/10-packaging-aio.conf',
>> '/etc/ovirt-engine-setup.conf.d/10-packaging.conf',
>> '/etc/ovirt-engine-setup.conf.d/20-setup-aio.conf',
>> '/etc/ovirt-engine-setup.conf.d/20-setup-ovirt-post.conf']
>>           Log file:
>> /var/log/ovirt-engine/setup/ovirt-engine-setup-20140405184435.log
>>           Version: otopi-1.2.0 (otopi-1.2.0-1.fc19)
>> [ ERROR ] Failed to execute stage 'Environment setup': initial_value
>> must be unicode or None, not str
>> [ INFO  ] Stage: Clean up
>>           Log file is located at
>> /var/log/ovirt-engine/setup/ovirt-engine-setup-20140405184435.log
>> [ INFO  ] Stage: Pre-termination
>> [ INFO  ] Stage: Termination
>> [ ERROR ] Execution of setup failed
>
> Please attach setup log, need to see where it comes from.

here it is:
https://drive.google.com/file/d/0BwoPbcrMv8mvMnRMSm5oTF9NRUU/edit?usp=sharing


>
>>
>>  If I patch as in
>> http://gerrit.ovirt.org/#/c/26005/
>
> You should not patch unless we find an issue, but this error is strange, as patch does contains this variable[1]
>
> [1] http://gerrit.ovirt.org/#/c/26005/4/packaging/setup/ovirt_engine_setup/reportsconstants.py,cm
>
>>
>> I get
>> # engine-setup
>> [ INFO  ] Stage: Initializing
>> [ ERROR ] Failed to execute stage 'Initializing': type object
>> 'ConfigEnv' has no attribute 'LEGACY_REPORTS_WAR'
>> [ INFO  ] Stage: Clean up
>>           Log file is located at
>> /var/log/ovirt-engine/setup/ovirt-engine-setup-20140405190842.log
>> [ INFO  ] Stage: Pre-termination
>> [ INFO  ] Stage: Termination
>> [ ERROR ] Execution of setup failed
>>
>> any hint?
>
> Thanks!

I tried that patch because actually I also found this thread some days
ago with the same error and it was suggested to do so...
http://lists.ovirt.org/pipermail/users/2014-April/023083.html

the setup log about the run after patching is here:
https://drive.google.com/file/d/0BwoPbcrMv8mvWEc5UVV4a1BuNlk/edit?usp=sharing

Gianluca