Ask Your Question

upgrade of swift 1.4.8 to 1.7.1 problems

asked 2012-10-19 13:12:39 -0500

dafridgie gravatar image

I am creating a multi server installation of swift. This comprises of 1 proxy server + 5 storage nodes. My use cases are exposure of native swift as well as S3 for multiple users/tenants. All storage nodes reside on their own isolated network. I have built out the platform on for Ubuntu 12.04 using the standard repo packages. I then built out a Folsom openstack platform succesfully on 12.04 using the ubuntu cloud repo additional repo as outlined here - (

so far so good I then wanted to attach my exisitng 1.4.8 swift platform to connect and test with Folsom which seemed to work fine. I then took the step of upgrading the swift nodes to the Folsom release of swift by adding the repo as above, apt-get update and then apt-get upgrade. I started on the storage nodes 1 at a time, then the proxy server last.

Issues encountered when upgrading the storage nodes - The python-swiftclient was not instaleld as part of the upgrade and as a result serveral object and container services failed to start. an install of python-swiftclient resolved these problems and the sotrage nodes upgraded successfully

so far so good.....

I then did the same process on the proxy server and once the upgrade was completed, i found that the proxy service would fail to start - see error here -

swift-init proxy-server reload Signal proxy-server pid: 1760 signal: 1 proxy-server (1760) appears to have stopped Starting proxy-server...(/etc/swift/proxy-server.conf) Traceback (most recent call last): File "/usr/bin/swift-proxy-server", line 22, in <module> run_wsgi(conf_file, 'proxy-server', default_port=8080, *options) File "/usr/lib/python2.7/dist-packages/swift/common/", line 138, in run_wsgi loadapp('config:%s' % conf_file, global_conf={'log_name': log_name}) File "/usr/lib/python2.7/dist-packages/paste/deploy/", line 247, in loadapp return loadobj(APP, uri, name=name, *kw) File "/usr/lib/python2.7/dist-packages/paste/deploy/", line 271, in loadobj global_conf=global_conf) File "/usr/lib/python2.7/dist-packages/paste/deploy/", line 296, in loadcontext global_conf=global_conf) File "/usr/lib/python2.7/dist-packages/paste/deploy/", line 320, in _loadconfig return loader.get_context(object_type, name, global_conf) File "/usr/lib/python2.7/dist-packages/paste/deploy/", line 450, in get_context global_additions=global_additions) File "/usr/lib/python2.7/dist-packages/paste/deploy/", line 562, in _pipeline_app_context for name in pipeline[:-1]] File "/usr/lib/python2.7/dist-packages/paste/deploy/", line 408, in get_context object_type, name=name) File "/usr/lib/python2.7/dist-packages/paste/deploy/", line 587, in find_config_section self.filename)) LookupError: No section 'swift3' (prefixed by 'filter') found in config /etc/swift/proxy-server.conf

this is my existing proxy-server.conf file

[DEFAULT] bind_port = 8888 user = swift log_name = swift_proxy_log log_level = DEBUG log_headers = True

cert_file = /etc/swift/cert.crt

key_file = /etc/swift/cert.key

workers = 8

[pipeline:main] pipeline = catch_errors healthcheck cache swift3 authtoken keystone proxy-server

[app ... (more)

edit retag flag offensive close merge delete

4 answers

Sort by ยป oldest newest most voted

answered 2012-11-08 03:54:33 -0500

if this is correct, can someone please update the official docco's @ (

edit flag offensive delete link more

answered 2012-10-19 14:16:59 -0500

torgomatic gravatar image

The swift3 middleware now lives outside of Swift itself. You can find it on Github here:

It was pulled out due to an OpenStack policy change regarding third-party APIs, namely that they don't belong in the core projects. Summary here:

edit flag offensive delete link more

answered 2012-10-19 15:18:34 -0500

dafridgie gravatar image

Thanks for the info and super quick response Samuel! As a result of your answer, I've found that for Folsom on Ubuntu 12.04 you need to install the middleware as follows: apt-get install swift-plugin-s3 I've not tested functionality as yet, but the proxy service now starts with swift3 defined without errors

thanks again

Steve A

edit flag offensive delete link more

answered 2012-10-19 15:18:54 -0500

dafridgie gravatar image

Thanks Samuel Merritt, that solved my question.

edit flag offensive delete link more

Get to know Ask OpenStack

Resources for moderators

Question Tools

1 follower


Asked: 2012-10-19 13:12:39 -0500

Seen: 84 times

Last updated: Nov 08 '12