Bug 1600424 - Rebrand Tripleo to Director in OSP14
Summary: Rebrand Tripleo to Director in OSP14
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: openstack-tripleo-ui
Version: 14.0 (Rocky)
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: Upstream M2
: 14.0 (Rocky)
Assignee: Jason E. Rist
QA Contact: Arik Chernetsky
URL:
Whiteboard:
: 1635954 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-07-12 08:27 UTC by Udi Kalifon
Modified: 2019-01-11 11:50 UTC (History)
6 users (show)

Fixed In Version: openstack-tripleo-ui-9.3.1-0.20180921180341.df30b55.el7ost
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-01-11 11:50:39 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHEA-2019:0045 0 None None None 2019-01-11 11:50:50 UTC

Description Udi Kalifon 2018-07-12 08:27:52 UTC 
Description of problem:
Tripelo should be called Director downstream. Currently, when we install OSP14, we see Tripleo in the UI and not Director.


Version-Release number of selected component (if applicable):
openstack-tripleo-ui-9.0.1-0.20180523202213.73df625.el7ost.noarch
Comment 2 Jason E. Rist 2018-09-14 22:03:03 UTC 
https://code.engineering.redhat.com/gerrit/150191
Comment 9 Beth White 2018-10-17 10:11:31 UTC 
*** Bug 1635954 has been marked as a duplicate of this bug. ***
Comment 10 Udi Kalifon 2018-10-17 13:05:22 UTC 
Verified in: openstack-tripleo-ui-9.3.1-0.20180921180341.df30b55.el7ost.noarch
Comment 12 errata-xmlrpc 2019-01-11 11:50:39 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/RHEA-2019:0045
Note You need to log in before you can comment on or make changes to this bug.