We had (and still have) the same issue.
The log suggests to drop the collection but mongodb’s documentation clearly states not to drop collections from the config database.
That’s why we opened a jira ticket but we were told to raise the issue here in this forum, which we did (link follows as I’m not allowed to post more than 2 links in 1 message).
How did you succeed to drop the collection? Which user privileges did you use?
Thanks!