Bug 1190228 - Upgrade from 3.4 is broken
Summary: Upgrade from 3.4 is broken
Keywords:
Status: CLOSED DUPLICATE of bug 1161012
Alias: None
Product: oVirt
Classification: Retired
Component: ovirt-engine-installer
Version: 3.5
Hardware: Unspecified
OS: Unspecified
unspecified
urgent
Target Milestone: ---
: 3.5.2
Assignee: Simone Tiraboschi
QA Contact: Pavel Stehlik
URL:
Whiteboard: integration
Depends On:
Blocks: oVirt_3.5.2_tracker 1193058
TreeView+ depends on / blocked
 
Reported: 2015-02-06 17:33 UTC by David Caro
Modified: 2016-06-26 23:50 UTC (History)
9 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2015-02-09 12:32:00 UTC
oVirt Team: ---
Embargoed:


Attachments (Terms of Use)

Description David Caro 2015-02-06 17:33:48 UTC
Description of problem:
When upgrading an ovirt 3.4 installation to 3.5, we are seeing this error:

2015-02-04 15:50:29 DEBUG otopi.plugins.ovirt_engine_setup.ovirt_engine.upgrade.asynctasks plugin.executeRaw:803 execute-result: ('/usr/share/ovirt-engine/setup/dbutils/taskcleaner.sh', '-l', '/var/log/ovirt-engine/setup/ovirt-engine-setup-20150204155001-xiivim.log', '-u', 'engine', '-s', 'localhost', '-p', '5432', '-d', 'engine', '-R', '-A', '-J', '-q'), rc=1
2015-02-04 15:50:29 DEBUG otopi.plugins.ovirt_engine_setup.ovirt_engine.upgrade.asynctasks plugin.execute:861 execute-output: ('/usr/share/ovirt-engine/setup/dbutils/taskcleaner.sh', '-l', '/var/log/ovirt-engine/setup/ovirt-engine-setup-20150204155001-xiivim.log', '-u', 'engine', '-s', 'localhost', '-p', '5432', '-d', 'engine', '-R', '-A', '-J', '-q') stdout:


2015-02-04 15:50:29 DEBUG otopi.plugins.ovirt_engine_setup.ovirt_engine.upgrade.asynctasks plugin.execute:866 execute-output: ('/usr/share/ovirt-engine/setup/dbutils/taskcleaner.sh', '-l', '/var/log/ovirt-engine/setup/ovirt-engine-setup-20150204155001-xiivim.log', '-u', 'engine', '-s', 'localhost', '-p', '5432', '-d', 'engine', '-R', '-A', '-J', '-q') stderr:
psql:/usr/share/ovirt-engine/setup/dbutils/taskcleaner_sp.sql:145: ERROR:  type "command_entities" does not exist
FATAL: Cannot execute sql command: --file=/usr/share/ovirt-engine/setup/dbutils/taskcleaner_sp.sql

2015-02-04 15:50:29 DEBUG otopi.context context._executeMethod:152 method exception
Traceback (most recent call last):
  File "/usr/lib/python2.6/site-packages/otopi/context.py", line 142, in _executeMethod
    method['method']()
  File "/usr/share/ovirt-engine/setup/bin/../plugins/ovirt-engine-setup/ovirt-engine/upgrade/asynctasks.py", line 422, in _validateZombies
    self._clearZombieTasks()
  File "/usr/share/ovirt-engine/setup/bin/../plugins/ovirt-engine-setup/ovirt-engine/upgrade/asynctasks.py", line 156, in _clearZombieTasks
    'Failed to clear zombie tasks. Please access support '
RuntimeError: Failed to clear zombie tasks. Please access support in attempt to resolve the problem
2015-02-04 15:50:29 ERROR otopi.context context._executeMethod:161 Failed to execute stage 'Setup validation': Failed to clear zombie tasks. Please access support in attempt to resolve the problem

And the upgrade does not finish properly

Version-Release number of selected component (if applicable):
ovirt-engine-3.5

How reproducible:
See the jenkins job:
  http://jenkins.ovirt.org/job/ovirt-engine_3.5_upgrade-from-3.4_merged/1371/label=el6/console

Steps to Reproduce:
1.Install ovirt engine 3.4
2.Upgrade to ovirt engine 3.5
3.

Actual results:
Upgrade fails

Expected results:
Upgrade works

Additional info:
See the jenkins job:
  http://jenkins.ovirt.org/job/ovirt-engine_3.5_upgrade-from-3.4_merged/1371/label=el6/console

Comment 1 Sandro Bonazzola 2015-02-09 11:47:19 UTC
Error is:

15:50:28 [ ERROR ] Failed to execute stage 'Setup validation': Failed to clear zombie tasks. Please access support in attempt to resolve the problem
15:50:28 [ INFO  ] Stage: Clean up
15:50:28           Log file is located at /var/log/ovirt-engine/setup/ovirt-engine-setup-20150204155001-xiivim.log

Which seems to be related to: http://gerrit.ovirt.org/36302

Simone, can you investigate?

Comment 2 Simone Tiraboschi 2015-02-09 12:32:00 UTC

*** This bug has been marked as a duplicate of bug 1161012 ***


Note You need to log in before you can comment on or make changes to this bug.