Bug 1334522 - Incorrect sort by option for instances while sorting instances through C&U graphs
Summary: Incorrect sort by option for instances while sorting instances through C&U gr...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat CloudForms Management Engine
Classification: Red Hat
Component: UI - OPS
Version: 5.6.0
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: GA
: 5.6.0
Assignee: Milan Zázrivec
QA Contact: Nandini Chandra
URL:
Whiteboard: ui:c&u:cloud
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-05-09 21:17 UTC by Nandini Chandra
Modified: 2016-06-29 16:00 UTC (History)
7 users (show)

Fixed In Version: 5.6.0.9
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-06-29 16:00:51 UTC
Category: ---
Cloudforms Team: ---
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
Screen shot of all sort by options (72.39 KB, image/png)
2016-05-09 21:17 UTC, Nandini Chandra
no flags Details


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2016:1348 0 normal SHIPPED_LIVE CFME 5.6.0 bug fixes and enhancement update 2016-06-29 18:50:04 UTC

Description Nandini Chandra 2016-05-09 21:17:07 UTC
Created attachment 1155468 [details]
Screen shot of all sort by options

Description of problem:
-----------------------
While sorting instances through the C&U graphs of an Availability zone,
the sort by drop down lists 'cloud' as an option.

I was comparing the options listed in the sort by drop down on the 
Compute->Cloud->Instances page and the drop down on this page doesn't have 'cloud' as one of the options.For the sake of consistency, the 'cloud' option needs to be replaced with something that's present on the 
Compute->Cloud->Instances page.

Also,the UI blows up when the instances are sorted by the cloud option.


Version-Release number of selected component (if applicable):
--------------------------
5.6.0.5


How reproducible:
----------------
Always


Steps to Reproduce:
-------------------
1.Manage a cloud provider.Enable C&U collection.Navigate to the summary page of an Availability zone.
2.Click Monitoring, click Utilization.View hourly or daily graphs for network or disk or cpu usage.Drill into the chart data by hovering over a data point.
3.Click on  the short cut menu to display the virtual machines that were running at the time the data was captured. 


Actual results:
---------------
The instances running at the time the data was captured are displayed.On this page, 'cloud' is listed as one of the options in the the sort by drop down.


Expected results:
----------------
Replace the cloud option with something more relevant.


Additional info:
----------------

Comment 2 Milan Zázrivec 2016-05-10 12:57:51 UTC
Is there a CFME instance of a database showing this problem?

Thanks.

Comment 4 Milan Zázrivec 2016-05-26 12:55:50 UTC
https://github.com/ManageIQ/manageiq/pull/8985

Comment 5 CFME Bot 2016-05-27 14:05:56 UTC
New commit detected on ManageIQ/manageiq/master:
https://github.com/ManageIQ/manageiq/commit/eb8bb68ab069226a9722c3f6a67e50eb6c626c1f

commit eb8bb68ab069226a9722c3f6a67e50eb6c626c1f
Author:     Milan Zazrivec <mzazrivec>
AuthorDate: Thu May 26 14:51:40 2016 +0200
Commit:     Milan Zazrivec <mzazrivec>
CommitDate: Thu May 26 14:51:40 2016 +0200

    Fix report type when rendering instances under availability zone
    
    When navigating to Cloud -> Availability Zone -> Utilization ->
    Instances running / Instances stopped, we were using general
    VM report, which we normally use to render both instances and vms
    (all in one view).
    
    It's better fit to render view we use when we render cloud instances.
    
    https://bugzilla.redhat.com/show_bug.cgi?id=1334522

 app/controllers/vm_controller.rb | 4 +++-
 1 file changed, 3 insertions(+), 1 deletion(-)

Comment 6 Nandini Chandra 2016-06-08 13:10:15 UTC
Verified in 5.6.0.9

Comment 8 errata-xmlrpc 2016-06-29 16:00:51 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/RHBA-2016:1348


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