Comment 1 for bug 2037740

This appears to be a simple disconnection of the controller from the MongoDB primary.

Was it an intermittent failure, as in the controller re-established its presence?

I'll triage as low, as it appears to be an intermittent failure due to the networking environment, and we're working to replace MongoDB. If it is appearing frequently, we can update the status.