Bug 1246560 - Location of token persistence backends has changed in Kilo
Summary: Location of token persistence backends has changed in Kilo
Keywords:
Status: CLOSED CANTFIX
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: openstack-keystone
Version: 7.0 (Kilo)
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: 8.0 (Liberty)
Assignee: Jamie Lennox
QA Contact: yeylon@redhat.com
URL:
Whiteboard:
Depends On:
Blocks: 1243965 track-osp6-osp7
TreeView+ depends on / blocked
 
Reported: 2015-07-24 14:58 UTC by Lars Kellogg-Stedman
Modified: 2016-04-26 13:55 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-08-04 18:59:04 UTC
Target Upstream Version:
Embargoed:
lars: needinfo-


Attachments (Terms of Use)

Description Lars Kellogg-Stedman 2015-07-24 14:58:13 UTC
Description of problem:

After upgrading from OSP6 to OSP7, running Keystone will fail with:

  2015-07-24 10:36:03.358 2231 TRACE keystone ImportError: No module named backends.sql

Version-Release number of selected component (if applicable):

  python-keystone-2015.1.0-4.el7ost.noarch

This happens because the location of the token persistence backends has changed, as documented in:

  https://wiki.openstack.org/wiki/ReleaseNotes/Kilo#Upgrade_Notes_5

Should we be handling this automatically as part of the package ugprade?

Comment 3 Alan Pevec 2015-08-04 18:59:04 UTC
RPM by design does not touch configuration, it will save new config files as .rpmnew

Marking as can't fix in openstack-keystone RPM, please move to upgrade tool/script or documentation.


Note You need to log in before you can comment on or make changes to this bug.