Bug 1391123 - Infrastructure Topology legend buttons inaccuracy
Summary: Infrastructure Topology legend buttons inaccuracy
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat CloudForms Management Engine
Classification: Red Hat
Component: UI - OPS
Version: 5.7.0
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: GA
: 5.8.0
Assignee: Tzu-Mainn Chen
QA Contact: Ola Pavlenko
URL:
Whiteboard: openstack:topology
Depends On:
Blocks: 1399211
TreeView+ depends on / blocked
 
Reported: 2016-11-02 15:33 UTC by Ido Ovadia
Modified: 2017-08-30 03:50 UTC (History)
8 users (show)

Fixed In Version: 5.8.0.0
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
: 1399211 (view as bug list)
Environment:
Last Closed: 2017-06-12 17:25:00 UTC
Category: Bug
Cloudforms Team: Openstack
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
Infrastructure Topology (107.32 KB, image/png)
2016-11-02 15:33 UTC, Ido Ovadia
no flags Details

Description Ido Ovadia 2016-11-02 15:33:02 UTC
Created attachment 1216598 [details]
Infrastructure Topology

Description of problem:
=======================
Infrastructure Topology legend buttons inaccuracy

Click on Node shows the Roles
Click on Roles shows the Nodes

Version-Release number of selected component:
=============================================
5.7.0.7-beta1.20161025153249_9376fbd 

How reproducible:
=================
100%

Steps to Reproduce:
===================
1. Add OpenStack Director to CFME as infrastructure provider
2. Browse to: Compute --> Infrastructure --> Topology
3. Click Roles , Click Nodes

Actual results:
===============
- Click Roles show/hide Nodes
- Click Nodes show/hide Roles

Expected results:
=================
- Click Roles show/hide Roles
- Click Nodes show/hide Nodes

Additional info:
================
Screenshot is enclosed. Roles is selected but the the topology shows Nodes

Comment 1 Tzu-Mainn Chen 2016-11-22 16:04:03 UTC
https://github.com/ManageIQ/manageiq/pull/12573

Comment 3 Ronnie Rasouli 2017-03-08 07:09:20 UTC
verified on 5.8.0.3


Note You need to log in before you can comment on or make changes to this bug.