Description of problem: tempest.api.object_storage.test_object_version.ContainerTest.test_versioned_container fails because /etc/swift/container-server.conf is miss configured Version-Release number of selected component (if applicable): openstack-swift-plugin-swift3-1.9-1.el7ost.noarch openstack-swift-container-2.5.0-2.el7ost.noarch openstack-swift-account-2.5.0-2.el7ost.noarch openstack-swift-object-2.5.0-2.el7ost.noarch openstack-swift-2.5.0-2.el7ost.noarch openstack-swift-proxy-2.5.0-2.el7ost.noarch python-swiftclient-2.6.0-1.el7ost.noarch How reproducible: All the time Steps to Reproduce: 1. Install OSP-D 2. Run tempest Actual results: tempest.api.object_storage.test_object_version.ContainerTest.test_versioned_container fails Expected results: tempest.api.object_storage.test_object_version.ContainerTest.test_versioned_container pass Additional info: It's possible to fix it editing /etc/swift/container-server.conf setting allow_versions option to true and restarting the service: crudini --set /etc/swift/container-server.conf DEFAULT allow_versions true systemctl restart openstack-swift-container*
This bug did not make the OSP 8.0 release. It is being deferred to OSP 10.
Since 10 it does not fails, also the recommended configuration is different since 10.
Paul, this bug appears to be Storage related. Could you please have your guys check that the relative tempest test is now working as expected?
Will take a look, but also sounds like it's not an issue anymore based on #c4? Not sure there is a a reason to keep it open, but let's see if we want to make a default change or to expose an option. But this seems to be passing and it also had a work around.
This one does not affect OSP10 and later; the versioning architecture has been changed in Newton and no longer requires the setting in the container server. Closing this bug therefore; please re-open if this is still an issue.