Wrong name for zaqar websocket in UI when configured with puppet

Bug #1630965 reported by Julie Pichon
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
tripleo
Fix Released
High
Julie Pichon

Bug Description

In the UI configuration file, the URL name for the Zaqar websocket changed from "zaqar_websocket_url" to "zaqar-websocket" in http://git.openstack.org/cgit/openstack/tripleo-ui/commit/?id=e9765d . The template in the puppet configuration at http://git.openstack.org/cgit/openstack/puppet-tripleo/tree/templates/ui/tripleo_ui_config.js.erb wasn't updated though, so if a user just uncomments and changes the URL, it won't get picked up and things will break.

On a default install the UI still works, because except for Keystone the services URLs are obtained from the catalogue. This causes issues when overriding (which is frequently needed when using a virtualised environment and tunnelling to the UI).

Revision history for this message
Julie Pichon (jpichon) wrote :
Changed in tripleo:
status: Triaged → In Progress
Julie Pichon (jpichon)
tags: added: newton-backport-potential
Julie Pichon (jpichon)
Changed in tripleo:
milestone: none → ocata-1
Julie Pichon (jpichon)
Changed in tripleo:
milestone: ocata-1 → newton-rc3
Revision history for this message
Julie Pichon (jpichon) wrote :

The master patch merged. The newton backport is proposed at https://review.openstack.org/#/c/385453/ .

Changed in tripleo:
status: In Progress → Fix Released
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/puppet-tripleo 5.3.0

This issue was fixed in the openstack/puppet-tripleo 5.3.0 release.

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/puppet-tripleo 6.0.0

This issue was fixed in the openstack/puppet-tripleo 6.0.0 release.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.