Not sure if this is expected behavior but to reproduce, start a mixed version replica set with a 2.5.x primary and 2.4 secondar[y/ies]. After initiating the replica set, run the following on the primary.
db.addUser({user:"root",pwd:"root",roles:[{role:"root",db:"admin"}]})
or
db.createUser({user:"root",pwd:"root",roles:[{role:"root",db:"admin"}]})
in enterprise builds.
The 2.4 mongod(s) crash.
- is related to
-
SERVER-12158 Replica set blows up inelegantly when replicating authSchemaUpgradeStep changes to 2.4 secondary
- Closed
- related to
-
SERVER-11928 Cannot downgrade from 2.5.x to 2.4.8 if there are unapplied entries for new-style users in the oplog prior to downgrade.
- Closed