Bug 802689 - rhevm log not reporting vdsm service restart action roll back.
Summary: rhevm log not reporting vdsm service restart action roll back.
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: oVirt
Classification: Retired
Component: ovirt-engine-core
Version: unspecified
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: ---
Assignee: lpeer
QA Contact:
URL:
Whiteboard: infra
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-03-13 09:50 UTC by Ilanit Stein
Modified: 2012-12-13 08:12 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-12-13 08:12:51 UTC
oVirt Team: ---

Attachments (Terms of Use)
engine log, see 2012-03-04 10:46:00,345 (98.75 KB, application/x-compressed-tar)
2012-03-13 09:50 UTC, Ilanit Stein 		no flags Details
vdsm log (787.21 KB, application/x-xz)
2012-03-13 09:51 UTC, Ilanit Stein 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Description Ilanit Stein 2012-03-13 09:50:29 UTC 
Created attachment 569616 [details]
engine log, see 2012-03-04 10:46:00,345

Description of problem:

In case of a rolled back action, as a result of vdsm service restart, rhevm log not reporting on it, but instead, only fail action with result "cleanSuccsess". 

Details:

During VM sanity test, running on latest, on Jenkins, vdsm service restart, was done in parallel (unknown if initiated by vdsm or pappet). It failed Create vm from template. vdsm returned status "cleanSuccess"
rhevm reported action failed on result "cleanSuccess" (and not "success").

vdsm inquiry showed that the action was rolled back, as a result of the service vdsm restart.


Expected results:

rhevm log report on the action roll back, as a result of vdsm service restart
Comment 1 Ilanit Stein 2012-03-13 09:51:03 UTC 
Created attachment 569617 [details]
vdsm log
Comment 2 Itamar Heim 2012-12-13 08:12:51 UTC 
Closing old bugs. If this issue is still relevant/important in current version, please re-open the bug.
Note You need to log in before you can comment on or make changes to this bug.