Reviewed: https://review.openstack.org/640230 Committed: https://git.openstack.org/cgit/openstack/manila/commit/?id=edc60f76c2818351f8a6d1090a5549970b1891cc Submitter: Zuul Branch: stable/rocky commit edc60f76c2818351f8a6d1090a5549970b1891cc Author: Goutham Pacha Ravi <gouthampravi at gmail.com> Date: Wed Feb 20 18:00:45 2019 -0800 Fix tls-proxy issues with the devstack plugin Enabling tls-proxy allows devstack to set up a tls proxy server that front-ends interactions with the manila-api and terminates tls connections. Also enable tls-proxy in dummy and lvm jobs. The dummy driver job is configured to run the in-built wsgi server, the lvm job is configured to use mod-wsgi. Closes-Bug: #1816836 Change-Id: I48b0ccc082604d78242ba61bee94a45efeb2467b (cherry picked from commit 8f1c7dc91fb1e00784f6228526d95f4434ba8a01) ** Tags added: in-stable-rocky -- You received this bug notification because you are a member of OpenStack Security SIG, which is subscribed to OpenStack. https://bugs.launchpad.net/bugs/1816836 Title: manila's devstack plugin fails with tls_proxy enabled Status in Manila: Fix Released Bug description: This bug was exposed in https://review.openstack.org/#/c/625191/ (Relevant log files have been attached to this bug report). Manila's devstack plugin sets the listen port to 18786 when tls_proxy has been enabled on devstack, but performs a health check on the API service on the default/non-tls port (8786) [2]. This check causes devstack to fail. [1] https://github.com/openstack/manila/blob/22d25e8/devstack/plugin.sh#L280 [2] https://github.com/openstack/manila/blob/22d25e8/devstack/plugin.sh#L830 To manage notifications about this bug go to: https://bugs.launchpad.net/manila/+bug/1816836/+subscriptions