The native_tenant_data_isolation_curr_op.js test is failing when command serialization/deserialization plumbed in.  It's possible the SerializationContext objects being passed in are configured incorrectly when CurOp::reportState() (which should be serializing command replies) is being called, so we may need to look at the call stack and see which callers are generating the SerializationContext objects.