This is normal (if your attempt is 0, 1, 2) when your config version changes on the shard - the query will initially fail, then be retried with a refreshed version. You may see this happen repeatedly in clusters as all connections refresh their config data. This warning shouldn't propagate back to your app, however.

You can issue a db.adminCommand("flushRouterConfig") which should get rid of these messages.