[tickets] [opensaf:tickets] #178 escalation policy is not happening till the restart count exceeds, instead of reaching saAmfSGCompRestartMax for NPI components
- **assigned_to**: Nagendra Kumar --> nobody - **Blocker**: False --> True --- ** [tickets:#178] escalation policy is not happening till the restart count exceeds, instead of reaching saAmfSGCompRestartMax for NPI components** **Status:** unassigned **Milestone:** future **Created:** Tue May 14, 2013 06:24 AM UTC by Nagendra Kumar **Last Updated:** Mon Aug 28, 2017 07:00 AM UTC **Owner:** nobody Migrated from http://devel.opensaf.org/ticket/2144 error escalation is not happening till the restart count exceeds saAmfSGCompRestartMax for the components brought up in NPI. But according to spec, first level escalation should happen when the restart count reaches the saAmfSGCompRestartMax Mentioned in the spec, 3.11.2.2 page NO: 203, If this count reaches the saAmfSGCompRestartMax value before the end of the "component restart" probation period, the Availability Management Framework per- forms the first level of recovery escalation for that service unit: the Availability Man- agement Framework restarts the entire service unit --- Sent from sourceforge.net because opensaf-tickets@lists.sourceforge.net 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.-- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot___ Opensaf-tickets mailing list Opensaf-tickets@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
[tickets] [opensaf:tickets] #178 escalation policy is not happening till the restart count exceeds, instead of reaching saAmfSGCompRestartMax for NPI components
- **status**: assigned --> unassigned - **Blocker**: --> False --- ** [tickets:#178] escalation policy is not happening till the restart count exceeds, instead of reaching saAmfSGCompRestartMax for NPI components** **Status:** unassigned **Milestone:** future **Created:** Tue May 14, 2013 06:24 AM UTC by Nagendra Kumar **Last Updated:** Tue Sep 20, 2016 06:04 PM UTC **Owner:** Nagendra Kumar Migrated from http://devel.opensaf.org/ticket/2144 error escalation is not happening till the restart count exceeds saAmfSGCompRestartMax for the components brought up in NPI. But according to spec, first level escalation should happen when the restart count reaches the saAmfSGCompRestartMax Mentioned in the spec, 3.11.2.2 page NO: 203, If this count reaches the saAmfSGCompRestartMax value before the end of the "component restart" probation period, the Availability Management Framework per- forms the first level of recovery escalation for that service unit: the Availability Man- agement Framework restarts the entire service unit --- Sent from sourceforge.net because opensaf-tickets@lists.sourceforge.net 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.-- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot___ Opensaf-tickets mailing list Opensaf-tickets@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
[tickets] [opensaf:tickets] #178 escalation policy is not happening till the restart count exceeds, instead of reaching saAmfSGCompRestartMax for NPI components
- **Milestone**: 4.5.2 --> 4.6.2 --- ** [tickets:#178] escalation policy is not happening till the restart count exceeds, instead of reaching saAmfSGCompRestartMax for NPI components** **Status:** assigned **Milestone:** 4.6.2 **Created:** Tue May 14, 2013 06:24 AM UTC by Nagendra Kumar **Last Updated:** Wed Aug 12, 2015 09:11 AM UTC **Owner:** Nagendra Kumar Migrated from http://devel.opensaf.org/ticket/2144 error escalation is not happening till the restart count exceeds saAmfSGCompRestartMax for the components brought up in NPI. But according to spec, first level escalation should happen when the restart count reaches the saAmfSGCompRestartMax Mentioned in the spec, 3.11.2.2 page NO: 203, If this count reaches the saAmfSGCompRestartMax value before the end of the "component restart" probation period, the Availability Management Framework per- forms the first level of recovery escalation for that service unit: the Availability Man- agement Framework restarts the entire service unit --- Sent from sourceforge.net because opensaf-tickets@lists.sourceforge.net 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.-- ___ Opensaf-tickets mailing list Opensaf-tickets@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
[tickets] [opensaf:tickets] #178 escalation policy is not happening till the restart count exceeds, instead of reaching saAmfSGCompRestartMax for NPI components
- **status**: unassigned -- assigned - **assigned_to**: Nagendra Kumar --- ** [tickets:#178] escalation policy is not happening till the restart count exceeds, instead of reaching saAmfSGCompRestartMax for NPI components** **Status:** assigned **Milestone:** 4.5.2 **Created:** Tue May 14, 2013 06:24 AM UTC by Nagendra Kumar **Last Updated:** Thu Aug 06, 2015 11:16 AM UTC **Owner:** Nagendra Kumar Migrated from http://devel.opensaf.org/ticket/2144 error escalation is not happening till the restart count exceeds saAmfSGCompRestartMax for the components brought up in NPI. But according to spec, first level escalation should happen when the restart count reaches the saAmfSGCompRestartMax Mentioned in the spec, 3.11.2.2 page NO: 203, If this count reaches the saAmfSGCompRestartMax value before the end of the component restart probation period, the Availability Management Framework per- forms the first level of recovery escalation for that service unit: the Availability Man- agement Framework restarts the entire service unit --- Sent from sourceforge.net because opensaf-tickets@lists.sourceforge.net 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.-- ___ Opensaf-tickets mailing list Opensaf-tickets@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
[tickets] [opensaf:tickets] #178 escalation policy is not happening till the restart count exceeds, instead of reaching saAmfSGCompRestartMax for NPI components
- **Type**: enhancement -- defect - **Milestone**: future -- 4.5.2 - **Comment**: As part of ticket cleanup, evaluated and found that this issue needs to be fixed as defect. --- ** [tickets:#178] escalation policy is not happening till the restart count exceeds, instead of reaching saAmfSGCompRestartMax for NPI components** **Status:** unassigned **Milestone:** 4.5.2 **Created:** Tue May 14, 2013 06:24 AM UTC by Nagendra Kumar **Last Updated:** Wed Jul 15, 2015 06:46 PM UTC **Owner:** nobody Migrated from http://devel.opensaf.org/ticket/2144 error escalation is not happening till the restart count exceeds saAmfSGCompRestartMax for the components brought up in NPI. But according to spec, first level escalation should happen when the restart count reaches the saAmfSGCompRestartMax Mentioned in the spec, 3.11.2.2 page NO: 203, If this count reaches the saAmfSGCompRestartMax value before the end of the component restart probation period, the Availability Management Framework per- forms the first level of recovery escalation for that service unit: the Availability Man- agement Framework restarts the entire service unit --- Sent from sourceforge.net because opensaf-tickets@lists.sourceforge.net 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.-- ___ Opensaf-tickets mailing list Opensaf-tickets@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
[tickets] [opensaf:tickets] #178 escalation policy is not happening till the restart count exceeds, instead of reaching saAmfSGCompRestartMax for NPI components
- **Type**: defect -- enhancement --- ** [tickets:#178] escalation policy is not happening till the restart count exceeds, instead of reaching saAmfSGCompRestartMax for NPI components** **Status:** unassigned **Milestone:** future **Created:** Tue May 14, 2013 06:24 AM UTC by Nagendra Kumar **Last Updated:** Tue May 14, 2013 06:24 AM UTC **Owner:** nobody Migrated from http://devel.opensaf.org/ticket/2144 error escalation is not happening till the restart count exceeds saAmfSGCompRestartMax for the components brought up in NPI. But according to spec, first level escalation should happen when the restart count reaches the saAmfSGCompRestartMax Mentioned in the spec, 3.11.2.2 page NO: 203, If this count reaches the saAmfSGCompRestartMax value before the end of the component restart probation period, the Availability Management Framework per- forms the first level of recovery escalation for that service unit: the Availability Man- agement Framework restarts the entire service unit --- Sent from sourceforge.net because opensaf-tickets@lists.sourceforge.net 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.-- Don't Limit Your Business. Reach for the Cloud. GigeNET's Cloud Solutions provide you with the tools and support that you need to offload your IT needs and focus on growing your business. Configured For All Businesses. Start Your Cloud Today. https://www.gigenetcloud.com/___ Opensaf-tickets mailing list Opensaf-tickets@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
