Description of problem:
Packstack adds the S3 service to the endpoints, yet doesn't seem to actually configure it - the swift3 middleware that should provide it isn't in the Swift proxy server pipeline. The openstack-nova-objectstorage isn't installed either.

This has been a long-standing issue (you could probably reproduce it on anything from Havana to Icehouse), which was worked around in our test preparation, thus I didn't notice it. It's also possible the same problem is present in Staypuft, since they use the same puppet modules.


Version-Release number of selected component (if applicable):
Last time I tried it with RDO-Icehouse on Fedora 20.
openstack-packstack-2014.1.1-0.25.dev1208.fc21.noarch
openstack-packstack-puppet-2014.1.1-0.25.dev1208.fc21.noarch

How reproducible:
100%

Steps to Reproduce:
1. keystone endpoint-get --service s3
+--------------+-------------------------+
|   Property   |          Value          |
+--------------+-------------------------+
| s3.publicURL | http://172.16.40.8:8080 |
+--------------+-------------------------+
2. in tempest/etc/tempest.conf, set "[boto] s3_url = http://172.16.40.8:8080"
3. run tempest S3 tests

Actual results:
Fails with:
Traceback (most recent call last):
  File "tempest/thirdparty/boto/test_s3_objects.py", line 38, in test_create_get_delete_object
    bucket = self.client.create_bucket(bucket_name)
  File "tempest/services/botoclients.py", line 79, in func
    return getattr(conn, name)(*args, **kwargs)
  File "/usr/lib/python2.7/dist-packages/boto/s3/connection.py", line 504, in create_bucket
    response.status, response.reason, body)
S3ResponseError: S3ResponseError: 412 Precondition Failed
None

Expected results:
test passed...

Additional info:
Alternatively, you can verify S3 functionality by creating the access and secret key with "keystone ec2-credentials-create" and try to create a bucket with the boto client. See http://ceph.com/docs/master/radosgw/s3/python/


The bug can be worked around by installing openstack-nova-objectstore, starting the service and modifying the keystone endpoint to use port 3333.