seq_id set to 0 under some scenarios

scenarios which this might occur ( needs confirmation from engineering

1- user upgraded from 1.8.x to 2.0.0 using offline upgrade ( cbupgrade )
2- user has backed up data from 1.8.x or 2.0 customer and restored data to a 2.0 cluster
3- user backing up data from a 2.0 cluster where data was restored from 1.8
4- user has performed an online upgrade from 1.8.x to 2.x upgrade
5- user has only 2.0 nodes and seq_id is set to 0 and if a node is failed over some items will have seq id set to 0 ( MB-7532 already merged )