Bug 1139225 - setup doesn't clean up reports files correctly when canceled
Summary: setup doesn't clean up reports files correctly when canceled
Keywords:
Status: CLOSED DUPLICATE of bug 1130764
Alias: None
Product: Red Hat Enterprise Virtualization Manager
Classification: Red Hat
Component: ovirt-engine-reports
Version: 3.5.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: ---
Assignee: Shirly Radco
QA Contact: Pavel Stehlik
URL:
Whiteboard: integration
Depends On:
Blocks: 1072357
TreeView+ depends on / blocked
 
Reported: 2014-09-08 12:36 UTC by Petr Matyáš
Modified: 2014-09-09 12:01 UTC (History)
10 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-09-09 12:01:02 UTC
oVirt Team: ---
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

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 ***
Note You need to log in before you can comment on or make changes to this bug.