Support Migration Notice: To update migrated JIRA cases click here to open a new case use www.vmware.com/go/sr | vFabric Hyperic 5.7.0 is Now Available

Hyperic HQ

Group count in HQ-Health and Resource Browse page are different

Details

  • Type: Bug Bug
  • Status: Closed Closed
  • Priority: Trivial Trivial
  • Resolution: Deferred
  • Affects Version/s: 4.4, 4.5
  • Fix Version/s: None
  • Component/s: Reports
  • Environment:
    Release 4.5-EE-71,Platform:Linux,DB:built-in
  • Case Links:
    none
  • Regression:
    No
  • Tags:

Description

Steps to reproduce

DO NOT CREATE ANY GROUPS
go to HQ-Health -->Load

Actual results:

#Group=8

System groups are included in HQ health count

select * from EAM_RESOURCE_GROUP
id version_col description location fsystem has_or_criteria grouptype cluster_id ctime mtime modified_by resource_prototype resource_id
0 0 null null t t 11 -1 0 0 null null 5
1 0 null null t t 11 -1 0 0 null null 7
10001 1 null t t 0 0 10-Aug-2010 12:24:17 10-Aug-2010 12:24:17 hqadmin null 10946
10002 1 null t t 0 0 10-Aug-2010 12:24:35 10-Aug-2010 12:24:35 hqadmin null 10948
10003 1 null t t 0 0 10-Aug-2010 12:24:42 10-Aug-2010 12:24:42 hqadmin null 10950
10004 1 null t t 0 0 10-Aug-2010 12:24:49 10-Aug-2010 12:24:49 hqadmin null 10952
10005 1 null t t 0 0 10-Aug-2010 12:24:58 10-Aug-2010 12:24:58 hqadmin null 10954
10006 1 null t t 0 0 10-Aug-2010 12:25:05 10-Aug-2010 12:25:05 hqadmin null 10956
id version_col description location fsystem has_or_criteria grouptype cluster_id ctime mtime modified_by resource_prototype resource_id

select count from EAM_RESOURCE_GROUP
count
8
count
Query Time=0

Expected Results:

Health Groups count should match Resources Browse page

Activity

Hide
Idan Hod added a comment -

As part of our continuous effort to improve product quality, The Hyperic product team has decided to implement a "zero bug policy" methodology.

Following this methodology, only defects that are planned to be handled in the near future will remain open. Any other defect will be deferred, with the option to be reevaluated if the need arises, or if changes to the Hyperic road-map make such defect a candidate for a fix.

We believe this new process will help create clarity and focus in the Hyperic road-map and ultimately benefit our customer base.

This bug has been deferred as part of the new policy.

We appreciate your cooperation and continues contribution to the improvement of Hyperic.

Show
Idan Hod added a comment - As part of our continuous effort to improve product quality, The Hyperic product team has decided to implement a "zero bug policy" methodology. Following this methodology, only defects that are planned to be handled in the near future will remain open. Any other defect will be deferred, with the option to be reevaluated if the need arises, or if changes to the Hyperic road-map make such defect a candidate for a fix. We believe this new process will help create clarity and focus in the Hyperic road-map and ultimately benefit our customer base. This bug has been deferred as part of the new policy. We appreciate your cooperation and continues contribution to the improvement of Hyperic.

People

Vote (0)
Watch (0)

Dates

  • Created:
    Updated:
    Resolved:
    Last comment:
    42 weeks, 1 day ago