xenial-pike/proposed - keystone unable to load token provider

Bug #1722909 reported by James Page
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack Keystone Charm
Fix Released
High
James Page

Bug Description

I hit this issue whilst testing some updates for xenial-pike today:

2017-10-11 18:16:50.106231 mod_wsgi (pid=10696): Exception occurred processing WSGI script '/usr/bin/keystone-wsgi-public'.
2017-10-11 18:16:50.106249 Traceback (most recent call last):
2017-10-11 18:16:50.106261 File "/usr/bin/keystone-wsgi-public", line 51, in <module>
2017-10-11 18:16:50.106275 application = initialize_public_application()
2017-10-11 18:16:50.106291 File "/usr/lib/python2.7/dist-packages/keystone/server/wsgi.py", line 134, in initialize_public_application
2017-10-11 18:16:50.106301 config_files=_get_config_files())
2017-10-11 18:16:50.106306 File "/usr/lib/python2.7/dist-packages/keystone/server/wsgi.py", line 66, in initialize_application
2017-10-11 18:16:50.106313 startup_application_fn=loadapp)
2017-10-11 18:16:50.106318 File "/usr/lib/python2.7/dist-packages/keystone/server/common.py", line 47, in setup_backends
2017-10-11 18:16:50.106325 drivers = backends.load_backends()
2017-10-11 18:16:50.106329 File "/usr/lib/python2.7/dist-packages/keystone/server/backends.py", line 61, in load_backends
2017-10-11 18:16:50.106336 token_provider_api=token.provider.Manager())
2017-10-11 18:16:50.106340 File "/usr/lib/python2.7/dist-packages/keystone/common/dependency.py", line 96, in __wrapped_init__
2017-10-11 18:16:50.106347 init(self, *args, **kwargs)
2017-10-11 18:16:50.106351 File "/usr/lib/python2.7/dist-packages/keystone/common/dependency.py", line 155, in wrapper
2017-10-11 18:16:50.106358 self.__wrapped_init__(*args, **kwargs)
2017-10-11 18:16:50.106362 File "/usr/lib/python2.7/dist-packages/keystone/token/provider.py", line 73, in __init__
2017-10-11 18:16:50.106519 super(Manager, self).__init__(CONF.token.provider)
2017-10-11 18:16:50.106533 File "/usr/lib/python2.7/dist-packages/keystone/common/manager.py", line 169, in __init__
2017-10-11 18:16:50.106589 self.driver = load_driver(self.driver_namespace, driver_name)
2017-10-11 18:16:50.106596 File "/usr/lib/python2.7/dist-packages/keystone/common/manager.py", line 75, in load_driver
2017-10-11 18:16:50.106609 raise ImportError(msg, {'name': driver_name, 'namespace': namespace})
2017-10-11 18:16:50.106634 ImportError: (u'Unable to find %(name)r driver in %(namespace)r.', {'namespace': 'keystone.token.provider', 'name': 'keystone.token.providers.uuid.Provider'})

Switching the keystone.conf to use the 'uuid' entry point resolves this issue, but I'm bemused as to why this has started happening (as I already had an environment deployed on pike prior to redeployment)

Tags: test-gap uosci
Revision history for this message
James Page (james-page) wrote :
Changed in charm-keystone:
status: New → In Progress
importance: Undecided → High
assignee: nobody → James Page (james-page)
milestone: none → 17.11
Ryan Beisner (1chb1n)
tags: added: uosci
tags: added: test-gap
Revision history for this message
Ryan Beisner (1chb1n) wrote :

FYI

Issue was introduced with commit: https://github.com/openstack/charm-keystone/commit/23599501797f795681617a43f23d6aad67c5e011

Where before that, the value was 'uuid' based on template inheritance from mitaka.

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to charm-keystone (master)

Reviewed: https://review.openstack.org/511333
Committed: https://git.openstack.org/cgit/openstack/charm-keystone/commit/?id=9515a78cf00cc2e64f4780044a0dbbaead94cd53
Submitter: Jenkins
Branch: master

commit 9515a78cf00cc2e64f4780044a0dbbaead94cd53
Author: James Page <email address hidden>
Date: Wed Oct 11 16:44:30 2017 -0400

    Use compatible uuid entry point for tokens backend

    Ensure that a valid entry point is used for the uuid token
    backend, resolving compatibility with later OpenStack releases.

    Change-Id: I566e6a2e9c0aa1fc1afe02dbc9f899cfb0c7a9f6
    Closes-Bug: 1722909

Changed in charm-keystone:
status: In Progress → Fix Committed
James Page (james-page)
Changed in charm-keystone:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.