Description of problem: packstack configures the swift proxy pipeline in way which fails on 3 tempest test: tempest.api.object_storage.test_object_formpost_negative.ObjectFormPostNegativeTest.test_post_object_using_form_expired[id-d3fb3c4d-e627-48ce-9379-a1631f21336d,negative] tempest.api.object_storage.test_object_formpost_negative.ObjectFormPostNegativeTest.test_post_object_using_form_invalid_signature[id-b277257f-113c-4499-b8d1-5fead79f7360] tempest.api.object_storage.test_object_formpost.ObjectFormPostTest.test_post_object_using_form[id-80fac02b-6e54-4f7b-be0d-a965b5cbef76] moving the frompost before the staticweb helps. Additional info: openstack-packstack-9.0.0-0.20160922140727.3f43120.1.el7ost.noarch openstack-packstack-puppet-9.0.0-0.20160922140727.3f43120.1.el7ost.noarch openstack-swift-object-2.10.1-0.20160929005314.3349016.el7ost.noarch python-swiftclient-3.1.0-1.el7ost.noarch openstack-swift-account-2.10.1-0.20160929005314.3349016.el7ost.noarch openstack-swift-container-2.10.1-0.20160929005314.3349016.el7ost.noarch python-swift-2.10.1-0.20160929005314.3349016.el7ost.noarch puppet-swift-9.4.0-1.el7ost.noarch openstack-swift-proxy-2.10.1-0.20160929005314.3349016.el7ost.noarch
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