[tickets] [opensaf:tickets] #2122 smf: "Stray" temporary Node Group cannot be deleted
- **status**: review --> fixed - **assigned_to**: elunlen --> nobody - **Comment**: changeset: 8243:93a22ddd5a7c tag: tip parent: 8241:8aecb97e47c7 user:Lennart Lunddate:Thu Oct 20 12:16:17 2016 +0200 summary: smf: Admin owner set needed if new handles has been created [#2122] rev: 93a22ddd5a7c290d79658a517778ec89ecdfe54f changeset: 8242:a419ee7f46dd branch: opensaf-5.1.x parent: 8240:276761ea0a9b user:Lennart Lund date:Thu Oct 20 12:16:17 2016 +0200 summary: smf: Admin owner set needed if new handles has been created [#2122] rev: a419ee7f46dd6616d2f393dcee170eb952bff1c6 --- ** [tickets:#2122] smf: "Stray" temporary Node Group cannot be deleted** **Status:** fixed **Milestone:** 5.1.1 **Created:** Mon Oct 17, 2016 02:39 PM UTC by elunlen **Last Updated:** Tue Oct 18, 2016 01:55 PM UTC **Owner:** nobody Parallel lock handling creates a temporary node group containing nodes for a node group admin operation. Normally this node group object is always deleted directly after the admin operation. However in the case of an uncontrolled program abortion after the node group is created but before it is deleted the temporary node group will remain as a "stray" object. This means that the next time a campaign is executed an SA_AIS_ERR_EXIST error will be returned when the node group shall be created. To handle this a recovery mechanism is implemented that is supposed to delete the "stray" node group and retry node group creation. The problem is that this is not working since the correct admin owner for doing this is not set If this is not fixed it means that all future campainges that uses nodes as activation and/or deactivation units will fail unless the "stray" node group is manually deleted! --- 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] #2122 smf: "Stray" temporary Node Group cannot be deleted
- **status**: accepted --> review --- ** [tickets:#2122] smf: "Stray" temporary Node Group cannot be deleted** **Status:** review **Milestone:** 5.1.1 **Created:** Mon Oct 17, 2016 02:39 PM UTC by elunlen **Last Updated:** Mon Oct 17, 2016 02:39 PM UTC **Owner:** elunlen Parallel lock handling creates a temporary node group containing nodes for a node group admin operation. Normally this node group object is always deleted directly after the admin operation. However in the case of an uncontrolled program abortion after the node group is created but before it is deleted the temporary node group will remain as a "stray" object. This means that the next time a campaign is executed an SA_AIS_ERR_EXIST error will be returned when the node group shall be created. To handle this a recovery mechanism is implemented that is supposed to delete the "stray" node group and retry node group creation. The problem is that this is not working since the correct admin owner for doing this is not set If this is not fixed it means that all future campainges that uses nodes as activation and/or deactivation units will fail unless the "stray" node group is manually deleted! --- 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] #2122 smf: "Stray" temporary Node Group cannot be deleted
--- ** [tickets:#2122] smf: "Stray" temporary Node Group cannot be deleted** **Status:** accepted **Milestone:** 5.1.1 **Created:** Mon Oct 17, 2016 02:39 PM UTC by elunlen **Last Updated:** Mon Oct 17, 2016 02:39 PM UTC **Owner:** elunlen Parallel lock handling creates a temporary node group containing nodes for a node group admin operation. Normally this node group object is always deleted directly after the admin operation. However in the case of an uncontrolled program abortion after the node group is created but before it is deleted the temporary node group will remain as a "stray" object. This means that the next time a campaign is executed an SA_AIS_ERR_EXIST error will be returned when the node group shall be created. To handle this a recovery mechanism is implemented that is supposed to delete the "stray" node group and retry node group creation. The problem is that this is not working since the correct admin owner for doing this is not set If this is not fixed it means that all future campainges that uses nodes as activation and/or deactivation units will fail unless the "stray" node group is manually deleted! --- 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