Bug 1152232 - ovirt-engine-dwh requires package dom4j
Summary: ovirt-engine-dwh requires package dom4j
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: oVirt
Classification: Retired
Component: ovirt-engine-dwh
Version: 3.5
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: ---
Assignee: Yedidyah Bar David
QA Contact: bugs@ovirt.org
URL:
Whiteboard: integration
Depends On:
Blocks: 1144079
TreeView+ depends on / blocked
 
Reported: 2014-10-13 16:05 UTC by Petr Matyáš
Modified: 2014-10-14 08:49 UTC (History)
9 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-10-14 08:49:41 UTC
oVirt Team: ---


Attachments (Terms of Use)

Description Petr Matyáš 2014-10-13 16:05:07 UTC
Description of problem:
When installing ovirt with yum, there is a missing dependency, the package dom4j was renamed to dom4j-eap6

Error: Package: ovirt-engine-dwh-3.5.0-1.el6.noarch (ovirt-3.5-qa-latest-local)
           Requires: dom4j

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

How reproducible:
Always on my setup

Steps to Reproduce:
1. yum install ovirt-engine-setup ovirt-engine-dwh-setup
2.
3.

Actual results:
Missing package dom4j

Expected results:
Correct installation

Additional info:

Comment 1 Yedidyah Bar David 2014-10-14 05:41:35 UTC
Which OS?

Comment 2 Shirly Radco 2014-10-14 06:44:27 UTC
I tested on both f19 and el6 and had no issues.
Please make sure you use a clean environment.

Shirly

Comment 3 Petr Matyáš 2014-10-14 07:59:07 UTC
RHEL 6.6, and it's clean, fresh install from PXE.

Comment 4 Yedidyah Bar David 2014-10-14 08:49:41 UTC
(After looking at Petr's machine. Thanks Petr!)

You mixed upstream and downstream repos.

For upstream ovirt-engine on rhel6, please use the provided package [1].
In particular, it adds the jpackage repo, which provides a dom4j package.

Downstream rhevm-dwh requires dom4j-eap6, which is provided in downstream jboss repos.

[1] http://resources.ovirt.org/pub/yum-repo/ovirt-release35.rpm


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