Created attachment 1136228 [details]
logcollector from my personal RHEV VM built to test bug

Description of problem:
Fresh install RHEV 3.5.8 upgraded to RHEV 3.6 caused error that DWH was running, when it was not. Upgrade script did shutdown DWH, but RHEV database entry did not reflect this.

Version-Release number of selected component (if applicable):
RHEV 3.6
rhevm-setup-3.6.3.4-0.1.el6.noarch

How reproducible:
Two systems were built fresh, both exhibited the same problem and problem both were fixed the same way, manual modification of RHEV DB using:
UPDATE dwh_history_timekeeping SET var_value=0 WHERE var_name ='DwhCurrentlyRunning';

Steps to Reproduce:
1. Install RHEL 6.7 OS. After install, attached to Satellite 5.7 repo rhel-x86_64-server-6 (up to date as of 2016-03-02), run update then reboot:
yum update
shutdown -r now
2. Add repos for RHEV 3.5 (up to date as of 2016-03-10):
rhel-x86_64-server-supplementary-6
rhel-x86_64-server-6-rhevm-3.5
jbappplatform-6-x86_64-server-6-rpm
3. Install RHEV 3.5.8:
yum install rhevm rhevm-reports rhevm-dwh
engine-setup
4. Verify all packages up to date post RHEV 3.5 install, then reboot:
yum update
shutdown -r now
5. Upgrade RHEV by attaching repo rhel-x86_64-server-6-rhevm-3.6 (up to date as of 2016-03-10), then run:
yum update rhevm-setup
engine-setup

Actual results:
Error is reported in RHEV upgrade from engine-setup:
2016-03-10 11:39:41 ERROR otopi.plugins.ovirt_engine_setup.ovirt_engine_dwh.core.single_etl single_etl._transactionBegin:136 dwhd is currently running.

Expected results:
RHEV upgrades without need for manual intervention to pass test of if DWH is running.

Additional info:
Systems were checked after errors to see if DWH was running. Both systems showed DWH was not running via 'service ovirt-engine-dwhd status'. The command 'service ovirt-engine-dwhd stop' was also run to verify DWH was in fact not running.

I was not able to get logcollector from customer system, but I was able to get one from my local RHEV manager, file attached.