While working on SERVER-26671, I introduced an assertion which prevented the encryption logic from generating IVs while in readOnly mode. Because we do not perform writes while the readOnly flag is active, we should never generate IVs. I encountered a couple of failures which suggest that servers started with the recoverFromOplogAsStandalone setParameter enable readOnly mode, but then later do writes which hit the assertion.