Hide Forgot
Description of problem: Tempest by default expect the swift service is able to handle multiple versions of an object. It is enabled in the undercloud swift, but not enabled on the overcloud swift. The feature can be enabled/disabled via: /etc/swift/container-server.conf [app:container-server] allow_versions true This is very old feature, we do not have any real reason not to have it enabled by default. When the feature not enabled, the tempest-deployer-input.conf must have [object-storage-feature-enabled] object_versioning set to false. Please enable this feature by default, or at least tell to tempest the cloud is unable to support object versioning by will. Version-Release number of selected component (if applicable): puppet-swift-9.4.0-1.el7ost.noarch openstack-tripleo-0.0.1-0.20160916135259.4de13b3.el7ost.noarch openstack-tripleo-heat-templates-5.0.0-0.20160929150845.4cdc4fc.el7ost.noarch Actual results: /etc/swift/container-server.conf [app:container-server] allow_versions is false on the controller nodes. tempest-deployer-input.conf does not have [object-storage-feature-enabled] section. Expected results: /etc/swift/container-server.conf [app:container-server] allow_versions true tempest-deployer-input.conf [object-storage-feature-enabled] object_versioning has the same value as the above option. Additional info: tempest-deployer-input.conf created by the 'openstack overcloud deploy' .
Correct (merged) backport patch is https://review.openstack.org/#/c/385958/. Setting this bz to modified; patch is included in build puppet-tripleo-5.3.0-3.el7ost
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. https://rhn.redhat.com/errata/RHEA-2016-2948.html