[SERVER-14826] Upgrade to 2.6.3 appeared to remove admin user Created: 07/Aug/14 Updated: 24/Jan/15 Resolved: 23/Jan/15 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Usability |
| Affects Version/s: | 2.2.4, 2.6.3 |
| Fix Version/s: | None |
| Type: | Question | Priority: | Major - P3 |
| Reporter: | Phil Marshalsea | Assignee: | Unassigned |
| Resolution: | Incomplete | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Participants: |
| Description |
|
Hi Mongo, I upgraded mongo from 2.2 to 2.6 this afternoon and on completing the upgrade the applications failed to connect to mongo as the previous user and password was "not authorised". It appears the user in the admin collection was deleted by the upgrade. I realise thats a bit unlikely but I am looking for an explanation. The user must of been present in the 2.2 install as thats how the connection would of been authorised. Could it be part of taking down the replica set and the secondary becoming prime that caused the anomaly? We fixed the issue by adding the user back to the admin database but I would really appreciate an explanation and help diagnosing exactly what happened. Thanks Phil |
| Comments |
| Comment by Ramon Fernandez Marina [ 02/Sep/14 ] |
|
phil.marshalsea@haymarket.com, did you follow the upgrade procedure described here? As you can read in the "User Requirements", upgrading from 2.2 to 2.6 requires going through 2.4. If you went through 2.4, can you please send us the details of the procedure you used to determine if there are any bugs in the 2.4 -> 2.6 upgrade process? As explained in the instructions to update to 2.6, there were significant changes in the authorization model which may require additional upgrade steps. Those steps are not performed automatically when upgrading via yum though. |
| Comment by Phil Marshalsea [ 12/Aug/14 ] |
|
I started by replacing the binaries on the backup server first. Following the stop mongo (sudo service mongo stop) and dropping the binaries in. I was also executing a sudo yum upgrade on the linux box and noted that it was offering to upgrade mongo for me. So on the secondary I did the stop sudo yum update it all looked good, so executed on the primary (after stop) and everything looked good from the replica set side. As I mentioned this admin user was missing after the process. Whether it was a change in the user implementation in 2.6.3 or my upgrade process... |
| Comment by Ramon Fernandez Marina [ 08/Aug/14 ] |
|
phil.marshalsea@haymarketmedia.com, can you please post the details of your upgrade procedure? Did you use mongodump/mongorestore? Or just replaced the binaries? |