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.
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
Ondrej Lukas <olukas> updated the status of jira EAP6-182 to Reopened
https://github.com/jbossas/jboss-eap/pull/1838
Verified in EAP 6.4.0.DR7.
Rostislav Svoboda <rsvoboda> updated the status of jira EAP6-182 to Resolved