Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 1573808 - The inability to enable LbaaS in horizon
The inability to enable LbaaS in horizon
Status: CLOSED ERRATA
Product: Red Hat OpenStack
Classification: Red Hat
Component: openstack-tripleo-heat-templates (Show other bugs)
12.0 (Pike)
Unspecified Linux
low Severity low
: z3
: 12.0 (Pike)
Assigned To: Carlos Goncalves
Alexander Stafeyev
: OtherQA, Triaged, ZStream
Depends On:
Blocks: 1574412 1607512
  Show dependency treegraph
 
Reported: 2018-05-02 05:59 EDT by ojanas
Modified: 2018-08-20 09:01 EDT (History)
12 users (show)

See Also:
Fixed In Version: openstack-tripleo-heat-templates-7.0.9-16.el7ost
Doc Type: Bug Fix
Doc Text:
To enable the neutron-lbaas dashboard: 1. Enable the dashboard in the Horizon configuration file in all controller nodes: File: /var/lib/config-data/puppet-generated/horizon/etc/openstack-dashboard/local_settings OPENSTACK_NEUTRON_NETWORK = { 'enable_distributed_router': False, 'enable_firewall': False, 'enable_ha_router': False, 'enable_lb': True, <---------- 2. Restart the horizon container: # docker restart horizon A new "Load Balancers" tab will appear under the "Network" menu. The URL is http://<controller-vip>/dashboard/project/ngloadbalancersv2
Story Points: ---
Clone Of:
: 1574412 1607512 (view as bug list)
Environment:
Last Closed: 2018-08-20 08:59:48 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)


External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2018:2331 None None None 2018-08-20 09:01 EDT

  None (edit)
Description ojanas 2018-05-02 05:59:07 EDT
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.
Comment 1 Carlos Goncalves 2018-05-02 18:39:04 EDT
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
Comment 2 Carlos Goncalves 2018-05-02 18:41:49 EDT
Silly of me... Better and easier to NEEDINFO Beth Elwell.
Comment 21 errata-xmlrpc 2018-08-20 08:59:48 EDT
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

Note You need to log in before you can comment on or make changes to this bug.