[tickets] [opensaf:tickets] #2675 smf: SMF cannot distinguish swAdd and swRemove in same procedure.
commit 57459e185890e05fc4035f3d2656b099cc7b9165 Author: Vijay RoyDate: Mon Nov 27 12:21:35 2017 +0530 smf: SMF cannot distinguish swAdd and swRemove in same procedure [#2675] Conditional check on AMF nodes in swadd and swRemove exactly for same and match to avoid ambiguity between nodes. --- ** [tickets:#2675] smf: SMF cannot distinguish swAdd and swRemove in same procedure.** **Status:** review **Milestone:** 5.18.01 **Created:** Fri Nov 10, 2017 06:35 AM UTC by Vijay Roy **Last Updated:** Mon Nov 27, 2017 06:45 AM UTC **Owner:** Vijay Roy **Problem Summary:** If software installed on all the nodes (where not required) So, inorder to fix the accidental installation of software on nodes that are not required by using an upgrade campaign that remove software from SCs and upgrade software on PLs. The problem is that SMF ignores both swAdd and swRemove when it is same procedure and for same software bundle.As consequence, software is removed from all nodes. **Log Message** Oct 23 20:33:26.809021 osafsmfd [4440:5908:../../opensaf/src/smf/smfd/SmfUpgradeMethod.cc:0183] TR SmfUpgradeScope::removeSwAddRemoveDuplicates(): Bundle=safSmfBundle=campaign_install.xml found in and within a procedure, remove from both lists --- 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] #2675 smf: SMF cannot distinguish swAdd and swRemove in same procedure.
- **status**: review --> fixed --- ** [tickets:#2675] smf: SMF cannot distinguish swAdd and swRemove in same procedure.** **Status:** fixed **Milestone:** 5.18.01 **Created:** Fri Nov 10, 2017 06:35 AM UTC by Vijay Roy **Last Updated:** Fri Dec 01, 2017 07:07 AM UTC **Owner:** Vijay Roy **Problem Summary:** If software installed on all the nodes (where not required) So, inorder to fix the accidental installation of software on nodes that are not required by using an upgrade campaign that remove software from SCs and upgrade software on PLs. The problem is that SMF ignores both swAdd and swRemove when it is same procedure and for same software bundle.As consequence, software is removed from all nodes. **Log Message** Oct 23 20:33:26.809021 osafsmfd [4440:5908:../../opensaf/src/smf/smfd/SmfUpgradeMethod.cc:0183] TR SmfUpgradeScope::removeSwAddRemoveDuplicates(): Bundle=safSmfBundle=campaign_install.xml found in and within a procedure, remove from both lists --- 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] #2705 ntf: ntfd remove client in standby node while not finalize in active node
- **status**: accepted --> review --- ** [tickets:#2705] ntf: ntfd remove client in standby node while not finalize in active node** **Status:** review **Milestone:** 5.18.01 **Created:** Mon Nov 27, 2017 07:32 AM UTC by Canh Truong **Last Updated:** Thu Nov 30, 2017 02:46 AM UTC **Owner:** Canh Truong Steps to reproduce the issue (not always happen): 1/ saNtfInitialize_1 2/ saNtfFinalize_1 3/ saNtfInitialize_2 4/ saNtfNotificationSubscribe_2 5/ saNtfFinalize_2 At the end of step 2, the NCSMDS_DOWN event will be send to both active and standby node. - In active node, mds thread send this request to ntfd through mailbox. ntfd receive this request to process this event and it delete the all clients then go to step 3 to: initialize new client_2 and send ckpt to standby to initialize (create) new client_2 in standby node. - In standby node, mds thread send this request to ntfd through mailbox. But ntfd receive the NCSMDS_DOWN request after ckpt of initialize request of step 3. So new client_2 is created in standby node first, then ntfd process the NCSMDS_DOWN request. It will remove all clients in standby node. No client in standby node In step 4, the subcribe request is processed in active node and send ckpt of this request to standby node. In the standby node, ntfd receive the ckpt of subcribe request and process. But it can not find the client --- 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] #2683 pyosaf: refactor IMM utils
- **summary**: pyosaf: improve OI utils use a separate instance OM agent --> pyosaf: refactor IMM utils - Description has changed: Diff: --- old +++ new @@ -1 +1,2 @@ -Update the oi agent/implementer/applier to use a separate instance of om agent/accessor instead of using the immom and its deprecated functions. ++ Improve OI utils use a separate instance OM agent ++ Refactor OM utils with Ccb inheritace OmAgent, rename some classes... --- ** [tickets:#2683] pyosaf: refactor IMM utils** **Status:** accepted **Milestone:** 5.18.01 **Created:** Thu Nov 16, 2017 08:24 AM UTC by Hieu Nguyen **Last Updated:** Thu Nov 16, 2017 08:24 AM UTC **Owner:** Hieu Nguyen + Improve OI utils use a separate instance OM agent + Refactor OM utils with Ccb inheritace OmAgent, rename some classes... --- 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] #2712 msg: msgd crash during multiple node reboot
- **status**: review --> fixed - **Comment**: commit d40172a1afb2f95afdb6b6b5cf4804d559ac6c50 Author: Alex JonesDate: Thu Nov 30 08:29:21 2017 -0500 --- ** [tickets:#2712] msg: msgd crash during multiple node reboot** **Status:** fixed **Milestone:** 5.18.01 **Created:** Wed Nov 29, 2017 05:10 PM UTC by Alex Jones **Last Updated:** Wed Nov 29, 2017 07:44 PM UTC **Owner:** Alex Jones If multiple nodes are rebooted at the same time and one of the nodes is the active controller, msgd on the newly active controller can crash at AMF assignment time. There is a race condition in handling the CLM tracking notification. If the CLM tracking callback is called more than once before the assignment has finished, it is possible that "is_node_down" and "is_clm_down" can both be set to true. In the AMF assignment code the node info is deleted for each node for which these variables are set. But, if they are both set msgd crashes because of a double delete. --- 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