Bug 1474657 - Need an identifier on the "All Plans" breadcrumb in the deployment page
Summary: Need an identifier on the "All Plans" breadcrumb in the deployment page
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: openstack-tripleo-ui
Version: 12.0 (Pike)
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: beta
: 12.0 (Pike)
Assignee: RHOS Maint
QA Contact: Ola Pavlenko
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-07-25 06:54 UTC by Udi Kalifon
Modified: 2018-02-05 19:10 UTC (History)
6 users (show)

Fixed In Version: openstack-tripleo-ui-7.2.1-0.20170819031831.070a522.el7ost
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-12-13 21:44:48 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
OpenStack gerrit 487612 0 None None None 2017-07-26 22:27:20 UTC
Red Hat Product Errata RHEA-2017:3462 0 normal SHIPPED_LIVE Red Hat OpenStack Platform 12.0 Enhancement Advisory 2018-02-16 01:43:25 UTC

Description Udi Kalifon 2017-07-25 06:54:45 UTC 
Description of problem:
The new deployment page in the Ocata UI has a breadcrumb navigation at the top. To support the automation, please assign a unique ID on this element.


Version-Release number of selected component (if applicable):
openstack-tripleo-ui-7.1.1-0.20170718122426.8337319.el7ost.noarch
Comment 1 Jason E. Rist 2017-07-26 22:27:21 UTC 
I think this should be for Pike, not Ocata.  I've fixed the bug upstream for Pike.

https://review.openstack.org/487612
Comment 2 Jason E. Rist 2017-07-27 17:25:14 UTC 
Merged upstream.
Comment 4 Udi Kalifon 2017-09-03 11:38:28 UTC 
Tested in openstack-tripleo-ui-7.2.1-0.20170819031831.070a522.el7ost.noarch
Comment 8 errata-xmlrpc 2017-12-13 21:44:48 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-2017:3462
Note You need to log in before you can comment on or make changes to this bug.