I think this is a separate bug from #1671489 but caused by similar issues. I believe that error is actually from MongoDB and it happens that our representation of objects in the database is different during upgrade (which would be bad, but is still possible).
I think this is a separate bug from #1671489 but caused by similar issues. I believe that error is actually from MongoDB and it happens that our representation of objects in the database is different during upgrade (which would be bad, but is still possible).