-
Bug
-
Resolution: Won't Do
-
Major
-
None
-
3.0.0.Beta28
-
None
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:
/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
- is caused by
-
WFLY-9116 Eliminate use of RuntimeCapability.Builder add[Dynamic|Optional]Requirements, record missing requirements
- Closed
- relates to
-
WFCORE-3039 Capability requirement can be lost if two attributes on same resource reference the same capability
- Resolved