upgrade of swift 1.4.8 to 1.7.1 problems
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 - http://
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.
Traceback (most recent call last):
File "/usr/bin/
run_
File "/usr/lib/
loadapp(
File "/usr/lib/
return loadobj(APP, uri, name=name, **kw)
File "/usr/lib/
global_
File "/usr/lib/
global_
File "/usr/lib/
return loader.
File "/usr/lib/
global_
File "/usr/lib/
for name in pipeline[:-1]]
File "/usr/lib/
object_type, name=name)
File "/usr/lib/
self.filename))
LookupError: No section 'swift3' (prefixed by 'filter') found in config /etc/swift/
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:proxy-server]
use = egg:swift#proxy
account_autocreate = true
allow_account_
#object_chunk_size = 8192
#client_chunk_size = 8192
max_containers_
node_timeout = 15
client_timeout = 600
#[filter:swift3]
#use = egg:swift#swift3
[filter:keystone]
paste.filter_
operator_roles = admin, swiftoperator, Admin, SwiftOperator
[filter:authtoken]
paste.filter_
# Delaying the auth decision is required to support token-less
# usage for anonymous referrers ('.r:*') or for tempurl/formpost
# middleware.
delay_auth_decision = 1
service_protocol = http
service_port = 8888
service_host = 192.168.5.109
auth_protocol = http
auth_port = 35357
auth_host = 172.28.137.65
auth_token = kstoken1
admin_token = kstoken1
signing_dir = /var/cache/swift
[filter:cache]
use = egg:swift#memcache
set log_name = cache
memcache_servers = 192.168.5.109:11211
[filter:
use = egg:swift#
[filter:
use = egg:swift#
# You can override the default log routing for this filter here:
set log_name = healthcheck
set log_facility = LOG_LOCAL0
set log_level = DEBUG
set log_headers = TRUE
It looks like the configuration to enable S3 access has changed. If you remove the 'swift3' from the pipeline:main section, the proxy service starts as normal
So my question is , how can i re-enable S3 access to swift once I have upgraded to version 1.7.4 ?
any advice or guidance is appreciated
Question information
- Language:
- English Edit question
- Status:
- Solved
- Assignee:
- No assignee Edit question
- Solved by:
- Samuel Merritt
- Solved:
- Last query:
- Last reply: