Bug 1620076 - NetworkTopology vertical lines disappear when component is re-rendered
Summary: NetworkTopology vertical lines disappear when component is re-rendered
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
high
medium
Target Milestone: Upstream M3
: 14.0 (Rocky)
Assignee: Jiri Tomasek
QA Contact: Arik Chernetsky
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-08-22 12:05 UTC by Jiri Tomasek
Modified: 2019-01-11 11:52 UTC (History)
6 users (show)

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


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
OpenStack gerrit 594938 0 None None None 2018-08-22 12:08:17 UTC
Red Hat Product Errata RHEA-2019:0045 0 None None None 2019-01-11 11:52:52 UTC
Storyboard 2003524 0 None None None 2018-08-22 12:05:50 UTC

Description Jiri Tomasek 2018-08-22 12:05:51 UTC
Description of problem:
Vertical lines in network topology diagram disappear

Steps to Reproduce:
1. Open Network Configuration view by clicking 'Edit Configuration' at step 4 on deployment plan page
2. Let the network topology diagram load
3. Toggle validations sidebar
4. Vertical lines disappear

Comment 5 Udi Kalifon 2018-11-07 16:16:11 UTC
Verified: openstack-tripleo-ui-9.3.1-0.20180921180342.df30b55.el7ost.noarch

Comment 9 errata-xmlrpc 2019-01-11 11:51:27 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.