Bug 1147375

Summary: Empty PicketLink Subsystem disappears after reload
Product: [JBoss] JBoss Enterprise Application Platform 6 Reporter: Ondrej Lukas <olukas>
Component: PicketLinkAssignee: Pedro Igor <psilva>
Status: CLOSED CURRENTRELEASE QA Contact: Pavel Slavicek <pslavice>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 6.4.0CC: anmiller, bdawidow, kkhan, psilva
Target Milestone: DR7   
Target Release: EAP 6.4.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-08-19 12:43:01 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 Ondrej Lukas 2014-09-29 07:22:22 UTC 
Adding empty PicketLink Subsystem via CLI is not propagated into configuration. It turns server to reload-required state, but when server is reloaded PicketLink Subsystem disapears. This happens only if empty PicketLink Subsystem is added, when any next setting of subsystem is added (e.g. federation for Federation subsystem or partition-manager for IDM subsystem) then adding works fine.

How to reproduce:
1) Start EAP
2) Add PicketLink extension via CLI:
	/extension=org.wildfly.extension.picketlink:add()
3) Add one of PicketLink Subsystems (e.g. Federation subsystem):
	/subsystem=picketlink-federation:add()
4) Check whether subsystem was added (e.g. via read-resource operation):
	/subsystem=picketlink-federation:read-resource()
4) Reload server
	reload
5) Check again whether subsystem is still available (e.g. via read-resource operation):
	/subsystem=picketlink-federation:read-resource()

Current result:
PicketLink subsystem is not found.

Expected result:
PicketLink subsystem is found.
Comment 1 Josef Cacek 2014-09-29 07:41:46 UTC 
This problems are appearing again and again. Model reports "reload-required", but the reload will undo the operation. No word about it in documentation.

Summary
=======
Results coming from CLI: misleading
UX: bad
QE happiness: lagging
Comment 2 JBoss JIRA Server 2014-10-22 09:08:15 UTC 
Ondrej Lukas <olukas> updated the status of jira EAP6-182 to Reopened
Comment 3 Pedro Igor 2014-10-22 13:04:43 UTC 
https://github.com/jbossas/jboss-eap/pull/1838
Comment 4 Ondrej Lukas 2014-11-03 07:20:00 UTC 
Verified in EAP 6.4.0.DR7.
Comment 5 JBoss JIRA Server 2014-11-05 07:05:42 UTC 
Rostislav Svoboda <rsvoboda> updated the status of jira EAP6-182 to Resolved