-
Bug
-
Resolution: Done
-
Minor
-
8.0 Update 3.1
-
None
-
False
-
None
-
False
-
-
-
-
-
-
-
Cloning a profile with a target profile name of test, removing the cloned test profile again and then cloning another profile with a target profile name of test results in failed outcome, see:
[domain@localhost:9990 /] /profile=default:clone(to-profile=test) { "outcome" => "success", "result" => undefined, "server-groups" => undefined } [domain@localhost:9990 /] /profile=test:remove { "outcome" => "success", "result" => undefined, "server-groups" => undefined } [domain@localhost:9990 /] /profile=ha:clone(to-profile=test) { "outcome" => "failed", "failure-description" => {"domain-failure-description" => "WFLYCTL0436: Cannot register capability 'org.wildfly.ejb3.application-security-domain.known-deployments.other' at location '[ (\"profile\" => \"test\"), (\"subsystem\" => \"ejb3\"), (\"application-security-domain\" => \"other\") ]' as it is already registered in context 'profile=test' at location(s) '[[ (\"profile\" => \"test\"), (\"subsystem\" => \"ejb3\"), (\"application-security-domain\" => \"other\") ]]'"}, "rolled-back" => true }
- clones
-
WFLY-19843 EJB - application security domain doesn't remove capability
- Resolved
- is incorporated by
-
JBEAP-28024 (8.0.z) Upgrade EAP codebase to 8.0.7.GA-redhat-SNAPSHOT in EAP 8.0 Update 5
- Resolved