In rollback_after_enabling_majority_reads.js, we first verify that we fassert if we do a rollback immediately after upgrading enableMajorityReadConcern to true. Then, we restart the node and verify that it reaches SECONDARY state. However, after we verify that the node has fully restarted, it seems possible for the node to go into ROLLBACK (if, for instance, the source's last oplog entry was early than our first oplog entry). This would cause the verify command on the next line to fail.