Bug 1598910 - Backport support for custom neutron_options for Horizon to OSP10
Summary: Backport support for custom neutron_options for Horizon to OSP10
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: puppet-tripleo
Version: 10.0 (Newton)
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: z9
: 10.0 (Newton)
Assignee: Carlos Goncalves
QA Contact: nlevinki
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-07-06 20:23 UTC by Andrew Austin
Modified: 2019-10-29 20:36 UTC (History)
10 users (show)

Fixed In Version: puppet-tripleo-5.6.8-12.el7ost
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-09-17 16:56:14 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
OpenStack gerrit 573836 0 'None' MERGED Allow neutron_options customization for dashboard 2020-03-20 20:58:22 UTC
Red Hat Product Errata RHBA-2018:2670 0 None None None 2018-09-17 16:57:14 UTC

Description Andrew Austin 2018-07-06 20:23:20 UTC 
Description of problem:

A customer wishing to use the Horizon LBaaS dashboard is currently having to adjust the horizon configuration after any overcloud update with an Ansible playbook. In Pike and later, this option is supported via Hiera data overrides. This support has been backported to stable/ocata and stable/newton upstream. I would like to see the backport also pulled into OSP10 to reduce the amount of post-configuration conflicts for this customer and others using LBaaS.
Comment 12 Alex McLeod 2018-09-03 08:01:28 UTC 
Hi there,

If this bug requires doc text for errata release, please set the 'Doc Type' and provide draft text according to the template in the 'Doc Text' field.

The documentation team will review, edit, and approve the text.

If this bug does not require doc text, please set the 'requires_doc_text' flag to -.

Thanks,
Alex
Comment 14 errata-xmlrpc 2018-09-17 16:56:14 UTC 
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/RHBA-2018:2670
Note You need to log in before you can comment on or make changes to this bug.