-
Bug
-
Resolution: Done
-
Major
-
None
-
None
There stuck some required service after unsuccessful command for adding CredentialStore with wrong filled relative-to attribute.
Command with wrong filled relative-to attribute
/subsystem=elytron/credential-store=CredStore108:add(uri="cr-store://test/cs108.jceks?create.storage=true", credential-reference={clear-text=pass123}, relative-to=non.exist.path.resource)
You can see this log.
Especially information about New missing/unsatisfied dependencies:is important and it wouldn't be there.
16:54:18,809 ERROR [org.jboss.as.controller.management-operation] (management-handler-thread - 8) WFLYCTL0013: Operation ("add") failed - address: ([ ("subsystem" => "elytron"), ("credential-store" => "CredStore108") ]) - failure description: { "WFLYCTL0412: Required services that are not installed:" => ["jboss.server.path.\"non.exist.path.resource\""], "WFLYCTL0180: Services with missing/unavailable dependencies" => ["org.wildfly.security.credential-store.CredStore108 is missing [jboss.server.path.\"non.exist.path.resource\"]"] } 16:54:18,810 INFO [org.jboss.as.controller] (management-handler-thread - 8) WFLYCTL0183: Service status report WFLYCTL0184: New missing/unsatisfied dependencies: service jboss.server.path."non.exist.path.resource" (missing) dependents: [service org.wildfly.security.credential-store.CredStore108]
Now we try process same command without relative-to attribute
/subsystem=elytron/credential-store=CredStore108:add(uri="cr-store://test/cs108.jceks?create.storage=true", credential-reference={clear-text=pass123})
Result is success but we can notice this in log:
16:55:33,093 INFO [org.jboss.as.controller] (management-handler-thread - 10) WFLYCTL0183: Service status report
WFLYCTL0185: Newly corrected services:
service jboss.server.path."non.exist.path.resource" (no longer required)
- clones
-
JBEAP-8509 There stuck some required service after unsuccessful command for adding CredentialStore with wrong filled relative-to attribute.
- Closed
- is related to
-
WFCORE-1762 Missing dependency should be triggering rollback of the deployment operation
- Resolved