[
https://issues.jboss.org/browse/WFCORE-3040?page=com.atlassian.jira.plugi...
]
ehsavoie Hugonnet updated WFCORE-3040:
--------------------------------------
Description:
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.
was:
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.
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.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)