[
https://issues.jboss.org/browse/WFCORE-1260?page=com.atlassian.jira.plugi...
]
Brian Stansberry updated WFCORE-1260:
-------------------------------------
Description:
If you start a slave HC in admin-only with no master to connect to, boot is fine but then
any modifications made to the config result in capability resolution ERROR messages in the
host-controller.log
Starting a slave HC in admin-only with no master to connect to is meant to work, allowing
you to use CLI to manipulate the slave's host config:
{code}
bin/domain.sh --host-config=host-slave.xml --admin-only
-Djboss.domain.master.address=127.0.0.1
{code}
The boot is fine:
{code}
[Host Controller] 11:06:10,639 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0025:
WildFly Full 10.0.0.Final-SNAPSHOT (WildFly Core 2.0.5.Final) (Host Controller) started in
1152ms - Started 41 of 42 services (12 services are lazy, passive or on-demand)
{code}
However, subsequent changes made via management tools (e.g. CLI) succeed but result in
ERROR logging by the HC:
{code}
[domain@127.0.0.1:9999 /] /host=localhost/system-property=foo:add(value=bar)
{
"outcome" => "success",
"result" => undefined,
"server-groups" => undefined
}
{code}
The HC's log:
{code}
[Host Controller] 11:07:37,744 ERROR [org.jboss.as.controller] (management-handler-thread
- 4) WFLYCTL0369: Required capabilities are not available:
[Host Controller] org.wildfly.domain.server-group.other-server-group in context
'server-config'; There are no known registration points which can provide this
capability.
[Host Controller] org.wildfly.domain.server-group.main-server-group in context
'server-config'; There are no known registration points which can provide this
capability.
{code}
The boot works without logging because of the enhancement Stuart added such that
capability reference failures won't fail an admin-only boot, thus letting the user use
admin-only to fix the config. But then with subsequent changes, the user gets ERRORs
notifying them of the unfixed references.
But in this case, the references will never be available, so long as there is no
connection to a master to provide the domain-wide config.
This is a general case that needs to be accounted for in the capability resolution logic.
was:
If you start a slave HC in admin-only with no master to connect to, boot is fine but then
any modifications made to the config result in capabiloty resolution ERROR messages in the
host-controller.log
Starting a slave HC in admin-only with no master to connect to is meant to work, allowing
you to use CLI to manipulate the slave's host config:
{code}
bin/domain.sh --host-config=host-slave.xml --admin-only
-Djboss.domain.master.address=127.0.0.1
{code}
The boot is fine:
{code}
[Host Controller] 11:06:10,639 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0025:
WildFly Full 10.0.0.Final-SNAPSHOT (WildFly Core 2.0.5.Final) (Host Controller) started in
1152ms - Started 41 of 42 services (12 services are lazy, passive or on-demand)
{code}
However, subsequent changes made via management tools (e.g. CLI) succeed result in ERROR
logging by the HC:
{code}
[domain@127.0.0.1:9999 /] /host=localhost/system-property=foo:add(value=bar)
{
"outcome" => "success",
"result" => undefined,
"server-groups" => undefined
}
{code}
The HC's log:
{code}
[Host Controller] 11:07:37,744 ERROR [org.jboss.as.controller] (management-handler-thread
- 4) WFLYCTL0369: Required capabilities are not available:
[Host Controller] org.wildfly.domain.server-group.other-server-group in context
'server-config'; There are no known registration points which can provide this
capability.
[Host Controller] org.wildfly.domain.server-group.main-server-group in context
'server-config'; There are no known registration points which can provide this
capability.
{code}
The boot works without logging because of the enhancement Stuart added such that
capability references failures won't fail an admin-only boot, thus letting the user
use admin-only to fix the changes. But then with subsequent changes, the user gets ERRORs
notifying them of the unfixed references.
But in this case, the references will never be available, so long as there is no
connection to a master to provide the domain-wide config.
This is a general case that needs to be accounted for in the capability resolution logic.
Capability resolution complaints on admin-only slave HCs not
connected to the master
------------------------------------------------------------------------------------
Key: WFCORE-1260
URL:
https://issues.jboss.org/browse/WFCORE-1260
Project: WildFly Core
Issue Type: Bug
Components: Domain Management
Affects Versions: 2.0.5.Final
Reporter: Brian Stansberry
Assignee: Brian Stansberry
If you start a slave HC in admin-only with no master to connect to, boot is fine but then
any modifications made to the config result in capability resolution ERROR messages in the
host-controller.log
Starting a slave HC in admin-only with no master to connect to is meant to work, allowing
you to use CLI to manipulate the slave's host config:
{code}
bin/domain.sh --host-config=host-slave.xml --admin-only
-Djboss.domain.master.address=127.0.0.1
{code}
The boot is fine:
{code}
[Host Controller] 11:06:10,639 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0025:
WildFly Full 10.0.0.Final-SNAPSHOT (WildFly Core 2.0.5.Final) (Host Controller) started in
1152ms - Started 41 of 42 services (12 services are lazy, passive or on-demand)
{code}
However, subsequent changes made via management tools (e.g. CLI) succeed but result in
ERROR logging by the HC:
{code}
[domain@127.0.0.1:9999 /] /host=localhost/system-property=foo:add(value=bar)
{
"outcome" => "success",
"result" => undefined,
"server-groups" => undefined
}
{code}
The HC's log:
{code}
[Host Controller] 11:07:37,744 ERROR [org.jboss.as.controller] (management-handler-thread
- 4) WFLYCTL0369: Required capabilities are not available:
[Host Controller] org.wildfly.domain.server-group.other-server-group in context
'server-config'; There are no known registration points which can provide this
capability.
[Host Controller] org.wildfly.domain.server-group.main-server-group in context
'server-config'; There are no known registration points which can provide this
capability.
{code}
The boot works without logging because of the enhancement Stuart added such that
capability reference failures won't fail an admin-only boot, thus letting the user use
admin-only to fix the config. But then with subsequent changes, the user gets ERRORs
notifying them of the unfixed references.
But in this case, the references will never be available, so long as there is no
connection to a master to provide the domain-wide config.
This is a general case that needs to be accounted for in the capability resolution logic.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)