oslo middleware provides a paste filter that sets the correct proxy scheme and host. This is needed for the TLS proxy case.
Without this then enabling the TLS proxy in devstack will fail configuring tempest because 'nova flavor-list' returns a http scheme in Location in a redirect it returns.
I've proposed a temporary workaround in devstack using:
oslo middleware provides a paste filter that sets the correct proxy scheme and host. This is needed for the TLS proxy case.
Without this then enabling the TLS proxy in devstack will fail configuring tempest because 'nova flavor-list' returns a http scheme in Location in a redirect it returns.
I've proposed a temporary workaround in devstack using:
+ iniset $NOVA_API_PASTE_INI filter: ssl_header_ handler past .http_proxy_ to_wsgi: HTTPProxyToWSGI .factory openstack_ compute_ ap app_v21"
e.filter_factory oslo_middleware
+ iniset $NOVA_API_PASTE_INI composite:
i_v21 keystone "ssl_header_handler cors compute_req_id faultwrap sizelimit autht
oken keystonecontext osapi_compute_
But this isn't a long-term solution because two copies of the default paste filters will need to be maintained.
See https:/ /review. openstack. org/#/c/ 301172