[
https://issues.jboss.org/browse/WFCORE-3040?page=com.atlassian.jira.plugi...
]
Brian Stansberry commented on WFCORE-3040:
------------------------------------------
The WFCORE-1106 design is about tracking the capability dependencies. Are the dependencies
between these capabilities properly declared?
StepCapabilityStatus should take capability dependencies into
account
---------------------------------------------------------------------
Key: WFCORE-3040
URL:
https://issues.jboss.org/browse/WFCORE-3040
Project: WildFly Core
Issue Type: Bug
Components: Domain Management
Affects Versions: 3.0.0.Beta28
Reporter: ehsavoie Hugonnet
Assignee: Brian Stansberry
Currently at stage RUNTIME we check the stepCapabilityStatus before executing the OSH
associated with a capability. But this check doesn't take into account the state of
the capability dependencies.
For example if we add the undertow subsystem from scratch : the server service is not
added because its capability is RELOAD_REQUIRED but when adding the listener the
stepCapabilityStatus is NORMAL while it depends on a service that is in RELOAD_REQUIRED so
is potentially not there (which is the case) thus the RUNTIME OSH will fail instead of
being skipped.
Reproducer:
{code:java}
/extension=org.wildfly.extension.undertow:add(module="org.wildfly.extension.undertow")
/extension=org.wildfly.extension.io:add(module="org.wildfly.extension.io")
batch
/subsystem=undertow:add
/subsystem=undertow/servlet-container=default:add
/subsystem=undertow/server=default-server:add
/subsystem=undertow/server=default-server/host=default-host:add(alias=["localhost"])
/subsystem=undertow/server=default-server/http-listener=default:add(socket-binding="http")
/subsystem=undertow/buffer-cache=default:add
/subsystem=undertow/configuration=handler:add
/subsystem=undertow/configuration=filter:add
/subsystem=io:add
/subsystem=io/buffer-pool=default:add
/subsystem=io/worker=default:add
/socket-binding-group=standard-sockets/socket-binding=http:add(port="\${jboss.http.port:8080}")
run-batch
{code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)