Details
-
Bug
-
Resolution: Won't Do
-
Major
-
None
-
None
-
None
Description
The sample domain mode configuration bundled in WildFly has two servers in started state and the third one (named server-three) is created in stopped state.
For stopped servers and for inventory v3, the agent reported the following for the "server config" resource:
{
"Status"=>"DISABLED",
"Server Group"=>"other-server-group",
"Auto Start"=>"false",
"Name"=>"server-three"
}
These data allowed MiQ to associate the server to the stated server group. Now, under inventory v4, reported config contains only:
{"Server State"=>"STOPPED"}
and nothing else. Given that the parent resource is the host master, now it's not possible to find which server group the server belongs to. MiQ relies on correctly associating to a server group to treat the server as a domain server.
For reference, this is the config data reported for running domain servers (reporting correctly the server group):
{
"Bound Address"=>"127.0.0.5",
"Node Name"=>"master:server-one",
"Base Directory"=>"/home/edgar/Projects/hawkular/hawkular-agent/hawkular-javaagent-wildfly-dist/target/hawkular-javaagent-wildfly-dist-2.0.0.Alpha1-SNAPSHOT/domain/servers/server-one",
"Server State"=>"running",
"Product Name"=>nil,
"Hostname"=>"teya",
"Host"=>"master",
"Server Group"=>"main-server-group",
"Initial Running Mode"=>"NORMAL",
"Name"=>"server-one",
"Suspend State"=>"RUNNING",
"Running Mode"=>"NORMAL",
"Version"=>nil,
"Profile Name"=>"full",
"UUID"=>"2af16a86-d88b-4013-9539-75040b11b0e9"
}
