Hide Forgot
Description of problem: Some Swift middleware, which is required by Tempest to run successfully, is not configured by default. Some tests were failing until I added these: account_quotas container_quotas tempurl staticweb In /etc/swift/proxy-server.conf, this is the default after the packstack installation: [pipeline:main] pipeline = healthcheck cache authtoken keystone proxy-server Since I've seen some effort to prepare the deployment for Tempest, I think they should be included. Version-Release number of selected component (if applicable): openstack-packstack-2013.2.1-0.6.dev763.el6ost.noarch openstack-swift-container-1.10.0-0.2.rc1.el6ost.noarch openstack-swift-account-1.10.0-0.2.rc1.el6ost.noarch openstack-swift-object-1.10.0-0.2.rc1.el6ost.noarch openstack-swift-proxy-1.10.0-0.2.rc1.el6ost.noarch openstack-swift-1.10.0-0.2.rc1.el6ost.noarch openstack-swift-plugin-swift3-1.0.0-0.20120711git.1.el6ost.noarch How reproducible: always Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
Created attachment 815955 [details] /etc/swift/proxy-server.conf
Merged. Moving to MODIFIED.
Auto adding >= MODIFIED bugs to beta
Reverted 56798.
Tempest friendly minimal havana pipeline is: catch_errors healthcheck cache authtoken keystone tempurl staticweb container_quotas account_quotas proxy-server Tempest friendly minimal icehouse pipeline will be: catch_errors healthcheck cache container_sync crossdomain slo bulk authtoken keystone tempurl formpost staticweb container_quotas account_quotas proxy-server AFAIK the new swift with 'container_sync' support is not packaged yet, it can be excluded until it is ready. NOTE: For my looks strange the keystoneauth is called as 'keystone', would be simpler to read/write the config file if it would be 'keystoneaouth'. NOTE: devstack uses the following pipeline: catch_errors gatekeeper healthcheck proxy-logging cache container_sync bulk slo ratelimit crossdomain authtoken keystoneauth tempauth tempurl formpost staticweb container-quotas account-quotas proxy-logging ceilometer proxy-server
container_sync crossdomain and proxy-server are not yet available on the swift-puppet module. adding the options that are currently available.
Had to do quickfixes: https://review.openstack.org/#/c/82021/ https://review.openstack.org/#/c/82029/
Those fixes made Swift installable, but unfortunately broke solution of this bug.
Swift will get enabled again by default, I created patch that enables all middlewares for icehouse except for container_sync and crossdomain. These two will probably require patching puppet-swift. I'll start working on it right away.
The "bulk catch_errors healthcheck cache ratelimit authtoken keystone staticweb tempurl slo formpost account-quotas container-quotas proxy-server" pipeline is wrong. The catch_errors MUST be the FIRST in the pipeline ! See also: https://bugzilla.redhat.com/show_bug.cgi?id=1051113 BTW: the current default devstack pipeline is: pipeline = catch_errors gatekeeper healthcheck proxy-logging cache container_sync bulk tempurl slo dlo ratelimit crossdomain authtoken keystoneauth tempauth formpost staticweb container-quotas account-quotas proxy-logging proxy-server 'dlo' is new.
Setting correct bug status since this is RHOS-4 bug.
According to discussion with Attila, I'm re-targeting this bug to RHO-5.
the requested have been added to the /etc/swift/proxy-server.conf: pipeline = catch_errors bulk healthcheck cache crossdomain ratelimit authtoken keystone staticweb tempurl slo formpost account_quotas container_quotas proxy-server moving to verified on: [root@tigris01 ~]# rpm -qa |grep swift openstack-swift-object-1.13.1-3.el7ost.noarch python-swiftclient-2.1.0-2.el7ost.noarch openstack-swift-1.13.1-3.el7ost.noarch openstack-swift-plugin-swift3-1.7-3.el7ost.noarch openstack-swift-account-1.13.1-3.el7ost.noarch openstack-swift-proxy-1.13.1-3.el7ost.noarch openstack-swift-container-1.13.1-3.el7ost.noarch [root@tigris01 ~]# rpm -qa |grep packstack openstack-packstack-2014.1.1-0.40.dev1239.el7ost.noarch openstack-packstack-puppet-2014.1.1-0.40.dev1239.el7ost.noarch [root@tigris01 ~]#
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. http://rhn.redhat.com/errata/RHBA-2014-1324.html