Description of problem: One part of enabling the LbaaS v2 administration in horizon is installing a package openstack-neutron-lbaas-ui As I have confirmed, in a OSP 12 lab, the package is missing in the horizon container. The problem about this is the following: Assuming it is possible to get the package within the container, you would need to restart the httpd to take effect of the package. Since the httpd is PID 1 of the container, if you restart it, the container is killed and created again. Regarding the container is created / started again from the original image the package is not in the container anymore. So, I think the package should probably be included in the horizon docker image. Actual results: The package openstack-neutron-lbaas-ui is not in the horizon container thus it is not possible to enable LBaaS in horizon Expected results: The package is available in the container somehow.
The openstack-neutron-lbaas-ui package is installed in the horizon container: [root@controller-0 heat-admin]# docker exec -ti horizon rpm -q openstack-neutron-lbaas-ui openstack-neutron-lbaas-ui-3.0.1-3.el7ost.noarch The dashboard is enabled in kolla by tripleo-heat-templates upstream [1][2]. The reason why the dashboard is not enabled in OSP 12 is due to a downstream-only patch that prevented the dashboard from being enabled to resolve rhbz #1514412 [3]. While the reason for disabling the fwaas dashboard was justified, I do not understand at this moment why it was also necessary to disable the lbaas dashboard. I will reach out to the author of that patch to clarify. [1] https://github.com/openstack/tripleo-heat-templates/blob/stable/pike/docker/services/horizon.yaml#L155 [2] https://review.openstack.org/#/c/519445/ [3] https://bugzilla.redhat.com/show_bug.cgi?id=1514412
Silly of me... Better and easier to NEEDINFO Beth Elwell.
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://access.redhat.com/errata/RHSA-2018:2331