Bug 880745

Summary: Upgrade from 3.0.x to 3.1 requires a standalone utility that enables to review async tasks and clean them
Product: Red Hat Enterprise Virtualization Manager Reporter: Yair Zaslavsky <yzaslavs>
Component: ovirt-engineAssignee: Yair Zaslavsky <yzaslavs>
Status: CLOSED ERRATA QA Contact: Pavel Stehlik <pstehlik>
Severity: high Docs Contact:
Priority: unspecified    
Version: 3.1.0CC: aburden, bazulay, cpelland, dyasny, hateya, iheim, lpeer, oourfali, pspacek, Rhev-m-bugs, sgordon, sgrinber, tvvcox, yeylon, ykaul
Target Milestone: ---Keywords: Improvement, ZStream
Target Release: 3.1.1   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard: infra
Fixed In Version: Doc Type: Enhancement
Doc Text:
A new tool, engine-async-tasks-cli, is available. This standalone utility is for erasing asynchronous tasks on upgrade from Red Hat Enterprise Virtualization 3.0 to 3.1.
Story Points: ---
Clone Of:
: 884794 (view as bug list) Environment:
Last Closed: 2013-01-15 15:13:18 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: Infra RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 883388, 884794    

Description Yair Zaslavsky 2012-11-27 17:44:08 UTC
Description of problem:

Upgrade from 3.0.x to 3.1 requires a tool that will provide information to the user about running tasks, and if it is safe to clear them.

The tool should include the following:

- list all tasks in details
- list all zombie tasks (according to the zombie task period as defined at vdc_options)
- clear task (by task id)
   Here we need to define carefully what is cleared when the task is not a zombie task)
- clear all zombies


Open issues -

For Clear all zombies - Should we check of locked entities ?

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


How reproducible:


Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info:

Comment 15 errata-xmlrpc 2013-01-15 15:13:18 UTC
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/RHBA-2013-0003.html