Hi stackers,
Facing some issue running tempest with ceph radosgw as the swift
endpoint.
I enabled radosgw as part of a test-only patch which configures it as the
swift endpoint, the CI fails since tempest's verify-tempest-config fails
Console logs are at [1], tempest logs @ [2]
The actual failure is due to the list_extensions call being done @ [4]
Long story short,
verify-tempest-configs checks for API extensions of different
services,
incl. swift, which calls the swift endpoints /info API which fails
with
Unexpected Content Type error. IIUC radosgw still doesn't support
/info
API, which calls for skipping the list_extensions check for swift when
radosgw is being used.
I wanted to check with the experts here on whether its a good idea to
skip calling list_extensions() (see [4]) by setting
CONF.object_storage_feature_enabled.discoverability to False, as
part of
radosgw setup in the devstack-ceph-plugin code ? Something similar to
whats being done in [3] already
Thoughts ?
thanx,
deepak
[1]:
http://logs.openstack.org/04/260904/6/check/gate-tempest-dsvm-full-devstack-plugin-ceph/12cfb27/logs/devstacklog.txt.gz
[2]:
http://logs.openstack.org/04/260904/6/check/gate-tempest-dsvm-full-devstack-plugin-ceph/12cfb27/logs/tempest.txt.gz#_2016-01-04_14_24_32_094
[3]:
https://github.com/openstack/tempest/blob/master/tempest/api/object_storage/test_account_services.py#L123-L126
[4]:
https://github.com/openstack/tempest/blob/master/tempest/cmd/verify_tempest_config.py#L177
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20160105/a0c0335d/attachment.html>