Bug 1001633

Summary: [as7] system property created at the time of server group creation will not persist
Product: [JBoss] JBoss Operations Network Reporter: Dasharath Masirkar <dmasirka>
Component: Plugin -- JBoss EAP 6Assignee: Libor Zoubek <lzoubek>
Status: CLOSED CURRENTRELEASE QA Contact: Mike Foley <mfoley>
Severity: high Docs Contact:
Priority: unspecified    
Version: JON 3.1.2CC: loleary, lzoubek, skondkar, steven.post, theute, tsegismo
Target Milestone: DR01   
Target Release: JON 3.2.1   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-05-08 17:44:13 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:

Description Dasharath Masirkar 2013-08-27 12:34:00 UTC 
Description of problem:
The system property created at the time of server group creation will not exist once the server group created successfully. It require additional effort to recreate it again on newly created server group.
 

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

How reproducible:
Always

Steps to Reproduce:
1. Import domain EAP 6 server into JON inventory
2. in JON, go to the Domain controller, right click and select 'create child - servergroup'
3. enter name, click 'next'
4. choose profile and socket bindings
5. Add a system property (for example 'UseJK', with value 'true'), set 'boot time to true', click 'OK'
6. Observe that the property is in the list, but yet 'boot time' is not marked
7. click 'finish'
8. Observe in JON that the new server group exists, but without the property, this can also be verified with the EAP management console.

Actual results:
System property created at the time of server group creation will not persist into server group configuration.

Expected results:
System property created at the time of server group creation must be persist into server group configuration.

Additional info:
Comment 2 Libor Zoubek 2014-02-07 14:21:15 UTC 
in master

commit 07ceb9373badce39b10151ddef36ce8183fb19d2
Author: Libor Zoubek <lzoubek>
Date:   Fri Feb 7 15:06:15 2014 +0100
Comment 3 Thomas Segismont 2014-02-07 22:05:02 UTC 
Tested and cherry-picked over to release/jon3.2.x

commit d06aa46c093520cf19186205aae0bb7a0b880271
Author: Libor Zoubek <lzoubek>
Date:   Fri Feb 7 15:06:15 2014 +0100

(cherry picked from commit 07ceb9373badce39b10151ddef36ce8183fb19d2)
Signed-off-by: Thomas Segismont <tsegismo>
Comment 4 Simeon Pinder 2014-02-18 15:08:37 UTC 
Moving to ON_QA as available for testing in the following brew build:
https://brewweb.devel.redhat.com//buildinfo?buildID=336752

Note: the installed version is still JON 3.2.0.GA by design and this represents part of the payload for JON 3.2.1 also known as cumulative patch 1 for 3.2.0.GA.  How this will be delivered to customers is still being discussed.
Comment 5 Sunil Kondkar 2014-02-21 08:02:24 UTC 
Verified on JON 3.2.1 DR01 build (Build Number :c758688:4c03150)

Followed the steps and verified that system property created at the time of server group creation exists in server group configuration.
Comment 6 Mike Foley 2014-05-08 17:44:13 UTC 
JON 3.2.1 released week of 5/5/2014