Ask Your Question
0

SWIFT 400 bad request path not found when POST ing

asked 2014-01-08 22:36:02 -0500

garrett-s-page gravatar image

This is the first time I've installed OpenStack. I have the swift proxy installed on the same node as the storage node, but different than the controller node which has keystone. The swift proxy starts and swift stat returns properly.

When I test creating a container using swift post mycontainer I get an error:

Container POST failed http://10.10.10.4:8888/v1/AUTH_612d73af0232bee1331313/mycontainer (http://10.10.10.4:8888/v1/AUTH_612d73...) Invalid Path /sdb1/90145/AUTH_612d73af0232bee1331313

I have /dev/sdb1 partitioned as xfs and mounted to /srv/node/sdb1 the path is writable for the swift user.

My ring for accounts/containers/objects are all setup the same way with a single node 10.10.10.4 on port 6002 with dev sdb1 same IP and port for the replication info.

Everything seems to line up so I'm not sure what to look at next.

edit retag flag offensive close merge delete

2 answers

Sort by ยป oldest newest most voted
2

answered 2014-01-09 00:08:48 -0500

torgomatic gravatar image

Your object server listens on 6000, container on 6001, and account on 6002.

Therefore, your object ring's devices should have port 6000, container 6001, and account 6002. Otherwise you wind up sending account, container, and object requests to whichever server managed to bind to the port first, and it rejects 2/3 of them.

edit flag offensive delete link more
0

answered 2014-01-10 20:38:16 -0500

garrett-s-page gravatar image

Thanks Samuel Merritt, that solved my question.

edit flag offensive delete link more

Your Answer

Please start posting anonymously - your entry will be published after you log in or create a new account.

Add Answer

Get to know Ask OpenStack

Resources for moderators

Question Tools

1 follower

Stats

Asked: 2014-01-08 22:36:02 -0500

Seen: 592 times

Last updated: Jan 10 '14