Description of problem: ======================= The Octavia horizon plugin got significant improvement upstream. Those improvements include both usability enhancements and UI support for existing Octavia features that were not exposed in Horizon. We got demand from several customers to backport those improvements so they can better leverage the UI to use Octavia. This bug will contain backports that could not be backported upstream. Version-Release number of selected component (if applicable): ============================================================= OSP13
Tested okay with scratch-build, going to make those backports officially part of the package. For QE: How to test: Tunneling the UI: 1. From within the server (not undercloud): ssh -N -L 8080:<CONTROLLER_IP>:80 undercloud-0 2. Browse to your server FQDN with port 8080 via your local browser Advanced (QE you will get an official package so you can probably skip this section for verification): How I locally patched (and applied) the backports in order to test this. 1. ssh into the horizon docker container 2. add a yum repository form brew scratch build 3. yum update openstack-octavia-ui Now horizon log (/var/log/horizon/horizon.log) will complain about: tail -f /var/log/horizon/horizon.log To overcome this: 4. Copy the manage.py file to: https://raw.githubusercontent.com/openstack/horizon/master/manage.py /usr/lib/python2.7/site-packages/django And also /usr/lib/python2.7/site-packages/horizon (the latter might not be a must but I did it anyway and it worked for me) 5. Within both directories run: python manage.py compress Exit the container and restart it. Now you'll be able to use the octavia-ui in horizon.
*** Bug 1705904 has been marked as a duplicate of this bug. ***
"Fixed in Version" was set to OSP 14 octavia dashboard. Setting correct RPM for OSP 13 (released in OSP 13z7).
According to our records, this should be resolved by openstack-octavia-ui-1.0.1-6.el7ost. This build is available now.
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-2020:0769