-
Bug
-
Resolution: Won't Do
-
Major
-
None
-
None
-
None
-
Undefined
When we have a domain with several HCs, management operations that use wildcards are not correctly managed in all the cases.
For example, suppose we have a domain with one DC (without servers), one HC (without servers), and one HC (with servers):
[domain@localhost:9990 /] /host=*/server=*:read-resource-description()
{
"outcome" => "success",
"result" => [
{
"address" => [
("host" => "master"),
("server" => "*")
],
"outcome" => "success",
"result" => { ......
[domain@localhost:9990 /] /host=*/server=*/interface=management:read-resource-description()
{
"outcome" => "failed",
"result" => [
{
"address" => [
("host" => "localhost"),
("server" => "server-one"),
("interface" => "management")
],
"outcome" => "failed",
"result" => {....
The second operation returns results. We can say it failed because one of the HC has no servers and then the interface=management subresource doesn't exist.
However, If we have only one DC (without servers) and one HC (with servers) both operations are executed correctly and return the expected results. This seems to be inconsistent if we assume the operation should fail because the DC has no servers, hence the interface=management subresource is not available.
For example, executing the operation in a domain with a DC (without servers) we get:
[domain@localhost:9990 /] /host=*/server=*/interface=management:read-resource-description()
{
"outcome" => "failed",
"result" => [],
"failure-description" => "WFLYCTL0030: No resource definition is registered for address [
(\"host\" => \"*\"),
(\"server\" => \"*\")
]",
"rolled-back" => true
}