Comment 5 for bug 1306675

I set this to confirmed because it has been seen in one other Evergreen instance.

While I'd really like to find the ultimate cause*, a workaround will do.

We've loaded the above patch in our production system this morning. I tried it in development yesterday just to make sure it didn't blow up, which I didn't think it would.

Jason, if you or Bill could throw that in a branch, I'd be happy to sign off in a week or so if the errors don't come back. Alternatively, I could throw it in a branch and set the commit's author to Bill's name and email address.

* I suspect it is a failure of a module to completely initialize in some cases owing to a slightly hosed package somewhere. (Probably an upgrade hang over that debsums doesn't catch.) I've seen this reported with other projects, and the only effective fix seems to be to reinstall most everything.