Bug 1200454 - Setup validation: Failed to clear zombie tasks after upgrade
Summary: Setup validation: Failed to clear zombie tasks after upgrade
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise Virtualization Manager
Classification: Red Hat
Component: ovirt-engine
Version: 3.5.1
Hardware: Unspecified
OS: Unspecified
urgent
urgent
Target Milestone: ovirt-3.6.0-rc
: 3.6.0
Assignee: Simone Tiraboschi
QA Contact: Petr Matyáš
URL:
Whiteboard:
Depends On:
Blocks: 1180867 1202334
TreeView+ depends on / blocked
 
Reported: 2015-03-10 15:25 UTC by Petr Matyáš
Modified: 2016-03-11 07:35 UTC (History)
11 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
With oVirt 3.5 we also have tables for async commands. The task cleaning utility should not only erase tasks, but should also erase commands that are associated with tasks.
Clone Of:
: 1202334 (view as bug list)
Environment:
Last Closed: 2016-03-11 07:35:20 UTC
oVirt Team: Integration
Target Upstream Version:
Embargoed:
stirabos: needinfo-


Attachments (Terms of Use)
Engine setup log (508.70 KB, text/plain)
2015-03-10 15:25 UTC, Petr Matyáš
no flags Details

Description Petr Matyáš 2015-03-10 15:25:27 UTC
Created attachment 1000013 [details]
Engine setup log

Description of problem:
After upgrade setup fails to clear zombie tasks.

Version-Release number of selected component (if applicable):
vt14

How reproducible:
always on my setup

Steps to Reproduce:
1. install and setup rhevm+dwh 3.4
2. upgrade to 3.5.1
3. engine-setup

Actual results:
fail to clear zombie tasks

Expected results:
successful setup

Additional info:

Comment 1 Sandro Bonazzola 2015-03-10 16:04:23 UTC
Can you please provide the logs?

Comment 2 Petr Matyáš 2015-03-10 16:10:19 UTC
What particular logs you want except the setup logs I already provided?

Comment 3 Simone Tiraboschi 2015-03-10 17:07:50 UTC

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

Comment 4 Petr Matyáš 2015-03-11 10:06:43 UTC
The bug 1161012 is for oVirt


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