yahoo-eng-team team mailing list archive

[Henry Nash <henryn@xxxxxxxxxxxxxxxxxx>]

Public bug reported:

When we recently split role management into its own backend api, there
are a few cases (e.g.  in test_backend_ldap.py) where we didn't fully
switch over to calling role_api directly.  For example:

        self.role_api.get_role.invalidate(self.assignment_api,
                                          self.role_member['id'])

....where we should really be passing self.role_api as opposed to
self.assignment_api in as a parameter.

** Affects: keystone
     Importance: Low
     Assignee: Henry Nash (henry-nash)
         Status: New

** Changed in: keystone
   Importance: Undecided => Low

** Changed in: keystone
     Assignee: (unassigned) => Henry Nash (henry-nash)

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Keystone.
https://bugs.launchpad.net/bugs/1414909

Title:
  In some tests, calls to role_api still go via assignment_api

Status in OpenStack Identity (Keystone):
  New

Bug description:
  When we recently split role management into its own backend api, there
  are a few cases (e.g.  in test_backend_ldap.py) where we didn't fully
  switch over to calling role_api directly.  For example:

          self.role_api.get_role.invalidate(self.assignment_api,
                                            self.role_member['id'])

  ....where we should really be passing self.role_api as opposed to
  self.assignment_api in as a parameter.

To manage notifications about this bug go to:
https://bugs.launchpad.net/keystone/+bug/1414909/+subscriptions