Description of problem: The request returned that the resource could not be found while trying to create a container on a known volume/account. The issue is that the volume was not mounted by swift thus causing the error. Once the volume was mounted manually, the request was able to create a container in the specified volume/account.
Output of curl commands: [pportant@gprfc019 Catalyst]$ curl -sS --connect-timeout 1 --write-out "%{http_code} %{time_total} %{url_effective}\n" -X PUT http://gprfs011:8080/v1/AUTH_test1/newcont <html> <head> <title>404 Not Found</title> </head> <body> <h1>404 Not Found</h1> The resource could not be found.<br /><br /> </body> </html>404 0.474 http://gprfs011:8080/v1/AUTH_test1/newcont [pportant@gprfc019 Catalyst]$ curl -sS --connect-timeout 1 --write-out "%{http_code} %{time_total} %{url_effective}\n" -X PUT http://gprfs011:8080/v1/AUTH_test1/newcont <html> <head> <title>404 Not Found</title> </head> <body> <h1>404 Not Found</h1> The resource could not be found.<br /><br /> </body> </html>404 0.123 http://gprfs011:8080/v1/AUTH_test1/newcont [pportant@gprfc019 Catalyst]$ curl -sS --connect-timeout 1 --write-out "%{http_code} %{time_total} %{url_effective}\n" -X PUT http://gprfs011:8080/v1/AUTH_catalyst/newcont <html> <head> <title>404 Not Found</title> </head> <body> <h1>404 Not Found</h1> The resource could not be found.<br /><br /> </body> </html>404 0.119 http://gprfs011:8080/v1/AUTH_catalyst/newcont *** At this point we did the following on the server: * Create the directory with the same name as the volume under the mount point directory defined in /etc/swift/fs.conf * Mount the glusterfs volume at the location of the directory [pportant@gprfc019 Catalyst]$ curl -sS --connect-timeout 1 --write-out "%{http_code} %{time_total} %{url_effective}\n" -X PUT http://gprfs011:8080/v1/AUTH_catalyst/newcont 201 Created 201 0.054 http://gprfs011:8080/v1/AUTH_catalyst/newcont
Created attachment 750708 [details] /var/log/messages
Gluster for swift will not support automount of Gluster volumes.