Schedule indexes dropped in "Scheduled for Creation" state reappear if same Keyspace is created again

Steps to reproduce: - 

1. Create a cluster in 2 index nodes.
2. Add a bucket, scope and collection
3. Run -  

   curl -u Administrator:password -X POST  http://10.112.190.101:9102/settings -d '{"queryport.client.waitForScheduledIndex": true, "indexer.debug.enableBackgroundIndexCreation": false}'

4. Create few indexes (say 30) in parallel so that few indexes are in "scheduled for creation" state
5. Now drop collection/scope/ bucket and re-create the complete Keyspace. Indexes which were in scheduled state still showing in Index workbench but not in result for "system:indexes" query.