@FlareImp Thanks. That should not happen on 1.6.0.181: when a host PXE boots and the master already has 10 tasks, the host should get a free node in the same group. I ran the same setup on my lab, 12 hosts with Max Clients 10, booted one at a time and all at once. Every time, the extra hosts moved to the free node.
When FOG looks for a free node, it skips a node without a message if any of these is true:
The node is not enabled, or its Max Clients is 0. The node is not in the location’s Storage Group. The main server cannot reach the node. FOG tests the node’s SSH port (22 unless you changed it) first, then port 443 (or 80 if you use http).Please check these for the Adamsville storage group:
In Storage Node Management, for each of the three nodes: Storage Group, Is Enabled, Is Master Node, Max Clients. In Location Management, for that location: Storage Group and Storage Node. On the main server, run this for each of the two other nodes (replace the IP): nc -zv -w 1 <node-ip> 22; nc -zv -w 1 <node-ip> 443; nc -zv -w 1 <node-ip> 80If all three fail for a node, FOG treats that node as offline, and that is why the hosts stayed in the queue.