From the ticket...

2018-05-20T02:23:02 - [fts_base:883] INFO - Creating fulltext-index sasl_bucket_1_index_1 on 172.23.98.164

In [4]:
!/Users/steveyen/dev/scratch/logmerge/logmerge.py --out=out.log --near=2018-05-20T02:23:02 cbcollect_info_ns_1@172.23.98.164_20180520-092507/

100% (34599536 of 34599536) |#############| Elapsed Time: 0:00:01 ETA:  00:00:00
done

Here we see fts creates the index definition...

ns_server.fts.log 2018-05-20T02:23:02.533-07:00 [INFO] manager_api: index definition created, indexType: fulltext-index, indexName: sasl_bucket_1_index_1, indexUUID: e78e18b5aa2e3707

And then fts is updating the lead plan...

ns_server.fts.log 2018-05-20T02:23:02.553-07:00 [INFO] cfg_metakv_lean: setLeanPlan, val: {"uuid":"16b31bd5f75b2e07","planPIndexes":{"sasl_bucket_1_index_1_e78e18b5aa2e3707_13aa53f3":{"name":"sasl_bucket_1_index_1_e78e18b5aa2e3707_13aa53f3","uuid":"7b3a02225f407100","indexType":"fulltext-index","indexName":"sasl_bucket_1_index_1","indexUUID":"e78e18b5aa2e3707","sourceType":"couchbase","sourceName":"sasl_bucket_1","sourcePartitions":"0,1,2,3,4,5,6,7,8,9,10,11,12,13,14,15,16,17,18,19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42,43,44,45,46,47,48,49,50,51,52,53,54,55,56,57,58,59

But here we see the pindexes aren't being added...

ns_server.fts.log 2018-05-20T02:23:02.586-07:00 [INFO] janitor: pindexes to add: 0
ns_server.fts.log 2018-05-20T02:23:02.586-07:00 [INFO] janitor: pindexes to restart: 0