tripleo-ui should listen on all interfaces

[Donny Davis]

The Tripleo UI puppet module has the tripleo-ui listen on only the br-ctlplane interface. This is the pxe interface in baremetal deployments may not be accessible from outside the tripleo machine.

https://github.com/openstack/puppet-tripleo/blob/master/manifests/ui.pp

 $bind_host = hiera('controller_host'),

This parameter makes the tripleo-ui listen on only br-ctlplane interface.

[Donny Davis (automatikdonn)]

Changing the parameter to

 $bind_address = undef,

resolves this issue

[Dan Trainor (dtrainor)]

Digging in to this a little, I discovered that setting bind_host (reported as bind_address in the bug, but I think what Donny meant was "bind_host") to undef will not work for SSL-enabled Undercloud deployments.

The reason for this is that, when an SSL-enabled Undercloud is used, HAProxy listens on both the undercloud_public_vip (a required parameter for SSL-enabled Underclouds) and controller_admin_vip (which is the same as the ctrlplane address when using non-SSL Underclouds). If bind_host gets set to undef, then Apache attempts to listen on *:3000 which conflicts with the port already allocated by HAProxy, causing Apache startup to fail.

I think the best approach to doing this would be to set ui.pp bind_host to undef, and make haproxy only listen on port 443 per the UI container. This would provide a happy path for both SSL-enabled Underclouds (via $undercloud_public_vip:443) and non-SSL Underclouds (via $undercloud_public_vip or the ctrlplane address).

[Michael Glaser (mikeg451)]

Haven't had time to work on this, so will unassign myself to allow someone else to work on it.

[Emilien Macchi (emilienm)]

This is an automated cleanup. This bug report has been closed because it
is older than 18 months and there is no open code change to fix this.
After this time it is unlikely that the circumstances which lead to
the observed issue can be reproduced.

If you can reproduce the bug, please:
* reopen the bug report (set to status "New")
* AND add the detailed steps to reproduce the issue (if applicable)
* AND leave a comment "CONFIRMED FOR: <RELEASE_NAME>"
  Only still supported release names are valid (FUTURE, PIKE, QUEENS, ROCKY, STEIN).
  Valid example: CONFIRMED FOR: FUTURE

[Ruslanas Gzibovskis (lpic)]

this is still active :) and reproducible :)