Wrong s3_token filter configuration for swift-proxy for Juno

Bug #1384149 reported by Aleksandr Didenko
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
puppet-swift
Fix Released
Undecided
Aleksandr Didenko

Bug Description

I'm getting the following error when starting swift-proxy on Ubuntu deployed with puppet-swfit module v 4.1.0 (Juno packages)

Starting proxy-server...(/etc/swift/proxy-server.conf)
Traceback (most recent call last):
  File "/usr/bin/swift-proxy-server", line 23, in <module>
    sys.exit(run_wsgi(conf_file, 'proxy-server', default_port=8080, **options))
  File "/usr/lib/python2.7/dist-packages/swift/common/wsgi.py", line 432, in run_wsgi
    loadapp(conf_path, global_conf=global_conf)
  File "/usr/lib/python2.7/dist-packages/swift/common/wsgi.py", line 352, in loadapp
    ctx = loadcontext(loadwsgi.APP, conf_file, global_conf=global_conf)
  File "/usr/lib/python2.7/dist-packages/swift/common/wsgi.py", line 336, in loadcontext
    global_conf=global_conf)
  File "/usr/lib/python2.7/dist-packages/paste/deploy/loadwsgi.py", line 296, in loadcontext
    global_conf=global_conf)
  File "/usr/lib/python2.7/dist-packages/paste/deploy/loadwsgi.py", line 320, in _loadconfig
    return loader.get_context(object_type, name, global_conf)
  File "/usr/lib/python2.7/dist-packages/swift/common/wsgi.py", line 61, in get_context
    object_type, name=name, global_conf=global_conf)
  File "/usr/lib/python2.7/dist-packages/paste/deploy/loadwsgi.py", line 450, in get_context
    global_additions=global_additions)
  File "/usr/lib/python2.7/dist-packages/paste/deploy/loadwsgi.py", line 562, in _pipeline_app_context
    for name in pipeline[:-1]]
  File "/usr/lib/python2.7/dist-packages/swift/common/wsgi.py", line 61, in get_context
    object_type, name=name, global_conf=global_conf)
  File "/usr/lib/python2.7/dist-packages/paste/deploy/loadwsgi.py", line 458, in get_context
    section)
  File "/usr/lib/python2.7/dist-packages/paste/deploy/loadwsgi.py", line 517, in _context_from_explicit
    value = import_string(found_expr)
  File "/usr/lib/python2.7/dist-packages/paste/deploy/loadwsgi.py", line 22, in import_string
    return pkg_resources.EntryPoint.parse("x=" + s).load(False)
  File "/usr/lib/python2.7/dist-packages/pkg_resources.py", line 1989, in load
    entry = __import__(self.module_name, globals(),globals(), ['__name__'])
ImportError: No module named s3_token

A part of /etc/swift/proxy-server.conf config:

[filter:s3token]
paste.filter_factory = keystone.middleware.s3_token:filter_factory

It should be:

[filter:s3token]
paste.filter_factory = keystoneclient.middleware.s3_token:filter_factory

Because s3_token is a part of keystoneclient middleware since Juno:
https://github.com/openstack/python-keystoneclient/tree/master/keystoneclient/middleware

It should be fixed in this template:
https://github.com/stackforge/puppet-swift/blob/master/templates/proxy/s3token.conf.erb#L2

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to puppet-swift (master)

Fix proposed to branch: master
Review: https://review.openstack.org/130179

Changed in puppet-swift:
assignee: nobody → Aleksandr Didenko (adidenko)
status: New → In Progress
description: updated
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to puppet-swift (master)

Reviewed: https://review.openstack.org/130179
Committed: https://git.openstack.org/cgit/stackforge/puppet-swift/commit/?id=2dea09fed575d4133614ce86558a01c615518cc3
Submitter: Jenkins
Branch: master

commit 2dea09fed575d4133614ce86558a01c615518cc3
Author: Aleksandr Didenko <email address hidden>
Date: Wed Oct 22 12:51:56 2014 +0300

    Fix s3_token filter configuration for swift-proxy

    Since Juno s3_token middleware is a part of keystoneclient, not
    keystone.

    Change-Id: I97da480fcf5ce62da99c31481b181b8b61375db5
    Closes-bug: 1384149

Changed in puppet-swift:
status: In Progress → Fix Committed
Mathieu Gagné (mgagne)
Changed in puppet-swift:
milestone: none → 6.0.0
milestone: 6.0.0 → 5.0.0
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.