Bug 990518

Summary: config: [environment:default] overwrite instead of set default
Product: [oVirt] otopi Reporter: Ilanit Stein <istein>
Component: Plugins.coreAssignee: Alon Bar-Lev <alonbl>
Status: CLOSED CURRENTRELEASE QA Contact: Ilanit Stein <istein>
Severity: low Docs Contact:
Priority: unspecified    
Version: ---CC: acathrow, alonbl, bazulay, dougsland, iheim, Rhev-m-bugs, yeylon
Target Milestone: ---Keywords: Improvement, Triaged
Target Release: 1.1.0Flags: istein: devel_ack?
Hardware: Unspecified   
OS: Unspecified   
Whiteboard: integration
Fixed In Version: is10 Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-08-18 08:41:11 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:
Attachments:
Description Flags
engine-setup log none

Description Ilanit Stein 2013-07-31 11:18:37 UTC
Created attachment 781042 [details]
engine-setup log

Description of problem:

Running "engine-setup-2 --jboss-home=dir" do not run over jboss-home as expected.

/etc/ovirt-engine-setup.conf.d/10-packaging.conf 
still contain original jboss-home:
OVESETUP_CONFIG/jbossHome=str:/usr/share/jbossas

alonbl explanation:
In order to find jboss location which is different in distributions, we add this packaging file during rpm installation.
at fedora and rhel it is different setting
the --jboss-home should have overridden this setting, while the packaging file overwrite the parameter...

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

Comment 1 Alon Bar-Lev 2013-08-01 07:25:20 UTC
setting this as low, as:

1. production should not modify jboss home.

2. this can be achieved via configuration file.