Bug 759094 - ovirt's engine-config does not work, hard coded paths are incorrect
Summary: ovirt's engine-config does not work, hard coded paths are incorrect
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: oVirt
Classification: Retired
Component: ovirt-engine-config
Version: unspecified
Hardware: x86_64
OS: Linux
urgent
high
Target Milestone: ---
: ---
Assignee: Doron Fediuck
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-12-01 12:05 UTC by Ronen Angluster
Modified: 2012-08-09 07:58 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-08-09 07:58:05 UTC
oVirt Team: ---


Attachments (Terms of Use)

Description Ronen Angluster 2011-12-01 12:05:46 UTC
Description of problem:
The paths in engine-config are not on par with 
the RPM deployment.
paths are:
configuration: /etc/ovirt-engine/engine-config
jboss home: /usr/local/jboss
profile dir: /usr/local/jboss/server/default/
etc...
if any information is missing please contact me.

Comment 1 Doron Fediuck 2011-12-07 13:13:06 UTC
(In reply to comment #0)
> Description of problem:
> The paths in engine-config are not on par with 
> the RPM deployment.
> paths are:
> configuration: /etc/ovirt-engine/engine-config
> jboss home: /usr/local/jboss
> profile dir: /usr/local/jboss/server/default/
> etc...
> if any information is missing please contact me.

Please provide a full list of wrong variables, and the desired values.
Bear in mind this should be distro agnostic.

Comment 2 Ronen Angluster 2011-12-11 08:54:36 UTC
i do not know the full list of the wrong variables. for every one i changed another appeared.
please install ovirt-engine's rpm and see how everything i set up and adjust the utility according to those paths.

Comment 3 Doron Fediuck 2011-12-12 12:49:56 UTC
Proposed patch:
http://gerrit.ovirt.org/#change,565

Comment 6 Itamar Heim 2012-08-09 07:58:05 UTC
closing ON_QA bugs as oVirt 3.1 was released:
http://www.ovirt.org/get-ovirt/


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