Bug: REST API is not responding with all username targets

[annatorok]

The REST API endpoints /username/resolve/:starname and /username/owner/:owner only return the iov-mainnet target even when other targets exist. All targets should be returned. (The bnsd v1.0.0 version of the REST API does not suffer from this bug; see the kraken*dave account at http://exchangenet-bnsapi.iov.one:8000/account/accounts?domainKey=dave.)

• http://bnsapi.iov.one:8000/username/resolve/dave*iov must return targets for ETH, LISK, and IOV

[orkunkl]

We delved into the issue with @davepuchyr. Evidently, the bug does not exist. There was a misunderstanding. Here is the explanation by Dave:

Ah, ok, I guess I got really confused because bnscli query -path /usernames/owner -data 04C3DB7CCCACF58EEFCC296FF7AD0F6DB7C2FA17 is not displaying all the targets that I see in Neuma in production. 
 Evidently it's because the ETH and LISK addresses are associated with the private key in Neuma but haven't been published to the chain because dave*iov is in the genesis file (with only the one target).  
When I do the same query against dancenet I do see three targets.  That's because I created dave*iov on dancenet with Neuma and it did push the targets to the chain on creation.

Long story short, We don't have a bug