@Test
    @Ignore // FIXME test has been implicitly disabled for ages, figure out and fix
    public void testPersistentFailureResetClusterStateNoGoodNodesNotMarkedDown() {
        // If reset detection works (within the few messages sent in test), we should not fail any requests in second half.

        // This is just as sad as the above. Even if the node got detected to be screwed, we'd still be in the setting above. We don't expect nodes
        // to get into this state however.

        runSimulation("First correctnode .*, wrongnode .*, downnode .*, worked .*, failed .* "
                    + "Last correctnode .*, wrongnode 91, downnode 0, worked 0, failed 100",
                      new PersistentFailureTestParameters().addBadNode(new BadNode(3, FailureType.RESET_CLUSTER_STATE_NO_GOOD_NODES)));
    }
Verify that a reset cluster state version doesn't keep sending requests to the wrong node.
We expect a few failures in first half. We should have detected the issue before second half, so there all should be fine.
documentapi/src/test/java/com/yahoo/documentapi/messagebus/protocol/test/storagepolicy/ContentPolicyTest.java