[tickets] [opensaf:tickets] #2400 AMFD: Cached node_up message causes amfnd reboot after node joins cluster
- **status**: unassigned --> accepted - **assigned_to**: Gary Lee --- ** [tickets:#2400] AMFD: Cached node_up message causes amfnd reboot after node joins cluster** **Status:** accepted **Milestone:** 5.1.1 **Created:** Wed Mar 29, 2017 06:05 AM UTC by Minh Hon Chau **Last Updated:** Wed Mar 29, 2017 06:05 AM UTC **Owner:** Gary Lee SC Absence is enabled, restarts both SCs. After all amfnd introduce node_up and join cluster, cluster startup timer expires in which amfd will start application assignments. At this time, a retransmitted node_up message which could be cached in mailbox (or late coming) that makes amfd to order a node reboot ar 20 15:04:46 SC-2 osafamfd[9576]: NO Receive message with event type:12, msg_type:31, from node:2040f, msg_id:0 Mar 20 15:04:46 SC-2 osafamfd[9576]: NO Receive message with event type:12, msg_type:31, from node:2030f, msg_id:0 Mar 20 15:04:46 SC-2 osafamfd[9576]: NO Receive message with event type:13, msg_type:32, from node:2040f, msg_id:0 Mar 20 15:04:46 SC-2 osafamfd[9576]: NO Receive message with event type:13, msg_type:32, from node:2030f, msg_id:0 Mar 20 15:04:46 SC-2 osafamfd[9576]: NO Received node_up_msg from all nodes Mar 20 15:04:46 SC-2 osafamfd[9576]: NO Received node_up from 2030f: msg_id 1 Mar 20 15:04:46 SC-2 osafamfd[9576]: NO Enter restore headless cached RTAs from IMM Mar 20 15:04:46 SC-2 osafamfd[9576]: NO Leave reading headless cached RTAs from IMM: SUCCESS Mar 20 15:04:46 SC-2 osafamfd[9576]: NO Node 'SC-2' joined the cluster Mar 20 15:04:49 SC-2 osafamfd[9576]: NO Received node_up from 2030f: msg_id 1 Mar 20 15:04:49 SC-2 osafamfd[9576]: NO Node 'PL-3' joined the cluster Mar 20 15:04:49 SC-2 osafamfd[9576]: NO Received node_up from 2010f: msg_id 1 Mar 20 15:04:49 SC-2 osafamfd[9576]: NO Node 'SC-1' joined the cluster Mar 20 15:05:00 SC-2 osafamfd[9576]: NO Cluster startup is done Mar 20 15:05:18 SC-2 osafamfd[9576]: NO Received node_up from 2030f: msg_id 1 Mar 20 15:05:18 SC-2 osafamfd[9576]: WA Sending node reboot order to node:safAmfNode=PL-3,safAmfCluster=myAmfCluster, due to late node_up_msg after cluster startup timeout --- 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] #2400 AMFD: Cached node_up message causes amfnd reboot after node joins cluster
--- ** [tickets:#2400] AMFD: Cached node_up message causes amfnd reboot after node joins cluster** **Status:** unassigned **Milestone:** 5.1.1 **Created:** Wed Mar 29, 2017 06:05 AM UTC by Minh Hon Chau **Last Updated:** Wed Mar 29, 2017 06:05 AM UTC **Owner:** nobody SC Absence is enabled, restarts both SCs. After all amfnd introduce node_up and join cluster, cluster startup timer expires in which amfd will start application assignments. At this time, a retransmitted node_up message which could be cached in mailbox (or late coming) that makes amfd to order a node reboot ar 20 15:04:46 SC-2 osafamfd[9576]: NO Receive message with event type:12, msg_type:31, from node:2040f, msg_id:0 Mar 20 15:04:46 SC-2 osafamfd[9576]: NO Receive message with event type:12, msg_type:31, from node:2030f, msg_id:0 Mar 20 15:04:46 SC-2 osafamfd[9576]: NO Receive message with event type:13, msg_type:32, from node:2040f, msg_id:0 Mar 20 15:04:46 SC-2 osafamfd[9576]: NO Receive message with event type:13, msg_type:32, from node:2030f, msg_id:0 Mar 20 15:04:46 SC-2 osafamfd[9576]: NO Received node_up_msg from all nodes Mar 20 15:04:46 SC-2 osafamfd[9576]: NO Received node_up from 2030f: msg_id 1 Mar 20 15:04:46 SC-2 osafamfd[9576]: NO Enter restore headless cached RTAs from IMM Mar 20 15:04:46 SC-2 osafamfd[9576]: NO Leave reading headless cached RTAs from IMM: SUCCESS Mar 20 15:04:46 SC-2 osafamfd[9576]: NO Node 'SC-2' joined the cluster Mar 20 15:04:49 SC-2 osafamfd[9576]: NO Received node_up from 2030f: msg_id 1 Mar 20 15:04:49 SC-2 osafamfd[9576]: NO Node 'PL-3' joined the cluster Mar 20 15:04:49 SC-2 osafamfd[9576]: NO Received node_up from 2010f: msg_id 1 Mar 20 15:04:49 SC-2 osafamfd[9576]: NO Node 'SC-1' joined the cluster Mar 20 15:05:00 SC-2 osafamfd[9576]: NO Cluster startup is done Mar 20 15:05:18 SC-2 osafamfd[9576]: NO Received node_up from 2030f: msg_id 1 Mar 20 15:05:18 SC-2 osafamfd[9576]: WA Sending node reboot order to node:safAmfNode=PL-3,safAmfCluster=myAmfCluster, due to late node_up_msg after cluster startup timeout --- 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] #2396 base: Use dlopen to avoid LSB violation
- **status**: review --> fixed - **Comment**: changeset: 8735:68a5e668f807 user:Anders Widell date:Tue Mar 28 14:15:14 2017 +0200 summary: base: Use dlopen to avoid LSB violation [#2396] [staging:68a5e6] --- ** [tickets:#2396] base: Use dlopen to avoid LSB violation** **Status:** fixed **Milestone:** 5.2.RC2 **Created:** Thu Mar 23, 2017 02:59 PM UTC by Anders Widell **Last Updated:** Mon Mar 27, 2017 06:39 AM UTC **Owner:** Anders Widell Ticket [#2266] introduced a dependency towards the openssl library. This causes two problems: the first one is that this library is not part of LSB. The second (and related) one is that OpenSAF binaries built on one Linux distribution may fail to load on another Linux distribution, due to different names (versions) of this library. The suggested solution is to follow our earlier pattern and use dlopen() to open the library. If the library doesn't exist then the functionality will exhibit some default behaviour (e.g. the hash function will always return zero). --- 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] #2398 imm: retry of ccb abort should be allowed if failed with TRY_AGAIN and TIMEOUT
- **status**: review --> fixed - **Comment**: changeset: 8732:ea44141c05ee branch: opensaf-5.0.x parent: 8727:9a1452dcd190 user:Neelakanta Reddy date:Tue Mar 28 16:25:09 2017 +0530 summary: retry ccbabort when failed with TRY_AGAIN and TIMEOUT[#2398] changeset: 8733:be2fd9824bc4 branch: opensaf-5.1.x parent: 8728:bdd9cdb1ced9 user:Neelakanta Reddy date:Tue Mar 28 16:25:09 2017 +0530 summary: retry ccbabort when failed with TRY_AGAIN and TIMEOUT[#2398] changeset: 8734:5810bba59478 tag: tip parent: 8731:52f7fab7b8a7 user:Neelakanta Reddy date:Tue Mar 28 16:30:11 2017 +0530 summary: imm:retry ccbabort when failed with TRY_AGAIN and TIMEOUT[#2398] --- ** [tickets:#2398] imm: retry of ccb abort should be allowed if failed with TRY_AGAIN and TIMEOUT** **Status:** fixed **Milestone:** 5.0.2 **Created:** Mon Mar 27, 2017 07:50 AM UTC by Neelakanta Reddy **Last Updated:** Mon Mar 27, 2017 08:37 AM UTC **Owner:** Neelakanta Reddy steps : 1. create a ccb 2. saImmOmCcbAbort the ccb, the return code should be TRY_AGAIN, which can be re-produced when fevs queue is full T2 Too many pending incoming FEVS messages (> 16) enqueueing async message. Backlog:1 The saImmOmCcbAbort ccb will create the imma_newCcbId, without finalizing old ccbid. solution: do not create new ccbid when the return code is TRY_AGAIN or TIMEOUT --- 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] #2392 amf: PR doc updates for 5.2 release.
- **status**: accepted --> review --- ** [tickets:#2392] amf: PR doc updates for 5.2 release.** **Status:** review **Milestone:** 5.2.RC2 **Created:** Thu Mar 23, 2017 05:36 AM UTC by Praveen **Last Updated:** Tue Mar 28, 2017 09:52 AM UTC **Owner:** Praveen Updates to be done for: -Enhancments: #1190, #2259, #2144, #2252 -Defect:2233 --- 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] #2392 amf: PR doc updates for 5.2 release.
AMF PR doc for review for #1190, #2259, #2144, #2065 and #2233. Attachments: - [OpenSAF_AMF_PR_5.2.odt](https://sourceforge.net/p/opensaf/tickets/_discuss/thread/1d1e1df6/f63c/attachment/OpenSAF_AMF_PR_5.2.odt) (133.4 kB; application/vnd.oasis.opendocument.text) --- ** [tickets:#2392] amf: PR doc updates for 5.2 release.** **Status:** accepted **Milestone:** 5.2.RC2 **Created:** Thu Mar 23, 2017 05:36 AM UTC by Praveen **Last Updated:** Thu Mar 23, 2017 05:36 AM UTC **Owner:** Praveen Updates to be done for: -Enhancments: #1190, #2259, #2144, #2252 -Defect:2233 --- 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] #2399 log: unit test failed due to not updating new rfc5424 msgid handling
- **status**: review --> fixed - **assigned_to**: Vu Minh Nguyen --> nobody - **Comment**: changeset: 8731:52f7fab7b8a7 tag: tip user:Vu Minh Nguyen date:Mon Mar 27 21:24:56 2017 +0700 summary: log: unit test failed due to not updating new rfc5424 msgid handling [#2399] --- ** [tickets:#2399] log: unit test failed due to not updating new rfc5424 msgid handling** **Status:** fixed **Milestone:** 5.2.RC2 **Created:** Mon Mar 27, 2017 02:22 PM UTC by Vu Minh Nguyen **Last Updated:** Mon Mar 27, 2017 02:27 PM UTC **Owner:** nobody The RFC5424 msgid handling was updated in [#2397] but not reflect it to unit test, then causing following test case failed: > [==] 17 tests from 3 test cases ran. (3 ms total) > [ PASSED ] 16 tests. > [ FAILED ] 1 test, listed below: > [ FAILED ] WriteToDestination.HaveDestNameAndDestCfg --- 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] #2391 IMM: OI should not receive callbacks on a locked node
- **status**: review --> fixed - **Comment**: changeset: 8730:50398de4f5bc tag: tip user:Neelakanta Reddy date:Tue Mar 28 11:49:41 2017 +0530 summary: imm:unregister local implementers when clm node is locked[#2391] --- ** [tickets:#2391] IMM: OI should not receive callbacks on a locked node** **Status:** fixed **Milestone:** 5.2.RC2 **Created:** Wed Mar 22, 2017 09:08 AM UTC by Chani Srivastava **Last Updated:** Mon Mar 27, 2017 05:46 AM UTC **Owner:** Neelakanta Reddy **Environment details** OS : Suse 64bit Changeset : 8701 ( 5.2RC1) Setup : 4 nodes **Steps to Reproduce:** * Create a test class * Node1 - Initialize OM with A.2.18 * Node2 - Initialize OI with A.2.18 * Node2 - Make OI implementer for the test class created * Node2 - Call OiDispatch * Lock Node2 * Node1 - Try creating an object for test class for which OI is an implementer OI receives CreateCallback and responds with SA_AIS_OK **Expected**: On a clm locked node, OI should not receive any callback when initialize with A.2.18 --- 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] #2269 amf: saAmfSGNumPrefAssignedSUs is not honored in N-Way Active model.
- **status**: review --> assigned - **Milestone**: 5.0.2 --> next --- ** [tickets:#2269] amf: saAmfSGNumPrefAssignedSUs is not honored in N-Way Active model.** **Status:** assigned **Milestone:** next **Created:** Wed Jan 18, 2017 06:08 AM UTC by Praveen **Last Updated:** Fri Mar 10, 2017 10:44 AM UTC **Owner:** Praveen **Attachments:** - [AppConfig-nwayactive_3SUs_1SIs.xml](https://sourceforge.net/p/opensaf/tickets/2269/attachment/AppConfig-nwayactive_3SUs_1SIs.xml) (13.7 kB; text/xml) AMF assigns more SUs than the configured vaue of saAmfSGNumPrefAssignedSUs in N-Way Active model. Issue can be reproduced by brining up the attached configurration. In the application saAmfSGNumPrefAssignedSUs is set to 2: immlist safSg=NWay_Active\,safApp=NWay_Active | grep -i prefass saAmfSGNumPrefAssignedSUs SA_UINT32_T 2 (0x2) But AMF is giving assignmets to all the three SUs: safSISU=safSu=SU2\,safSg=NWay_Active\,safApp=NWay_Active,safSi=NWay_Active,safApp=NWay_Active saAmfSISUHAState=ACTIVE(1) safSISU=safSu=SU1\,safSg=NWay_Active\,safApp=NWay_Active,safSi=NWay_Active,safApp=NWay_Active saAmfSISUHAState=ACTIVE(1) safSISU=safSu=SU3\,safSg=NWay_Active\,safApp=NWay_Active,safSi=NWay_Active,safApp=NWay_Active saAmfSISUHAState=ACTIVE(1) Since this attribute is valid for N-Way model also, issue is applicable to N-Way model also. --- 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] #316 SI Assignments are not removed for a SU in Nway redundancy model
- **status**: review --> assigned - **Milestone**: 5.0.2 --> next --- ** [tickets:#316] SI Assignments are not removed for a SU in Nway redundancy model** **Status:** assigned **Milestone:** next **Created:** Fri May 24, 2013 08:39 AM UTC by Nagendra Kumar **Last Updated:** Thu Jan 05, 2017 06:31 AM UTC **Owner:** Praveen **Attachments:** - [logs.tar](https://sourceforge.net/p/opensaf/tickets/316/attachment/logs.tar) (2.5 MB; application/x-gzip-compressed) - [osafamfd](https://sourceforge.net/p/opensaf/tickets/316/attachment/osafamfd) (228.2 kB; application/octet-stream) - [osafamfnd](https://sourceforge.net/p/opensaf/tickets/316/attachment/osafamfnd) (122.8 kB; application/octet-stream) - [pl_logs.tar](https://sourceforge.net/p/opensaf/tickets/316/attachment/pl_logs.tar) (1.3 MB; application/x-gzip-compressed) Migrated from http://devel.opensaf.org/ticket/2987 changeset : 3855 Model : NWay configuration : 1App,1SG,5SU with 3comps each, 5SIs with 3csi each. si-si deps configured as SI1<-SI2<-SI3<-SI4 SIrankedSus not configured. Node mapping : SU1 on SC-1, SU2 on SC-2, SU3 on PL-3, SU4,SU5 on PL-4. While running the campaign, smf performs lock,lock-in of the activation units i.e SUs. The SIs for SU3 are not removed though SU3 is in locked-state. Subsequent unlock-in,unlock of SU3 fails. /var/log/messages of active ctrl- SC-1 shows Feb 3 22:45:14 linux-xc76 osafamfd[20055]: WA SIs still assigned to this SU Feb 3 22:45:16 linux-xc76 osafamfd[20055]: WA SIs still assigned to this SU Feb 3 22:45:18 linux-xc76 osafamfd[20055]: WA SIs still assigned to this SU Feb 3 22:45:20 linux-xc76 osafamfd[20055]: WA SIs still assigned to this SU Feb 3 22:45:23 linux-xc76 osafamfd[20055]: WA SIs still assigned to this SU Feb 3 22:45:23 linux-xc76 osafsmfd[20081]: ER Fail to invoke admin operation, too many SA_AIS_ERR_TRY_AGAIN, giving up. dn=[safSu=SU3,safSg=SGONE,safApp=NWAYAPP], opId=[3] Feb 3 22:45:23 linux-xc76 osafsmfd[20081]: ER Failed to call admin operation 3 on safSu=SU3,safSg=SGONE,safApp=NWAYAPP Feb 3 22:45:23 linux-xc76 osafsmfd[20081]: ER Failed to Terminate activation units in step=safSmfStep=0003 Feb 3 22:45:23 linux-xc76 osafsmfd[20081]: ER Step undoing failed Feb 3 22:45:23 linux-xc76 osafsmfd[20081]: ER Step safSmfStep=0003 in procedure safSmfProc=amfClusterProc-1 failed, step result 5 Feb 3 22:45:23 linux-xc76 osafsmfd[20081]: NO CAMP: Procedure safSmfProc=amfClusterProc-1 returned FAILED SU Assignments brief: === safSISU=safSu=SU1\,safSg=SGONE\,safApp=NWAYAPP,safSi=NWAYSI3,safApp=NWAYAPP saAmfSISUHAState=ACTIVE(1) safSISU=safSu=SU1\,safSg=SGONE\,safApp=NWAYAPP,safSi=NWAYSI2,safApp=NWAYAPP saAmfSISUHAState=STANDBY(2) safSISU=safSu=SU3\,safSg=SGONE\,safApp=NWAYAPP,safSi=NWAYSI5,safApp=NWAYAPP saAmfSISUHAState=QUIESCED(3) safSISU=safSu=SU4\,safSg=SGONE\,safApp=NWAYAPP,safSi=NWAYSI5,safApp=NWAYAPP saAmfSISUHAState=ACTIVE(1) safSISU=safSu=SU2\,safSg=SGONE\,safApp=NWAYAPP,safSi=NWAYSI1,safApp=NWAYAPP saAmfSISUHAState=ACTIVE(1) SU States: == safSu=SU3,safSg=SGONE,safApp=NWAYAPP saAmfSUAdminState=LOCKED(2) saAmfSUOperState=ENABLED(1) saAmfSUPresenceState=INSTANTIATED(3) saAmfSUReadinessState=OUT-OF-SERVICE(1) changed 4 months ago by bertil ¶ ■owner changed from ingber to ravisekhar ■component changed from saf/smfsv to saf/avsv I beleave this is an AMF problem. SMF only uses the AMF admin ops (lock, unlock etc). --- 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
