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

NPE in UI if metric used in condition set has been removed.

Details

  • Type: Bug Bug
  • Status: Closed Closed
  • Priority: Trivial Trivial
  • Resolution: Deferred
  • Affects Version/s: 4.5
  • Fix Version/s: None
  • Component/s: Alerts
  • Case Links:
    none
  • Regression:
    No
  • Tags:

Description

If a plugin is redeployed and a metric which has been removed is used in alert condition sets, those alerts will become unviewable from the UI.

It's debatable what should happen in this scenario, and for that I'll be logging an HPM bug. In the meantime, this NPE should be avoided so that the metric can be corrected without needing to delete and re-create the alert definition. The stacktrace is as follows and should be fairly easy to fix:

ava.lang.NullPointerException at org.hyperic.hq.ui.action.resource.common.monitor.alerts.config.ConditionBean.importProperties(ConditionBean.java:340) at org.hyperic.hq.ui.action.resource.common.monitor.alerts.config.DefinitionForm.importConditionsEnablement(DefinitionForm.java:495) at com.hyperic.hq.ui.action.resource.common.monitor.alerts.config.DefinitionForm.importConditionsEnablement(DefinitionForm.java:142) at

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 ago