Bug 1139225

Summary:	setup doesn't clean up reports files correctly when canceled
Product:	Red Hat Enterprise Virtualization Manager	Reporter:	Petr Matyáš <pmatyas>
Component:	ovirt-engine-reports	Assignee:	Shirly Radco <sradco>
Status:	CLOSED DUPLICATE	QA Contact:	Pavel Stehlik <pstehlik>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	3.5.0	CC:	bazulay, didi, dougsland, ecohen, gklein, iheim, pmatyas, rbalakri, Rhev-m-bugs, yeylon
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:	integration
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2014-09-09 12:01:02 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	1072357

Description Petr Matyáš 2014-09-08 12:36:46 UTC

Description of problem:
When running engine-setup with rhevm-reports otopi doesn't run clean up when killed with Ctrl+c. With error statement [ ERROR ] Failed to execute stage 'Misc configuration': Command './js-import.sh' failed to execute
War file is not deleted from /var/lib/ovirt-engine-reports/

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

How reproducible:
Always on my setup

Steps to Reproduce:
1. run engine-setup
2. kill with Ctrl+c after jasper is deployed
3.

Actual results:
Otopi doesn't run clean up

Expected results:
Otopi should run clean up

Additional info:

Comment 1 Shirly Radco 2014-09-08 13:54:29 UTC

What VT version did you test on ?
Is this happening only on this stage?

We had this issue with Michl when he was not using a clean installation and the otopi was different from what was required. Please discuss this with him. 

Shirly

Comment 3 Petr Matyáš 2014-09-08 16:15:05 UTC

I'm testing on vt2.2, otopi is version 1.3, system is clean. Michal told me to report this as otopi bug, not reports.

Comment 4 Yedidyah Bar David 2014-09-09 12:01:02 UTC

(In reply to Petr Matyáš from comment #3)
> I'm testing on vt2.2, otopi is version 1.3, system is clean. Michal told me
> to report this as otopi bug, not reports.

And he was right :-)
(actually rpm/yum, still need to find out)

Next time please attach logs just to make sure. See the description of the clone. If it's different, please reopen and attach logs. Thanks!

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