The use of keystone caching on subclouds causes problems because
the syncing of fernet keys to the subcloud results in stale
cache entries. This causes authentication failures until the
cache entries age out or new tokens are created.
Since the keystone load in a subcloud is light, there is really
no need for caching at this time - it is being disabled in
subclouds.
Reviewed: https:/ /review. opendev. org/708729 /git.openstack. org/cgit/ starlingx/ config/ commit/ ?id=f6eebbd318f 3c596c7d408696c e1558fd03a5497
Committed: https:/
Submitter: Zuul
Branch: master
commit f6eebbd318f3c59 6c7d408696ce155 8fd03a5497
Author: Bart Wensley <email address hidden>
Date: Wed Feb 19 12:56:21 2020 -0600
Disable keystone caching on subclouds
The use of keystone caching on subclouds causes problems because
the syncing of fernet keys to the subcloud results in stale
cache entries. This causes authentication failures until the
cache entries age out or new tokens are created.
Since the keystone load in a subcloud is light, there is really
no need for caching at this time - it is being disabled in
subclouds.
Change-Id: I777c57c46cf1bc d701fbbac73228a 2cb81d8424b
Closes-Bug: 1860372
Signed-off-by: Bart Wensley <email address hidden>