We have both ReplSetTest.waitForState and ReplSetTest.awaitSecondaryNodes that can be used wait for a node to become secondary. However, there's a subtle difference in reporting from the primary vs the actual node, so this behavior ends up becoming nuanced in practice. In this case, maybe we should error if a user tries to use waitForState as a means of waiting for the secondary state. The comment at the function signature says something to this effect, but we should start enforcing this behavior.