Bug 1057705

Summary: availability graph isn't present for storage nodes auto-group
Product: [JBoss] JBoss Operations Network Reporter: Armine Hovsepyan <ahovsepy>
Component: UIAssignee: RHQ Project Maintainer <rhq-maint>
Status: CLOSED CURRENTRELEASE QA Contact: Armine Hovsepyan <ahovsepy>
Severity: medium Docs Contact:
Priority: unspecified    
Version: JON 3.2CC: jkremser, loleary, mfoley
Target Milestone: ER01   
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 13:59:38 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:
Bug Depends On: 1034512, 1057255    
Bug Blocks:    
Attachments:
Description Flags
avail_group
none
storage-group-graphs none

Description Armine Hovsepyan 2014-01-24 16:03:56 UTC
Created attachment 855064 [details]
avail_group

Description of problem:
availability graph isn't present for storage nodes auto-group

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

How reproducible:
always

Steps to Reproduce:

1. go to platforms -> Storage Nodes group -> Graphs 
2. go to platforma -> CPUs -> graphs 
3. go to platforms -> CPUs -> graphs -> RHQ Storage Nodes group -

Actual results:
After step1. --- no availability graph visible
After step2. --- availability graph is visible
After step3. --- availability graph is visible

Expected results:
After step1. --- availability graph is visiblee
After step2. --- availability graph is visible
After step3. --- availability graph is visible

Additional info:
screen-shot attached

Comment 1 Larry O'Leary 2014-01-24 22:41:18 UTC
This issue was reportedly fixed in upstream commits found in bug 1057255 and bug 1034512 and just needs to be brought over to the release branch.

Comment 2 Jirka Kremser 2014-08-19 14:07:41 UTC
It's in the release branch.

Comment 3 Jirka Kremser 2014-08-20 15:09:34 UTC
bz 1057255 was fixed by commit 799a0fe55 in master
bz 1034512 was fixed by commits b6206b7b9 and 1b05bf1c0, both in master

Commits were pushed to the master before the fork of master and creating the release 3.3.x branch. Hence, no need for cherry-picking. The BZ is happilly waiting to be verified against the ER01 release bits.

Comment 4 Armine Hovsepyan 2014-08-21 09:01:35 UTC
Created attachment 929120 [details]
storage-group-graphs

Comment 5 Armine Hovsepyan 2014-08-21 09:48:37 UTC
initial issue i fixed, availability graph is visible
new bz filed 1132400# (for storage nodes auto-group, which does not have metrics  - loading icon for metrics is visible forever)

Comment 6 Jirka Kremser 2014-08-21 10:02:18 UTC
right, I haven't noticed the missing metrics