yahoo-eng-team team mailing list archive

[Lance Bragstad <lbragstad@xxxxxxxxx>]

Public bug reported:

Keystone has a timeout configuration option for memcache [0]. Keystone's
definition of this option isn't actually used anywhere, so it appears to
be a broken knob.

In fact oslo.cache has a duplicate option that appears to be used
instead [1].

We should deprecate the keystone-specific option and point people to the
oslo.cache option.

[0] https://opendev.org/openstack/keystone/src/commit/a0aa21c237f7b42077fc945f157844deb77be5ef/keystone/conf/memcache.py#L26-L32
[1] https://opendev.org/openstack/oslo.cache/src/commit/a5023ba2754dd537c802d4a59290ff6378bd6285/oslo_cache/_opts.py#L85-L89

** Affects: keystone
     Importance: Undecided
         Status: New


** Tags: configuration low-hanging-fruit

** Tags added: configuration low-hanging-fruit

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

Title:
  keystone's keystone.conf.memcache socket_timeout isn't actually used

Status in OpenStack Identity (keystone):
  New

Bug description:
  Keystone has a timeout configuration option for memcache [0].
  Keystone's definition of this option isn't actually used anywhere, so
  it appears to be a broken knob.

  In fact oslo.cache has a duplicate option that appears to be used
  instead [1].

  We should deprecate the keystone-specific option and point people to
  the oslo.cache option.

  [0] https://opendev.org/openstack/keystone/src/commit/a0aa21c237f7b42077fc945f157844deb77be5ef/keystone/conf/memcache.py#L26-L32
  [1] https://opendev.org/openstack/oslo.cache/src/commit/a5023ba2754dd537c802d4a59290ff6378bd6285/oslo_cache/_opts.py#L85-L89

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