Red Hat Bugzilla – Bug 1090914
MinimalVersionCheck job has incorrect instructions for upgrade of engine & dwh.
Last modified: 2016-02-10 14:14:53 EST
Description of problem: MinimalVersionCheck job has incorrect instructions for upgrade of engine & dwh. This is due to change to otopi setup and the fact that dwh is a plugin. Need to update the messages. Version-Release number of selected component (if applicable): 3.4.0 How reproducible: always Steps to Reproduce: 1. upgrade engine to 3.4.0 2. start dwh 3.3 Actual results: error says - "You have upgraded your oVirt Engine and now require an upgrade of the ovirt-engine-dwh package. Please upgrade using yum and run ovirt-engine-dwh-setup. Service will now exit." Expected results: should say - "You have upgraded your oVirt Engine and now require an upgrade of the ovirt-engine-dwh package. Please upgrade using yum and run engine-setup again. Service will now exit." Additional info:
Verification failed: av8.1: # rpm -qa | egrep 'rhevm-3|dwh|reports' | grep -v setup jasperreports-server-pro-5.5.0-6.el6ev.noarch rhevm-dwh-3.3.2-1.el6ev.noarch rhevm-reports-3.3.2-3.el6ev.noarch rhevm-3.4.0-0.16.rc.el6ev.noarch tail /var/log/ovirt-engine/ovirt-engine-dwhd.log: 2014-05-01 12:16:01|W4Xf4E|yfPOLK|yfPOLK|OVIRT_ENGINE_DWH|MinimalVersionCheck|Default|5|tDie|tDie_1|2014-05-01 12:16:01|You have upgraded your oVirt Engine and now require an upgrade of the ovirt-engine-dwh package. Please upgrade using yum and run ovirt-engine-dwh-setup. Service will now exit.|4 2014-05-01 12:16:01|You have upgraded your oVirt Engine and now require an upgrade of the ovirt-engine-dwh package. Please upgrade using yum and run ovirt-engine-dwh-setup. Service will now exit. Exception in component tRunJob_2 java.lang.RuntimeException: Child job running failed at ovirt_engine_dwh.historyetl_3_3.HistoryETL.tRunJob_2Process(HistoryETL.java:5800) at ovirt_engine_dwh.historyetl_3_3.HistoryETL$4.run(HistoryETL.java:7772) 2014-05-01 12:16:01|yfPOLK|yfPOLK|yfPOLK|OVIRT_ENGINE_DWH|HistoryETL|Default|6|Java Exception|tRunJob_2|java.lang.RuntimeException:Child job running failed|1 2014-05-01 12:16:01|ETL Service Stopped
Created attachment 891422 [details] dwh log
Please test 3.4 to 3.4 test by changing the db values manually. I added a release note for 3.3 that covers the upgrade to 3.4. Yaniv
(In reply to Yaniv Dary from comment #4) > Please test 3.4 to 3.4 test by changing the db values manually. > I added a release note for 3.3 that covers the upgrade to 3.4. > > > > Yaniv Which DB / table holds these records ?
vdc_options in engine. history_configuartion in ovirt_engine_history. Yaniv
Yaniv, Doesn't seem to work fixing the DB values: bash-4.1$ psql -d engine -c "select * from vdc_options where option_name = 'MinimalETLVersion';" | less -S could not change directory to "/root" option_id | option_name | option_value | version -----------+-------------------+--------------+--------- 238 | MinimalETLVersion | 3.3.3 | general bash-4.1$ psql -d ovirt_engine_history -c "select * from history_configuration where var_name = 'MinimalETLVersion';" | less -S could not change directory to "/root" var_name | var_value | var_datetime -------------------+-----------+-------------- MinimalETLVersion | 3.3.3 | [root@vm1 ~]# service ovirt-engine-dwhd start Starting oVirt Engine Dataware House: [ OK ] [root@vm1 ~]# service ovirt-engine-dwhd status ovirt-engine-dwhd (pid 17253) is running...
(In reply to Barak Dagan from comment #7) > Yaniv, > > Doesn't seem to work fixing the DB values: > > bash-4.1$ psql -d engine -c "select * from vdc_options where option_name = > 'MinimalETLVersion';" | less -S > could not change directory to "/root" > option_id | option_name | option_value | version > -----------+-------------------+--------------+--------- > 238 | MinimalETLVersion | 3.3.3 | general > > > > bash-4.1$ psql -d ovirt_engine_history -c "select * from > history_configuration where var_name = 'MinimalETLVersion';" | less -S > could not change directory to "/root" > var_name | var_value | var_datetime > -------------------+-----------+-------------- > MinimalETLVersion | 3.3.3 | > > > [root@vm1 ~]# service ovirt-engine-dwhd start > Starting oVirt Engine Dataware House: [ OK ] > > > [root@vm1 ~]# service ovirt-engine-dwhd status > ovirt-engine-dwhd (pid 17253) is running... Are you using the 3.4.0 packages? Yaniv
(In reply to Yaniv Dary from comment #8) > (In reply to Barak Dagan from comment #7) > > Yaniv, > > > > Doesn't seem to work fixing the DB values: > > > > bash-4.1$ psql -d engine -c "select * from vdc_options where option_name = > > 'MinimalETLVersion';" | less -S > > could not change directory to "/root" > > option_id | option_name | option_value | version > > -----------+-------------------+--------------+--------- > > 238 | MinimalETLVersion | 3.3.3 | general > > > > > > > > bash-4.1$ psql -d ovirt_engine_history -c "select * from > > history_configuration where var_name = 'MinimalETLVersion';" | less -S > > could not change directory to "/root" > > var_name | var_value | var_datetime > > -------------------+-----------+-------------- > > MinimalETLVersion | 3.3.3 | > > > > > > [root@vm1 ~]# service ovirt-engine-dwhd start > > Starting oVirt Engine Dataware House: [ OK ] > > > > > > [root@vm1 ~]# service ovirt-engine-dwhd status > > ovirt-engine-dwhd (pid 17253) is running... > > Are you using the 3.4.0 packages? > > Yes I am > > Yaniv
Verification failed on av9: rhevm-3.4.0-0.18.el6ev.noarch rhevm-dwh-3.4.0-9.el6ev.noarch rhevm-dwh-setup-3.4.0-9.el6ev.noarch rhevm-reports-3.4.0-9.el6ev.noarch rhevm-reports-setup-3.4.0-9.el6ev.noarch missing : "*Please upgrade using yum*" log: 2014-05-14 09:55:46|ETL Service Started 2014-05-14 09:55:46|wEHbwH|XO0g4c|XO0g4c|OVIRT_ENGINE_DWH|MinimalVersionCheck|Default|5|tDie|tDie_1|2014-05-14 09:55:46|You have upgraded your oVirt Engine and now require an upgrade of the ovirt-engine-dwh package. Please run engine-setup to upgrade the version. Service will now exit.|4 2014-05-14 09:55:46|You have upgraded your oVirt Engine and now require an upgrade of the ovirt-engine-dwh package. Please run engine-setup to upgrade the version. Service will now exit. Exception in component tRunJob_2 java.lang.RuntimeException: Child job running failed at ovirt_engine_dwh.historyetl_3_4.HistoryETL.tRunJob_2Process(HistoryETL.java:7152) at ovirt_engine_dwh.historyetl_3_4.HistoryETL$3.run(HistoryETL.java:9930) 2014-05-14 09:55:46|XO0g4c|XO0g4c|XO0g4c|OVIRT_ENGINE_DWH|HistoryETL|Default|6|Java Exception|tRunJob_2|java.lang.RuntimeException:Child job running failed|1 2014-05-14 09:55:46|ETL Service Stopped
(In reply to Barak Dagan from comment #10) > Verification failed on av9: > > rhevm-3.4.0-0.18.el6ev.noarch > rhevm-dwh-3.4.0-9.el6ev.noarch > rhevm-dwh-setup-3.4.0-9.el6ev.noarch > rhevm-reports-3.4.0-9.el6ev.noarch > rhevm-reports-setup-3.4.0-9.el6ev.noarch > > missing : "*Please upgrade using yum*" > > > log: > 2014-05-14 09:55:46|ETL Service Started > 2014-05-14 > 09:55: > 46|wEHbwH|XO0g4c|XO0g4c|OVIRT_ENGINE_DWH|MinimalVersionCheck|Default|5|tDie|t > Die_1|2014-05-14 09:55:46|You have upgraded your oVirt Engine and now > require an upgrade of the ovirt-engine-dwh package. Please run engine-setup > to upgrade the version. Service will now exit.|4 > 2014-05-14 09:55:46|You have upgraded your oVirt Engine and now require an > upgrade of the ovirt-engine-dwh package. Please run engine-setup to upgrade > the version. Service will now exit. > Exception in component tRunJob_2 > java.lang.RuntimeException: Child job running failed > at > ovirt_engine_dwh.historyetl_3_4.HistoryETL.tRunJob_2Process(HistoryETL.java: > 7152) > at > ovirt_engine_dwh.historyetl_3_4.HistoryETL$3.run(HistoryETL.java:9930) > 2014-05-14 > 09:55:46|XO0g4c|XO0g4c|XO0g4c|OVIRT_ENGINE_DWH|HistoryETL|Default|6|Java > Exception|tRunJob_2|java.lang.RuntimeException:Child job running failed|1 > 2014-05-14 09:55:46|ETL Service Stopped This is the correct instructions. otopi will do the update for the user from 3.4 and on. Yaniv
Not unless the dwh is upgraded using yum. Anyway, the returned results are different from the expected.
Pavel, Please advice.
Verified on av9.1. no longer reproducible, will be tested again on 3.5
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. http://rhn.redhat.com/errata/RHEA-2014-0601.html