Description of problem:
Staticweb uses an absolute url in his redirect reposes,
which leads to failure in the tempest tests in an ssl setup.
The swift started to provide this option for solving the issue:
https://review.openstack.org/#/c/372809/2/etc/proxy-server.conf-sample
python-swiftclient-3.1.0-0.20160920234445.cbd71a8.el7ost.noarch
openstack-swift-object-2.10.1-0.20160929005314.3349016.el7ost.noarch
openstack-swift-proxy-2.10.1-0.20160929005314.3349016.el7ost.noarch
puppet-swift-9.4.0-1.el7ost.noarch
python-swift-2.10.1-0.20160929005314.3349016.el7ost.noarch
openstack-swift-account-2.10.1-0.20160929005314.3349016.el7ost.noarch
openstack-swift-container-2.10.1-0.20160929005314.3349016.el7ost.noarch
(.venv)[root@undercloud-0 tempest-dir]# rpm -qa |grep triple
openstack-tripleo-heat-templates-5.0.0-0.20161003064637.d636e3a.1.1.el7ost.noarch
openstack-tripleo-0.0.1-0.20160916135259.4de13b3.el7ost.noarch
python-tripleoclient-5.2.0-1.el7ost.noarch
openstack-tripleo-puppet-elements-5.0.0-0.20160929220627.200d011.el7ost.noarch
puppet-tripleo-5.2.0-1.el7ost.noarch
openstack-tripleo-common-5.2.1-0.20160930181658.40ad7e5.el7ost.noarch
openstack-tripleo-image-elements-5.0.0-0.20161002235922.14e1f41.el7ost.noarch
openstack-tripleo-ui-1.0.3-0.20160930145215.f7297c3.el7ost.noarch
The failing tempest tests are:
tempest.api.object_storage.test_container_staticweb.StaticWebTest.test_web_index [0.111226s] ... FAILED
tempest.api.object_storage.test_container_staticweb.StaticWebTest.test_web_listing_css [0.100988s] ... FAILED
The problem with Tripple-O that prompted this fix was that it uses SSL
(which is great), but Swift has no way to know that. In such cases,
it is best to set the url_base to "https://" and nothing else. Other
parts will be properly determined automatically.
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