A service task can specify which nodes are allowed to pick up a service that is about to start using the allowedNodes option.
The smart modules extends some of these tasks options by allowing to choose if the task should be spread evenly onto other nodes using splitLogicallyOverNodes. But now these two options are clashing because the smart module would not check if the service is allowed to start on the node that was chosen for logically splitting the services.
Modification
Added a check to the smart modules splitLogicallyOverNodes handling which makes sure that only nodes are chosen that are allowed (if any are specified).
Result
The smart module options and service task options are not clashing anymore and respecting each other.
Motivation
A service task can specify which nodes are allowed to pick up a service that is about to start using the
allowedNodesoption. The smart modules extends some of these tasks options by allowing to choose if the task should be spread evenly onto other nodes usingsplitLogicallyOverNodes. But now these two options are clashing because the smart module would not check if the service is allowed to start on the node that was chosen for logically splitting the services.Modification
Added a check to the smart modules
splitLogicallyOverNodeshandling which makes sure that only nodes are chosen that are allowed (if any are specified).Result
The smart module options and service task options are not clashing anymore and respecting each other.
Other context
Fixes #1312