yahoo-eng-team team mailing list archive

[Steve Martinelli <1590779@xxxxxxxxxxxxxxxxxx>]

So, I'm not sure we can do anything about this in Mitaka.

Correct me if I'm wrong:

In Master/Newton this is solved in keystone via oslo.cache (we use
dogpile >0.6.2)

In Mitaka the problem exists, and should be fixed in oslo.cache
(https://review.openstack.org/354831). But I think would break stable
policy since it's a fairly large change. I'm not sure, regardless this
does not impact keystone itself.

In Liberty this won't go in since it's not a security or critical fix.


** Changed in: keystone
       Status: In Progress => Invalid

** Changed in: keystone
    Milestone: newton-3 => None

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

** Changed in: keystone
     Assignee: Boris Bobrov (bbobrov) => (unassigned)

-- 
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/1590779

Title:
  Cache region invalidation works for local CacheRegion object only

Status in OpenStack Identity (keystone):
  Invalid
Status in oslo.cache:
  In Progress

Bug description:
  oslo_cache uses dogpile.cache's CacheRegion
  which invalidates by setting region object attributes:
  - self._hard_invalidated
  - self._soft_invalidated
  Then it checks these attributes on value get.
  So this invalidation works for particular region object only.

  If there is a need to invalidate a region so that values in it are no
  more valid for other instances of CacheRegion (either in the same
  process or in another one) - it's simply impossible.

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