Details
-
Bug
-
Status: Patch Available
-
Major
-
Resolution: Unresolved
-
2.9.2, 3.0.3, 2.8.5
-
None
-
None
-
None
Description
The RM state machine decides to put new or running nodes in inactive state only past the point of either registration or being in the exclude list. This does not cover the case where a node is the in the include list but never registers and since all state changes are based on these NodeState transitions, having NEW nodes be listed as inactive first may help. This would change the semantics of how inactiveNodes are looked at today. Another state addition might help this case too.