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

Avail balloon bar is not correctly calculated on group level

Details

  • Type: Bug Bug
  • Status: Closed Closed
  • Priority: Minor Minor
  • Resolution: Deferred
  • Affects Version/s: 4.6
  • Fix Version/s: None
  • Component/s: UI / UX
  • Case Links:
    none
  • 3.0 Category:
    UI, Metric Data, Groups
  • Regression:
    No

Description

When viewing group(either compatible or auto-group), availability balloons are not calculated correctly(see attached screenshots).

group with 2 members, one up, one down: avails are 0.0% (should be 50.0%)
group with 3 members, two up, one down: avails are 50.0% (should be 66.7%)
group with 4 members, three up, one down: avails are 66.7% (should be 75.0%)

group with 2 members, balloons should be yellow but those are red. This is because avails are set to 0%. groups with 3/4 members are correctly shown as yellow, but this is because yellow is shows if avails is between 0% and 100%.

  1. avails-group-scripts.png
    56 kB
    19/Sep/11 8:31 AM
  2. avails-group-scripts2.png
    56 kB
    19/Sep/11 8:31 AM
  3. avails-group-scripts3.png
    47 kB
    19/Sep/11 8:31 AM
  4. avails-on-group-level.png
    35 kB
    19/Sep/11 8:31 AM
  5. group-level.png
    32 kB
    19/Sep/11 8:31 AM
  6. group-scripts.png
    54 kB
    19/Sep/11 8:31 AM
  7. group-scripts2.png
    55 kB
    19/Sep/11 8:31 AM
  8. group-scripts-2.png
    55 kB
    19/Sep/11 8:31 AM

Issue Links

Activity

Hide
Adar Margalit added a comment - - edited

Tested in 4.7, percentages working correctly. Perhaps it was fixed. May also be that availability percentage is a bit confusing: Availability percentage is calculated over time, so if a resource becomes available/unavailable, the percentage will not immediately respond to this. E.g: if two resources exist and both are down, then when one becomes available the percentage will initially stay on 0%, and gradually rise over time until it reaches 50%.
For case of two resources, one up one down, the dots are red - this is a bug.

Show
Adar Margalit added a comment - - edited Tested in 4.7, percentages working correctly. Perhaps it was fixed. May also be that availability percentage is a bit confusing: Availability percentage is calculated over time, so if a resource becomes available/unavailable, the percentage will not immediately respond to this. E.g: if two resources exist and both are down, then when one becomes available the percentage will initially stay on 0%, and gradually rise over time until it reaches 50%. For case of two resources, one up one down, the dots are red - this is a bug.
Hide
Yoav Epelman added a comment -

Bulk change to new components

Show
Yoav Epelman added a comment - Bulk change to new components
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 (1)

Dates

  • Created:
    Updated:
    Resolved:
    Last comment:
    41 weeks ago