- **status**: review --> fixed
- **Comment**:
changeset: 5455:c387169d4891
tag: tip
user: [email protected]
date: Mon Jul 14 10:04:41 2014 +0530
summary: amf : fix component related alarms [#108]
[staging:c38716]
---
** [tickets:#108] AMF - Clear SA_AMF_NTFID_COMP_INSTANTIATION_FAILED alarms
automatically**
**Status:** fixed
**Milestone:** 4.5.FC
**Created:** Mon May 13, 2013 05:39 AM UTC by Nagendra Kumar
**Last Updated:** Tue Jun 24, 2014 08:42 AM UTC
**Owner:** Praveen
Migrated from http://devel.opensaf.org/ticket/1801
--------------------------------------------------------
I caused this alarm to be raised by rendering the component non-executable.
Once satisfied with the result (alarm generated) I re-enabled the component.
The component was eventually recovered, comes up and assumes standby - but the
alarm remains.
If I lock an SG, I get alarms raised that automatically clear upon unlock of
the SG. Should the behavior be consistent? My expectation was that once the
affected component started, the alarm would automatically clear.
--------------------------------------------------------
Changed 2 years ago by hafe ¶
■owner changed from nagendra to hafe
■status changed from new to accepted
■version changed from 4.0.1 to 4.2.0
■type changed from defect to enhancement
■summary changed from SA_AMF_NTFID_COMP_INSTANTIATION_FAILED fails to clear
automatically to Clear SA_AMF_NTFID_COMP_INSTANTIATION_FAILED alarms
automatically
Will be published together with #1194.
Changed 2 years ago by hafe ¶
■summary changed from Clear SA_AMF_NTFID_COMP_INSTANTIATION_FAILED alarms
automatically to AMF - Clear SA_AMF_NTFID_COMP_INSTANTIATION_FAILED alarms
automatically
■version changed from 4.2.0 to 4.0.1
■milestone set to 4.2.0.GA
Changed 2 years ago by hafe ¶
My patch produces this output:
May 3 7:05:15 - Alarm
eventType = SA_NTF_ALARM_PROCESSING
notificationObject =
"safComp=AmfDemo?,safSu=SU2,safSg=AmfDemo?,safApp=AmfDemo?1"
notifyingObject = "safApp=safAmfService"
notificationClassId = SA_NTF_VENDOR_ID_SAF.SA_SVC_AMF.2 (0x2)
additionalText = "Previous raised alarm of
safComp=AmfDemo?,safSu=SU2,safSg=AmfDemo?,safApp=AmfDemo?1 is now cleared"
probableCause = SA_NTF_SOFTWARE_ERROR
perceivedSeverity = SA_NTF_SEVERITY_CLEARED
OK?
Changed 2 years ago by hafe ¶
■patch_waiting changed from no to yes
Changed 2 years ago by creid ¶
Looks good to me. Seems consistent with other auto-behaviour.
Changed 20 months ago by hafe ¶
■milestone changed from 4.2.0.GA to 4.3.GA
Changed 2 months ago by hafe ¶
■milestone changed from 4.3.GA to future_releases
---
Sent from sourceforge.net because [email protected] is
subscribed to https://sourceforge.net/p/opensaf/tickets/
To unsubscribe from further messages, a project admin can change settings at
https://sourceforge.net/p/opensaf/admin/tickets/options. Or, if this is a
mailing list, you can unsubscribe from the mailing list.
------------------------------------------------------------------------------
Want fast and easy access to all the code in your enterprise? Index and
search up to 200,000 lines of code with a free copy of Black Duck®
Code Sight™ - the same software that powers the world's largest code
search on Ohloh, the Black Duck Open Hub! Try it now.
http://p.sf.net/sfu/bds
_______________________________________________
Opensaf-tickets mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
