yahoo-eng-team team mailing list archive

["jun923.gu" <gujun1989@xxxxxxx>]

Public bug reported:

I encounter a situation that keystone can't identify the updated user
information after updating ldap user. Because keystone use memcached
server as a cached backend, the get_user api get user information from
memcached server if the cached user information is not expired. The
updated ldap user can't be updated into memcached server, so the
get_user api get the origin user information, not updated user
information.I am curious whether there are some solutions to solve the
problem.

** Affects: keystone
     Importance: Undecided
         Status: New

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Identity (keystone).
https://bugs.launchpad.net/bugs/1845412

Title:
  Update ldap user information and it can't be identified by keystone

Status in OpenStack Identity (keystone):
  New

Bug description:
  I encounter a situation that keystone can't identify the updated user
  information after updating ldap user. Because keystone use memcached
  server as a cached backend, the get_user api get user information from
  memcached server if the cached user information is not expired. The
  updated ldap user can't be updated into memcached server, so the
  get_user api get the origin user information, not updated user
  information.I am curious whether there are some solutions to solve the
  problem.

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