Comment 31 for bug 1537585

Alrighty then...

The problem boils down the setting of the machine addresses. This passes the state.address type into the insert for the preferredpublicaddress and preferredprivateaddress.

At some stage between the Update, and when the transaction is finished, the ordering of the bson.D structure is different. This makes the assertions in the following calls to set the preferred addresses to fail.

Investigation continues as to why the ordering changes. Theoretically, mongo should guarantee order here.