Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1552095

Summary: Network Topology "Graph" tab always shows nothing
Product: Red Hat OpenStack Reporter: Beth White <beth.white>
Component: python-django-horizonAssignee: Radomir Dopieralski <rdopiera>
Status: CLOSED ERRATA QA Contact: Ido Ovadia <iovadia>
Severity: urgent Docs Contact:
Priority: urgent    
Version: 13.0 (Queens)CC: apannu, athomas, jrist, mrunge, srevivo, ukalifon
Target Milestone: betaKeywords: OtherQA, Triaged
Target Release: 13.0 (Queens)   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: python-django-horizon-13.0.1-0.20180323102048.4dd4ef0.el7ost Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-06-27 13:35:05 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
network topology osp 13 none

Description Beth White 2018-03-06 13:48:15 UTC
Network Topology "Graph" tab always says "There are no networks, routers, or connected instances to display."
This happens after a fix for bug 1661350 (commit f35eaa2d13fc5aff31b9a83dc729cc20b91fc611) was merged.

Note that "Topology" tab works fine.

Comment 2 Radomir Dopieralski 2018-03-16 11:26:30 UTC
I couldn't reproduce this with the upstream master, neither in Chrome nor Firefox.

Comment 6 Jason E. Rist 2018-04-11 05:23:46 UTC
Created attachment 1420163 [details]
network topology osp 13

Comment 7 Jason E. Rist 2018-04-11 05:27:26 UTC
python-django-horizon-13.0.1-0.20180323102049.el7ost.noarch

Comment 9 errata-xmlrpc 2018-06-27 13:35:05 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-2018:2086