It currently fails with PooledConnectionsDropped when setFCV is run concurrently with movePrimary.

It seems like it's due to a race condition in between creating a connection between the donor and recipient shards and tagging the connection as kKeepOpen in the NetworkInterfaceTL (so that setFCV does not close the connection with the non-retryable error code PooledConnectionsDropped).

This ticket is to finish investigating the root cause and either unblacklist the workload or update the comment in the places where it is blacklisted.