Flushing cache when schema changes occur to avoid drift between
what might be cached and what keystone queries expect.
Given that this is a workaround which is only usually required
in major upgrades (and should really be handled in process by
keystone itself), we make the execution optional so that it can
be set to happen only on major upgrades.
To prevent test breakage as happened in master, we combine the
two master patches into one for the backport:
Reviewed: https:/ /review. openstack. org/613321 /git.openstack. org/cgit/ openstack/ openstack- ansible- os_keystone/ commit/ ?id=ce0df5355f8 37dc406e0a94e6f cc6e4c8f1b37e0
Committed: https:/
Submitter: Zuul
Branch: stable/rocky
commit ce0df5355f837dc 406e0a94e6fcc6e 4c8f1b37e0
Author: rexredinger <email address hidden>
Date: Thu Oct 4 15:38:01 2018 -0400
Add memcache flushing handler on db migrations
Flushing cache when schema changes occur to avoid drift between
what might be cached and what keystone queries expect.
Given that this is a workaround which is only usually required
in major upgrades (and should really be handled in process by
keystone itself), we make the execution optional so that it can
be set to happen only on major upgrades.
To prevent test breakage as happened in master, we combine the
two master patches into one for the backport:
https:/ /review. openstack. org/608066 /review. openstack. org/613256
https:/
Depends-On: https:/ /review. openstack. org/613290 446a14dc8228fa0 05f12fcc840
Change-Id: Ibf8f3dd60d6f3c
Closes-Bug: 1793389