Bug 1032033

Summary:	Sort unavailable & alerted resources portlet - parent first
Product:	[JBoss] JBoss Operations Network	Reporter:	Libor Zoubek <lzoubek>
Component:	UI	Assignee:	Libor Zoubek <lzoubek>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Mike Foley <mfoley>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	JON 3.2	CC:	jshaughn, myarboro, theute
Target Milestone:	DR01
Target Release:	JON 3.3.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2014-12-11 14:05:01 UTC	Type:	Enhancement
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Libor Zoubek 2013-11-19 12:19:02 UTC

Description of problem:

On our dashboard, there is by default portlet called "Alerted or unavailable resources". It's by default set to display only 20 resources.


Version-Release number of selected component (if applicable):
JON 3.2.ER5

How reproducible: always


Steps to Reproduce:
1. have EAP6 imported and available
2. stop it
3. go to dashboard and look at above portlet

Actual results:

It shows lot's of resources, direct or undirect children of your EAP6 server. It does not show EAP6 server itself though. When you see this (assuming you don't know you just stopped your server) you have to navigate to any of those resources and find out .. "ah that JMS factory is down is because server is down"


Expected results: portlet should show resources with shortest inventory path (platforms first, servers, services, then rest of resources) so user does not have to navitage. 


Additional info:

Comment 1 Libor Zoubek 2014-05-06 09:48:16 UTC

in master
commit e429846dd715e0615e27eb1aa7e599cc508481a6
Author: Libor Zoubek <lzoubek>
Date:   Tue May 6 11:41:30 2014 +0200

    [BZ 1032033] - Sort unavailable & alerted resources portlet - parent first

    Unavailable and alerted resources are now ordered by 1. alert count, 2.
    ancestry.length 3. resource name - so when for example platform is DOWN it
    will show up in portlet before it's children

Comment 2 Jay Shaughnessy 2014-05-13 16:05:14 UTC

commit 89d4f63a8017d4ee4acd20b3af3129f71086c980
Author: Jay Shaughnessy <jshaughn>
Date:   Tue May 13 12:04:14 2014 -0400

  Fix a few issues with the prior commit for this issue (e429846dd715e0)
  - needed to be able to handle null ancestry (for platforms, which can
    be problem resources like anything else). This fix fixed the test
    failures as well.
  - Restore the previous ProblemResourceComposite constructor since this
    class *is* exposed remotely.  Add new entry for new constructor.

Comment 3 Simeon Pinder 2014-07-31 15:52:36 UTC

Moving to ON_QA as available to test with brew build of DR01: https://brewweb.devel.redhat.com//buildinfo?buildID=373993