Red Hat Bugzilla – Bug 1000153
availability graph isn't present unless there are other metrics
Last modified: 2015-02-05 20:19:17 EST
Select a resource with no metrics - e.g. sudoers or bundle handler.
Monitoring tab only contains 'schedules' there's no 'metrics' tab to view the avail graph.
This was an oversight with combining the availability tab into the metrics tab. This has been fixed availability shows up even if the resource or resource group doesn't have metrics associated with it.
Committed to master: f8226ea.
Created attachment 800017 [details]
visible for resource groups in jon 3.2 er7 -> http://d.pr/i/Xha9
@Armine I think the comment https://bugzilla.redhat.com/show_bug.cgi?id=1000153#c4 is erroneous as the screen shot shows the group metrics page (which should not have the avail graph) and not group graphs page which does have the avail graph.
@Mike, I'm sorry, comment #4 is an invalid one. The screen-shot is on metrics page, while the issue is visible on graphs page.
Test scenario is the following:
go to platforms -> Storage Nodes group -> Graphs --- no availability graph visible
go to platforma -> CPUs -> graphs -- availability graph is visible
go to platforms -> CPUs -> graphs -> RHQ Storage Nodes group -> availability graph is visible
Created attachment 854009 [details]
FYI: The fix for Bug 1057255 may be relevant.
Just FYI: this code was committed: 2013-08-22 18:02:47 EDT, was verified on 2013-09-19 11:50:52 EDT and made it to JON 3.2.0. release.
IMO the FailedQA on 2013-11-26 07:50:02 EST since it was already tested and committed to release/3.2.x. That is what changed the status to ASSIGNED from VERIFIED, which during a release can be very confusing.
I think we should split the bug from https://bugzilla.redhat.com/show_bug.cgi?id=1000153#c7 into its own BZ to avoid this confusion.
original bug is verified in jon 3.2
separate bz for comment #7 filed -> #1057705
JON 3.2.1 released week of 5/5/2014