mgo

RemoveUser of non-existent user has different behaviour with mongo 2.4/2.6

Bug #1340361 reported by Andrew Wilkins on 2014-07-10
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
mgo
Undecided
Unassigned

Bug Description

Whether this is something you want to handle in mgo is debatable, but I thought I'd bring up the issue in case you weren't aware.

With mongo 2.4.x, RemoveUser returns ErrNotFound if attempting to remove a non-existent user. With mongo 2.6.x (2.6.3 at least) returns a QueryError. It would be nice if mgo normalised the behaviour, but I can also see the argument for having mgo return exactly what mongo returns.

Revision history for this message
Gustavo Niemeyer (niemeyer) wrote :

The upcoming release does a lot to normalize the behavior of the several user-handling functions, which changed due to the way MongoDB 2.6 handles user modifications via commands rather than via straight database modifications.

Please let me know if you have any issues with it once it's out.

Changed in mgo:
status: New → Fix Committed
Changed in mgo:
status: Fix Committed → Fix Released
Revision history for this message
Andrew Wilkins (axwalk) wrote :

Thanks! I'll get onto updating Juju to the latest release soon.

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers