get_user has different behavior for db and ldap drivers
Bug #744462 reported by
Devin Carlen
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Compute (nova) |
Fix Released
|
Medium
|
Vish Ishaya |
Bug Description
The db auth driver raises NotFound if a user lookup fails, while ldap auth driver returns None.
This inconsistency needs to be fixed, and causes problems further down the line and forces developers to awkwardly handle both scenarios.
Changed in nova: | |
assignee: | nobody → Joe Pawlak (jpawlak1) |
status: | Confirmed → In Progress |
Changed in nova: | |
status: | In Progress → Confirmed |
Changed in nova: | |
status: | Confirmed → In Progress |
assignee: | nobody → Andrew Clay Shafer (littleidea) |
Changed in nova: | |
assignee: | Andrew Clay Shafer (littleidea) → nobody |
Changed in nova: | |
assignee: | nobody → John Griffith (john-griffith) |
Changed in nova: | |
status: | Fix Committed → In Progress |
Changed in nova: | |
assignee: | John Griffith (john-griffith) → Vish Ishaya (vishvananda) |
Changed in nova: | |
milestone: | none → essex-4 |
status: | Fix Committed → Fix Released |
Changed in nova: | |
milestone: | essex-4 → 2012.1 |
To post a comment you must log in.
Looks like it's still a problem
e.g. LdapDriver. get_user( ) should raise UserNotFound if __get_ldap_user() returns None