The test has recently been flakey due to a node failing to change syncsource when requested to via the syncFrom comand. These failures are not failures of the behavior the test intends to check.

To reduce its flapping its timeout will be increased. Before 3.2 is released, whatever underlying syncsource problem is causing this failure will be fixed and the test ought to return to its original 30 second timeout.