-
Bug
-
Resolution: Done
-
Major
-
7.1.0.DR13
-
None
-
User Experience
-
-
-
-
-
-
Not Required
When trying to remove a running server-config on slave host from host-master controller, the following message is produced in CLI:
[domain@localhost:9990 /] /host=hc1/server-config=server-two:remove()
{
"outcome" => "failed",
"result" => {},
"failure-description" => {"host-failure-descriptions" => {"hc1" => "WFLYHC0201: Error synchronizing the host model with the domain controller model with failure : WFLYCTL0063: Composite operation was rolled back."}},
"rolled-back" => true
}
This is not very informative. The error message from just removing running server-config managed by controller is different, and also much more informative:
[domain@localhost:9990 /] /host=master/server-config=server-two:remove()
{
"outcome" => "failed",
"result" => {},
"failure-description" => {"host-failure-descriptions" => {"master" => "WFLYHC0078: Server (server-two) still running"}},
"rolled-back" => true
}
- is cloned by
-
WFCORE-2360 Misleading failure description upon attempt of /host=slave/server-config=x:remove() when server-config=x is still running
-
- Resolved
-
- is incorporated by
-
JBEAP-9193 (7.1.0) Upgrade to WildFly Core to 3.0.0.Beta9
-
- Closed
-