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

Bug #1837407 reported by Lance Bragstad on 2019-07-22
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack Identity (keystone)
Chason Chan

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.


tags: added: configuration low-hanging-fruit
Colleen Murphy (krinkle) on 2019-07-22
Changed in keystone:
status: New → Triaged
importance: Undecided → Low
Chason Chan (chen-xing) on 2019-07-24
Changed in keystone:
assignee: nobody → Chason Chan (chen-xing)

Fix proposed to branch: master

Changed in keystone:
status: Triaged → In Progress

Submitter: Zuul
Branch: master

commit 4b747fa083ad09ae8ba92dadc63ac0b830c7e562
Author: chenxing <email address hidden>
Date: Thu Jul 25 13:53:21 2019 +0800

    Deprecate keystone.conf.memcache socket_timeout

    Change-Id: I5de14b5bd2d96c2f78152eda48842d388109e02b
    Partial-Bug: #1838037
    Closes-Bug: #1837407

Changed in keystone:
status: In Progress → Fix Released

This issue was fixed in the openstack/keystone release candidate.

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers