Bug 1254676 - Installation of rhevm-reports prevents dwh configuration
Summary: Installation of rhevm-reports prevents dwh configuration
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Virtualization Manager
Classification: Red Hat
Component: ovirt-engine-reports
Version: 3.6.0
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ovirt-3.6.0-rc
: 3.6.0
Assignee: Yaniv Lavi
QA Contact: Lukas Svaty
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-08-18 15:58 UTC by Anton Marchukov
Modified: 2016-03-09 21:20 UTC (History)
10 users (show)

Fixed In Version: 3.6.0-beta2
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-03-09 21:20:26 UTC
oVirt Team: Integration
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
Answer file (3.78 KB, text/plain)
2015-08-18 15:58 UTC, Anton Marchukov
no flags Details
Setup log (4.29 MB, text/plain)
2015-08-18 15:59 UTC, Anton Marchukov
no flags Details


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHEA-2016:0425 0 normal SHIPPED_LIVE rhevm-reports bug fix and enhancement update 2016-03-10 01:21:14 UTC

Description Anton Marchukov 2015-08-18 15:58:08 UTC
Created attachment 1064371 [details]
Answer file

Description of problem:

When 3.6.0-9 is installed the regular way:

yum install http://bob.eng.lab.tlv.redhat.com/builds/3.6/3.6.0-9/rhev-release-3.6.0-001-0.12.3.6.0.noarch.rpm
yum install rhevm{,-dwh,-reports} -y

engine-setup with all the defaults fails with the following message:

[ INFO  ] Creating/refreshing Engine database schema
[ INFO  ] Creating/refreshing Engine AAA database schema
[ INFO  ] Creating CA
[ INFO  ] Creating/refreshing DWH database schema
[ ERROR ] Failed to execute stage 'Misc configuration': Cannot find Jboss at /usr/share/jboss-as
[ INFO  ] Yum Performing yum transaction rollback
[ INFO  ] Rolling back database schema
[ INFO  ] Clearing Engine database engine
[ INFO  ] Rolling back DWH database schema
[ INFO  ] Clearing DWH database ovirt_engine_history
[ INFO  ] Stage: Clean up
          Log file is located at /var/log/ovirt-engine/setup/ovirt-engine-setup-20150818183314-b0y6fy.log
[ INFO  ] Generating answer file '/var/lib/ovirt-engine/setup/answers/20150818183755-setup.conf'
[ INFO  ] Stage: Pre-termination
[ INFO  ] Stage: Termination
[ ERROR ] Execution of setup failed

It works if rhevm-reports is not installed.

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

3.6.0-9


Steps to Reproduce:

1. yum install http://bob.eng.lab.tlv.redhat.com/builds/3.6/3.6.0-9/rhev-release-3.6.0-001-0.12.3.6.0.noarch.rpm
2. yum install rhevm{,-dwh,-reports} -y
3. engine-setup
4. Use all the defaults


Actual results:

[ ERROR ] Failed to execute stage 'Misc configuration': Cannot find Jboss at /usr/share/jboss-as


Expected results:

Setup successfull

Additional info:

engine setup log and answer files are attached.

Comment 1 Anton Marchukov 2015-08-18 15:59:34 UTC
Created attachment 1064372 [details]
Setup log

Comment 2 Sandro Bonazzola 2015-08-19 07:42:48 UTC
Yaniv, is this a downstream branding issue?

Comment 3 Yaniv Lavi 2015-08-19 10:05:25 UTC
What is the version of the RPM use used? for reports\DWH?

Comment 5 Anton Marchukov 2015-08-19 10:40:57 UTC
(In reply to Yaniv Dary from comment #3)
> What is the version of the RPM use used? for reports\DWH?

rhevm-dwh-3.6.0-0.2.el6ev.noarch.rpm
rhevm-reports-3.6.0-0.4.el6ev.noarch.rpm

They are part of 3.6.0-9 beta release:
http://bob.eng.lab.tlv.redhat.com/builds/3.6/3.6.0-9/el6/noarch/

Comment 6 Lukas Svaty 2015-09-08 12:06:49 UTC
verified in rhevm-reports-3.6.0-0.6.el6ev.noarch

Comment 8 errata-xmlrpc 2016-03-09 21:20:26 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.

https://rhn.redhat.com/errata/RHEA-2016-0425.html


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