Comment 3 for bug 1434013
Revision history for this message
| Marcin Zbik (zbikmarc+launchpad) wrote | #3 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
0e1f616
(Get the code!)
@ Comment #1
this is about updating from 2.6 to 3.0 when that problem will not occure due to old users having MONGODB-CR hashes already existing in databse.
Bug is about totally new installation with Mongo 3.0
@ Comment #2
I will do this at morning (CET), dont have access to logs now. But there should be no logs so far. It is new installation, so it happens during init of database.