[tickets] [opensaf:tickets] #2080 smf: balanced upgrade software bundle missmatch
--- ** [tickets:#2080] smf: balanced upgrade software bundle missmatch** **Status:** accepted **Milestone:** 5.1.1 **Created:** Thu Sep 29, 2016 07:50 AM UTC by Rafael **Last Updated:** Thu Sep 29, 2016 07:50 AM UTC **Owner:** Rafael When merging steps for the BALANCED_MODE execution there is a missmatch in how the software bundles are added to the new step. The problem will show when nodes have different software installed and not all of those nodes are included in the balanced list. --- 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] #2079 MDS: TIPC change logging level at TIPC_ERRINFO for all but TIPC_ERR_OVERLOAD
- **status**: review --> fixed - **Comment**: changeset: 8162:9bebf8014e89 tag: tip user:Hans Nordeback date:Wed Sep 28 13:33:01 2016 +0200 files: osaf/libs/core/mds/mds_dt_tipc.c description: MDS: TIPC change logging level at TIPC_ERRINFO for all but TIPC_ERR_OVERLOAD [#2079] --- ** [tickets:#2079] MDS: TIPC change logging level at TIPC_ERRINFO for all but TIPC_ERR_OVERLOAD** **Status:** fixed **Milestone:** 5.2.FC **Created:** Wed Sep 28, 2016 11:31 AM UTC by Hans Nordebäck **Last Updated:** Wed Sep 28, 2016 11:33 AM UTC **Owner:** Hans Nordebäck --- 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] #2081 amfd: assert in avd_compcsi_cleanup_imm_object
--- ** [tickets:#2081] amfd: assert in avd_compcsi_cleanup_imm_object** **Status:** review **Milestone:** 5.2.FC **Created:** Thu Sep 29, 2016 08:24 AM UTC by Hans Nordebäck **Last Updated:** Thu Sep 29, 2016 08:24 AM UTC **Owner:** Hans Nordebäck Sep 20 04:42:20 SC-1 osafamfd[12518]: ../../../../../../../opensaf/osaf/services/saf/amf/amfd/csi.cc:1688: avd_compcsi_cleanup_imm_object: Assertion 'comp' failed. --- 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] #2081 amfd: assert in avd_compcsi_cleanup_imm_object
This assert causes cyclic reboots of SC-1 during resilience testing --- ** [tickets:#2081] amfd: assert in avd_compcsi_cleanup_imm_object** **Status:** review **Milestone:** 5.2.FC **Created:** Thu Sep 29, 2016 08:24 AM UTC by Hans Nordebäck **Last Updated:** Thu Sep 29, 2016 08:24 AM UTC **Owner:** Hans Nordebäck Sep 20 04:42:20 SC-1 osafamfd[12518]: ../../../../../../../opensaf/osaf/services/saf/amf/amfd/csi.cc:1688: avd_compcsi_cleanup_imm_object: Assertion 'comp' failed. --- 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] #1650 IMM: When Ccb is aborted with BAD_OPERATION, wrong error string is received at the OM side
- **status**: accepted --> review --- ** [tickets:#1650] IMM: When Ccb is aborted with BAD_OPERATION, wrong error string is received at the OM side** **Status:** review **Milestone:** 5.0.2 **Created:** Mon Dec 21, 2015 12:28 PM UTC by Chani Srivastava **Last Updated:** Tue Sep 27, 2016 10:21 AM UTC **Owner:** Hung Nguyen Following are the steps to execute: 1. Enable long dn on one node only and initialize Ccb on that node 2. On other node create OI which does not supports long dns 3. Convert parent name and object name to long DN names and call ccbObjectCreate 4. Ccb will be aborted with FAILED_OPERATION at OM side 5. Call getErrorStrings to check the reason of abort. Result: 3. As OI does not support long DN, it returns BAD_OPERATION 5. Error string returned is - Resource abort: Upcall failed with error code: 20 Expected: In this case Validation Abort error string should be set by IMM --- 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] #2059 AMF: SU struck in terminating state, for failure in component instantiation
- **summary**: AMF: SU struck in terminating state, for failure in component restart --> AMF: SU struck in terminating state, for failure in component instantiation - **status**: assigned --> accepted - Attachments has changed: Diff: --- old +++ new @@ -1 +1,2 @@ 2059.tgz (821.7 kB; application/x-compressed-tar) +AppConfig-2N.xml_on_SC-1_2comps (10.5 kB; application/octet-stream) - **Part**: - --> nd - **Comment**: Analysis: Comp faults witjh comp-failover recovery. After removal of assignments, AMFNFD tries to reapir the component by trying to instantiate it. Since instantiate scripit is not present, comp instantiation fails and AMFND cleans up it succesfully. After this successful cleanup AMFND niether tries to instantiate the comp again not it marks comp and SU to INST_FAILED state. AMFND should mark the comp and SU to INST_FAILED state after finishing instantiation of comp MAX_TRY times. If the value is not configuted for the comp then AMFND should honour the default value of saAmfNumMaxInstantiateWithoutDelay=2. Attached is the amf_demo based conf to reproduce the issue. --- ** [tickets:#2059] AMF: SU struck in terminating state, for failure in component instantiation** **Status:** accepted **Milestone:** 5.0.2 **Created:** Thu Sep 22, 2016 07:05 AM UTC by Srikanth R **Last Updated:** Fri Sep 23, 2016 08:50 AM UTC **Owner:** Praveen **Attachments:** - [2059.tgz](https://sourceforge.net/p/opensaf/tickets/2059/attachment/2059.tgz) (821.7 kB; application/x-compressed-tar) - [AppConfig-2N.xml_on_SC-1_2comps](https://sourceforge.net/p/opensaf/tickets/2059/attachment/AppConfig-2N.xml_on_SC-1_2comps) (10.5 kB; application/octet-stream) Setup : Changeset : 7997 5.1.FC Setup : 5 node setup with 3 payloads. App : 2N PI Application with SUs hosted on PL-3,PL-4,SC-2. Issue : SU struck in terminating state, for failure in component restart Steps performed : -> Initially brought up the attached AMF configuration and 2 SUs got assigned successfully. -> Now moved the instantiation script on SU1. Note that termination script and instantiation script are different. -> Killed component of SU1. The component went for restart and assignments got removed from SU1 and SU2 & SU3 got active & standby. -> As the instantiation script is not available, SU should be moved to instantiation failed state. But the SU is struck in terminating state. -> Lock operation on SU succeeded, but lock-in operation on SU resulted in SG unstable. 175 12:28:31 09/22/2016 NO safApp=safAmfService "Admin op "LOCK" initiated for 'safSu=TestApp_SU1,safSg=TestApp_SG1,safApp=TestApp_TwoN', invocation: 408021893121" 176 12:28:31 09/22/2016 NO safApp=safAmfService "safSu=TestApp_SU1,safSg=TestApp_SG1,safApp=TestApp_TwoN AdmState UNLOCKED => LOCKED" 177 12:28:31 09/22/2016 NO safApp=safAmfService "Admin op done for invocation: 408021893121, result 1" 178 12:28:39 09/22/2016 NO safApp=safAmfService "Admin op "LOCK_INSTANTIATION" initiated for 'safSu=TestApp_SU1,safSg=TestApp_SG1,safApp=TestApp_TwoN', invocation: 412316860417" 179 12:28:39 09/22/2016 NO safApp=safAmfService "Admin op invocation: 412316860417, err: ''safSu=TestApp_SU1,safSg=TestApp_SG1,safApp=TestApp_TwoN' presence state is '4''" 180 12:28:39 09/22/2016 NO safApp=safAmfService "Admin op done for invocation: 412316860417, result 6" --- 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] #2059 AMF: SU struck in terminating state, for failure in component instantiation
- **status**: accepted --> review --- ** [tickets:#2059] AMF: SU struck in terminating state, for failure in component instantiation** **Status:** review **Milestone:** 5.0.2 **Created:** Thu Sep 22, 2016 07:05 AM UTC by Srikanth R **Last Updated:** Thu Sep 29, 2016 09:53 AM UTC **Owner:** Praveen **Attachments:** - [2059.tgz](https://sourceforge.net/p/opensaf/tickets/2059/attachment/2059.tgz) (821.7 kB; application/x-compressed-tar) - [AppConfig-2N.xml_on_SC-1_2comps](https://sourceforge.net/p/opensaf/tickets/2059/attachment/AppConfig-2N.xml_on_SC-1_2comps) (10.5 kB; application/octet-stream) Setup : Changeset : 7997 5.1.FC Setup : 5 node setup with 3 payloads. App : 2N PI Application with SUs hosted on PL-3,PL-4,SC-2. Issue : SU struck in terminating state, for failure in component restart Steps performed : -> Initially brought up the attached AMF configuration and 2 SUs got assigned successfully. -> Now moved the instantiation script on SU1. Note that termination script and instantiation script are different. -> Killed component of SU1. The component went for restart and assignments got removed from SU1 and SU2 & SU3 got active & standby. -> As the instantiation script is not available, SU should be moved to instantiation failed state. But the SU is struck in terminating state. -> Lock operation on SU succeeded, but lock-in operation on SU resulted in SG unstable. 175 12:28:31 09/22/2016 NO safApp=safAmfService "Admin op "LOCK" initiated for 'safSu=TestApp_SU1,safSg=TestApp_SG1,safApp=TestApp_TwoN', invocation: 408021893121" 176 12:28:31 09/22/2016 NO safApp=safAmfService "safSu=TestApp_SU1,safSg=TestApp_SG1,safApp=TestApp_TwoN AdmState UNLOCKED => LOCKED" 177 12:28:31 09/22/2016 NO safApp=safAmfService "Admin op done for invocation: 408021893121, result 1" 178 12:28:39 09/22/2016 NO safApp=safAmfService "Admin op "LOCK_INSTANTIATION" initiated for 'safSu=TestApp_SU1,safSg=TestApp_SG1,safApp=TestApp_TwoN', invocation: 412316860417" 179 12:28:39 09/22/2016 NO safApp=safAmfService "Admin op invocation: 412316860417, err: ''safSu=TestApp_SU1,safSg=TestApp_SG1,safApp=TestApp_TwoN' presence state is '4''" 180 12:28:39 09/22/2016 NO safApp=safAmfService "Admin op done for invocation: 412316860417, result 6" --- 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] #2077 amfd: fix cppcheck errors
- **status**: review --> fixed - **Comment**: changeset: 8163:52d4dc26b50a tag: tip user:Hans Nordeback date:Thu Sep 29 12:15:35 2016 +0200 files: osaf/libs/common/amf/include/amf_db_template.h description: amfd: fix cppcheck errors [#2077] cppcheck reports the following in changeset 7926: osaf/libs/common/amf/include/amf_db_template.h 36 noExplicitConstructor style Class 'SaNameTWrapper' has a constructor with 1 argument that is not explicit. 149 postfixOperator performance Prefer prefix ++/-- operators for non-primitive types. --- ** [tickets:#2077] amfd: fix cppcheck errors** **Status:** fixed **Milestone:** 5.2.FC **Created:** Tue Sep 27, 2016 04:54 PM UTC by Hans Nordebäck **Last Updated:** Wed Sep 28, 2016 07:22 AM UTC **Owner:** Hans Nordebäck cppcheck reports the following in changeset 7926: osaf/libs/common/amf/include/amf_db_template.h 36 noExplicitConstructor style Class 'SaNameTWrapper' has a constructor with 1 argument that is not explicit. 149 postfixOperator performance Prefer prefix ++/-- operators for non-primitive types. --- 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] #2082 CKPT : Track cbk not invoked for section creation after cpnd restart
--- ** [tickets:#2082] CKPT : Track cbk not invoked for section creation after cpnd restart** **Status:** unassigned **Milestone:** 4.7.2 **Created:** Thu Sep 29, 2016 11:06 AM UTC by Srikanth R **Last Updated:** Thu Sep 29, 2016 11:06 AM UTC **Owner:** nobody Changeset: 7997 5.1.FC Track Callback is not invoked after cpnd restart. Below are the apis called from the applications , spawned on two nodes .i.e payloads. On first node : -> Initialize with cpsv -> Create a ckpt with ACTIVE REPLICA flag. On second node. -> Initialize with cpsv. On First node, -> Open the checkpoint in writing mode -> Open the checkpoint in reading mode. -> Kill cpnd process -> Register for Track callback. On Second node, -> Open the ckpt in read mode. -> Kill cpnd proces -> Register for Track callback. After ensuring that both agents registered for track callback, create a section from the application on first node. For section creation, callback should be invoked for applications on two nodes. Currently callback is not invoked for the application on second node. With out cpnd restart, callback is invoked for the two applications --- 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] #2083 amf: error in syslog when initiating SI SWAP
--- ** [tickets:#2083] amf: error in syslog when initiating SI SWAP** **Status:** unassigned **Milestone:** future **Created:** Thu Sep 29, 2016 12:01 PM UTC by Rafael **Last Updated:** Thu Sep 29, 2016 12:01 PM UTC **Owner:** nobody SMF initiates an SI SWAP which fails but then the retry is succesful. The error result should not be logged as an error in syslog. osafamfd[473]: ER safSi=SC-2N,safApp=OpenSAF SWAP failed - only one assignment osafrded[407]: NO Peer up on node 0x2020f osafrded[407]: NO Got peer info request from node 0x2020f with role STANDBY osafrded[407]: NO Got peer info response from node 0x2020f with role STANDBY osafimmd[426]: NO MDS event from svc_id 24 (change:5, dest:13) osafimmnd[436]: NO Implementer (applier) connected: 49 (@safAmfService2020f) <0, 2020f> osafimmnd[436]: NO Implementer (applier) connected: 50 (@OpenSafImmReplicatorB) <0, 2020f> osafamfd[473]: ER safSi=SC-2N,safApp=OpenSAF SWAP failed - Cold sync in progress osafamfd[473]: NO safSi=SC-2N,safApp=OpenSAF Swap initiated --- 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] #2083 amf: error in syslog when initiating SI SWAP
Atleast this one seems to be duplicate #1897 Incorrect ER messages in syslog. However ther are other related tickets: #1294, #1779. --- ** [tickets:#2083] amf: error in syslog when initiating SI SWAP** **Status:** unassigned **Milestone:** future **Created:** Thu Sep 29, 2016 12:01 PM UTC by Rafael **Last Updated:** Thu Sep 29, 2016 12:01 PM UTC **Owner:** nobody SMF initiates an SI SWAP which fails but then the retry is succesful. The error result should not be logged as an error in syslog. osafamfd[473]: ER safSi=SC-2N,safApp=OpenSAF SWAP failed - only one assignment osafrded[407]: NO Peer up on node 0x2020f osafrded[407]: NO Got peer info request from node 0x2020f with role STANDBY osafrded[407]: NO Got peer info response from node 0x2020f with role STANDBY osafimmd[426]: NO MDS event from svc_id 24 (change:5, dest:13) osafimmnd[436]: NO Implementer (applier) connected: 49 (@safAmfService2020f) <0, 2020f> osafimmnd[436]: NO Implementer (applier) connected: 50 (@OpenSafImmReplicatorB) <0, 2020f> osafamfd[473]: ER safSi=SC-2N,safApp=OpenSAF SWAP failed - Cold sync in progress osafamfd[473]: NO safSi=SC-2N,safApp=OpenSAF Swap initiated --- 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] #2084 build: Refactor the directory structure and build system
--- ** [tickets:#2084] build: Refactor the directory structure and build system** **Status:** assigned **Milestone:** 5.2.FC **Created:** Thu Sep 29, 2016 02:15 PM UTC by Anders Widell **Last Updated:** Thu Sep 29, 2016 02:15 PM UTC **Owner:** Anders Widell Improve the OpenSAF directory structure and build system. The exact details of what and how to improve them is yet to be worked out, but below are some ideas: * In order to support better modularity of the different OpenSAF services, we should collect all files belonging to a particular OpenSAF service under a separate subdirectory per service. Today, files belonging to one single service (source code, library code, header files, tests, command-line tools) are scattered in many places. * Rename directories where appropriate. For example remove the "sv" suffix, e.g. clmsv -> clm. * Look at "standards" to see what kind of directory structure is commonly used by other projects. For example, maybe put the source code in a directory called "src". * Reduce the depth of the directory hierarchy. Some levels of the directory structure can be removed, for example the separate "include" directory that some services (but not all) currently use for their header files. Header files ought to into the same directory as source files. Another example is that we don't really need to divide services into "saf" and "infrastructure" and thus remove this level in the tree. * Improve parallelism of the build. I have a feeling that much more could be built in parallel than is possible today when you type "make -j". * Possibly look at alternatives to autotools, to see if we can also support something else (e.g. cmake) in addition to autotools. --- 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] #2069 smf : Retry for timeout should be avoided when si-swap returns timeout
- **status**: review --> fixed - **Comment**: changeset: 8164:5b2a3c287e31 branch: opensaf-5.0.x parent: 8159:abe3b25790a7 user:Neelakanta Reddy date:Fri Sep 30 10:04:15 2016 +0530 summary: smf:retry of Admin operation for TIMEOUT in si-swap to be avoided [#2069] changeset: 8165:b7ab66396f9b branch: opensaf-5.1.x parent: 8160:b54026b7ee72 user:Neelakanta Reddy date:Fri Sep 30 10:04:15 2016 +0530 summary: smf:retry of Admin operation for TIMEOUT in si-swap to be avoided [#2069] changeset: 8166:41ddae2ba01d tag: tip parent: 8163:52d4dc26b50a user:Neelakanta Reddy date:Fri Sep 30 10:04:15 2016 +0530 summary: smf:retry of Admin operation for TIMEOUT in si-swap to be avoided [#2069] --- ** [tickets:#2069] smf : Retry for timeout should be avoided when si-swap returns timeout** **Status:** fixed **Milestone:** 5.0.1 **Created:** Tue Sep 27, 2016 05:38 AM UTC by Neelakanta Reddy **Last Updated:** Tue Sep 27, 2016 07:22 AM UTC **Owner:** Neelakanta Reddy si-swap returns timeout : 1. timeout by the TIMEOUT parameter got expired 2. Implementation dependent timeout. In this case the TIMEOUT returned should be either from IMM/AMF.The timeout needs to be fixed. Before the TIMEOUT, if si-swap is about to complete and TIMEOUT is returned, because of IMM/AMF problems(like #1977), then retrying of TIMEOUT will again do si-swap operation. Retrying of si-swap should be avoided, when the return code is ERR_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.-- ___ Opensaf-tickets mailing list Opensaf-tickets@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
[tickets] [opensaf:tickets] #2056 imm: ccb is not aborted when OI gracefully disconnects
- **status**: review --> fixed - **Milestone**: 4.7.2 --> 5.0.1 - **Comment**: changeset: 8167:b6c4232b17f2 branch: opensaf-5.0.x parent: 8164:5b2a3c287e31 user:Neelakanta Reddy date:Fri Sep 30 10:12:41 2016 +0530 summary: imm:abort the uncommited ccbs when the implementer gracefully disconnects [#2056] changeset: 8168:31a68ac3cd9a branch: opensaf-5.1.x parent: 8165:b7ab66396f9b user:Neelakanta Reddy date:Fri Sep 30 10:12:41 2016 +0530 summary: imm:abort the uncommited ccbs when the implementer gracefully disconnects [#2056] changeset: 8169:c7be50036b8c tag: tip parent: 8166:41ddae2ba01d user:Neelakanta Reddy date:Fri Sep 30 10:12:41 2016 +0530 summary: imm:abort the uncommited ccbs when the implementer gracefully disconnects [#2056] --- ** [tickets:#2056] imm: ccb is not aborted when OI gracefully disconnects** **Status:** fixed **Milestone:** 5.0.1 **Created:** Wed Sep 21, 2016 10:58 AM UTC by Hung Nguyen **Last Updated:** Mon Sep 26, 2016 09:23 AM UTC **Owner:** Neelakanta Reddy **Attachments:** - [logs.7z](https://sourceforge.net/p/opensaf/tickets/2056/attachment/logs.7z) (201.2 kB; application/octet-stream) Reproduce steps: 1. Start OI 2. Create a ccb and add an operation to the ccb, leave the ccb in idle state root@SC-1:~# immcfg \> immcfg -c Test test=1 \> 3. Disconnect OI gracefully with OiImplementerClear() and OiFinalize() 4. Try to connect the OI again and OiImplementerSet() keeps failing with ERR_TRY_AGAIN If we roughly kill the OI in step 3, the ccb will be aborted and the OI can attach again. So there's a difference between roughly disconnecting and gracefully disconnecting the OI. Attached is logs and traces. ~~~ 17:30:43.168638 osafimmnd [2556:immsv_evt.c:5422] T8 Received: IMMND_EVT_D2ND_IMPLSET_RSP (60) from 0 17:30:43.168646 osafimmnd [2556:immnd_evt.c:9865] T2 originated here?:1 nodeId:2010f conn: 190 17:30:43.168653 osafimmnd [2556:ImmModel.cc:14309] >> implementerSet 17:30:43.168694 osafimmnd [2556:ImmModel.cc:14369] T7 Re-using implementer for testoi 17:30:43.168706 osafimmnd [2556:ImmModel.cc:14389] TR TRY_AGAIN: ccb 2 is active on object 'test=1' bound to OI name 'testoi'. Can not set re-attach implementer ~~~ --- 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] #2058 smf: slow joining node may flood syslog at the time of upgrade
- **status**: accepted --> fixed - **Comment**: changeset: 8170:20b4d2bb8bc0 branch: opensaf-5.1.x parent: 8168:31a68ac3cd9a user:Neelakanta Reddy date:Fri Sep 30 10:20:07 2016 +0530 summary: smf: Avoid flooding of syslog when the upgrade involves node reboot [#2058] changeset: 8171:ab0c13244507 tag: tip parent: 8169:c7be50036b8c user:Neelakanta Reddy date:Fri Sep 30 10:20:07 2016 +0530 summary: smf: Avoid flooding of syslog when the upgrade involves node reboot [#2058] --- ** [tickets:#2058] smf: slow joining node may flood syslog at the time of upgrade** **Status:** fixed **Milestone:** 5.1.1 **Created:** Thu Sep 22, 2016 05:56 AM UTC by Neelakanta Reddy **Last Updated:** Tue Sep 27, 2016 12:34 PM UTC **Owner:** Neelakanta Reddy Sep 20 19:00:06 SC-2-1 osafsmfd[4039]: NO SmfUpgradeStep::nodeReboot: Waiting to get node destination with increased UP counter Sep 20 19:00:06 SC-2-1 osafsmfd[4039]: NO getNodeDestination: className 'SaAmfNode' Sep 20 19:00:06 SC-2-1 osafsmfd[4039]: NO getNodeDestination: className 'SaAmfNode' Sep 20 19:00:06 SC-2-1 osafsmfd[4039]: NO getNodeDestination: className 'SaAmfNode' Sep 20 19:00:06 SC-2-1 osafsmfd[4039]: NO getNodeDestination: className 'SaAmfNode' ... Sep 20 19:00:09 SC-2-1 osafsmfd[4039]: NO getNodeDestination: className 'SaAmfNode' At the time of uprade, when the rebooted node joined is slow, syslog may get flooded. --- 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] #2085 CKPT : IMM attributes for ckpt table are increased by 1, when ckpt open returns TIME_OUT
--- ** [tickets:#2085] CKPT : IMM attributes for ckpt table are increased by 1, when ckpt open returns TIME_OUT** **Status:** unassigned **Milestone:** 4.7.2 **Created:** Fri Sep 30, 2016 05:13 AM UTC by Srikanth R **Last Updated:** Fri Sep 30, 2016 05:13 AM UTC **Owner:** nobody Changeset : 7997 5.1.FC IMM attributes for ckpt table are increased by 1, when ckpt open returns TIME_OUT. Below is the flow of steps in which how application uses CKPT. -> Initialize with ckpt with callbacks. API returned SA_AIS_OK -> Invoke selection object. API returned SA_AIS_OK -> Create a checkpoint using async option. API returned SA_AIS_OK -> Kill ckpnd process. -> Check for the callbacks and check the IMM attribute of CKPT object. Callback is invoked, in which return value is ERR_TIMEOUT. Spec mandates that, api should be called again to check whether checkpoint creation is successful or not. If the further call returns ERR_EXIST, the previous call is successful or the further call returns SA_AIS_OK, the previous call is unsuccessful. -> As the callback returned SA_AIS_ERR_TIMEOUT, invoked the checkpoint creation api async again. This time, api and both callback returned SA_AIS_OK. Now if you check the attributes for CKPT table object, the attributes saCkptCheckpointNumOpeners, saCkptCheckpointNumReaders and saCkptCheckpointNumWriters are having a value of 2, instead of expected value 1. --- 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] #1895 ntf: ER in syslog: ER NtfAdmin::subscriptionRemoved client 12 not found
- **status**: review --> fixed - **Part**: - --> d - **Comment**: changeset: 8161:29d4c2663f21 parent: 8156:1682135e7ba9 user:Canh Van Truong date:Thu Sep 29 10:52:12 2016 +0530 summary: ntfs: convert LOG_ER to LOG_WA [#1895] changeset: 8160:b54026b7ee72 branch: opensaf-5.1.x parent: 8157:1b00775bd22b user:Canh Van Truong date:Thu Sep 29 10:51:45 2016 +0530 summary: ntfs: convert LOG_ER to LOG_WA [#1895] changeset: 8159:abe3b25790a7 branch: opensaf-5.0.x user:Canh Van Truong date:Thu Sep 29 10:51:12 2016 +0530 summary: ntfs: convert LOG_ER to LOG_WA [#1895] --- ** [tickets:#1895] ntf: ER in syslog: ER NtfAdmin::subscriptionRemoved client 12 not found** **Status:** fixed **Milestone:** 5.0.2 **Created:** Fri Jun 24, 2016 03:24 AM UTC by Vo Minh Hoang **Last Updated:** Thu Sep 22, 2016 08:45 AM UTC **Owner:** Canh Truong **Attachments:** - [1895.tgz](https://sourceforge.net/p/opensaf/tickets/1895/attachment/1895.tgz) (471.5 kB; application/x-compressed) Failed when run test suit 2: Sep 15 11:13:41.191010 osafntfd [476:mds_dt_trans.c:0608] >> mdtm_process_poll_recv_data_tcp Sep 15 11:13:41.191034 osafntfd [476:mbcsv_mds.c:0244] << mbcsv_mds_send_msg: success Sep 15 11:13:41.191038 osafntfd [476:mbcsv_util.c:0492] << mbcsv_send_ckpt_data_to_all_peers Sep 15 11:13:41.191041 osafntfd [476:mbcsv_api.c:0868] << mbcsv_process_snd_ckpt_request: retval: 1 Sep 15 11:13:41.191044 osafntfd [476:ntfs_mbcsv.c:1365] << ntfs_send_async_update Sep 15 11:13:41.191047 osafntfd [476:ntfs_com.c:0093] << client_removed_res_lib Sep 15 11:13:41.191049 osafntfd [476:ntfs_evt.c:0304] << proc_finalize_msg Sep 15 11:13:41.191055 osafntfd [476:ntfs_evt.c:0357] >> proc_unsubscribe_msg: client_id 8, subscriptionId 111 Sep 15 11:13:41.191140 osafntfd [476:NtfAdmin.cc:0520] ER NtfAdmin::subscriptionRemoved client 8 not found Sep 15 11:13:41.191146 osafntfd [476:ntfs_evt.c:0369] << proc_unsubscribe_msg The issue here is when test case 4 of test suit2 is executed, the unsubcribe and Finalize is runing in parallel. Ntfd receive API request from Finalize before unsubcribe, so client and all of relating to its will be removed before ntfd process request from ubsubcribe. The error is printed out in this case. And unsubcribe action is failed. But in the test case the return code is re-assigned to ok for test case passed. Similiar ticket: https://sourceforge.net/p/opensaf/tickets/1818/ --- 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] #2086 LCK : Lock waiter callbacks are not invoked after glnd restart
--- ** [tickets:#2086] LCK : Lock waiter callbacks are not invoked after glnd restart** **Status:** unassigned **Milestone:** 4.7.2 **Created:** Fri Sep 30, 2016 06:10 AM UTC by Srikanth R **Last Updated:** Fri Sep 30, 2016 06:10 AM UTC **Owner:** nobody Changeset : 7997 5.1.FC Lock waiter callbacks are not invoked after glnd restart. Below are the steps performed as part of application. -> Initialize with LCK and store as handle 1. -> Initialize with LCK and store as handle 2 in another thread. -> Open a lock using saLckResourceOpen with handle1 -> Open the same lock using saLckResourceOpen with handle2 -> With handle 2, request lock in PR mode using saLckResourceOpen api. Call this api 5 times. -> WIth handle 1, request lock in EX mode, As the handle 2 has requested the lock 5 times, the thread for handle 1 should get 5 lock waiter callbacks. Some times, lock waiter callback is not invoked for the thread using handle 1. --- 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] #1944 amf: two actives for same SI after sufailover recovery during su lock/shutdown, NWAY.
- **status**: accepted --> review --- ** [tickets:#1944] amf: two actives for same SI after sufailover recovery during su lock/shutdown, NWAY.** **Status:** review **Milestone:** 5.0.2 **Created:** Tue Aug 09, 2016 09:23 AM UTC by Praveen **Last Updated:** Tue Sep 20, 2016 05:59 PM UTC **Owner:** Praveen **Attachments:** - [two_actives.tgz](https://sourceforge.net/p/opensaf/tickets/1944/attachment/two_actives.tgz) (69.1 kB; application/x-compressed) Attached are traces and conf. steps to reproduce: 1)Bring the configuration up. 2)Lock active SU. 3)While processing remove callback, one comp must fault sufailover recovery. 4)Amf will make Su3 also active for both the SIs when Su2 is already make active after quiesced assignments. Assignments before su lock safSISU=safSu=SU2\,safSg=AmfDemo\,safApp=AmfDemo1,safSi=AmfDemo,safApp=AmfDemo1 saAmfSISUHAState=STANDBY(2) safSISU=safSu=SU2\,safSg=AmfDemo\,safApp=AmfDemo1,safSi=AmfDemo1,safApp=AmfDemo1 saAmfSISUHAState=STANDBY(2) safSISU=safSu=SU3\,safSg=AmfDemo\,safApp=AmfDemo1,safSi=AmfDemo,safApp=AmfDemo1 saAmfSISUHAState=STANDBY(2) safSISU=safSu=SU3\,safSg=AmfDemo\,safApp=AmfDemo1,safSi=AmfDemo1,safApp=AmfDemo1 saAmfSISUHAState=STANDBY(2) safSISU=safSu=SU1\,safSg=AmfDemo\,safApp=AmfDemo1,safSi=AmfDemo,safApp=AmfDemo1 saAmfSISUHAState=ACTIVE(1) safSISU=safSu=SU1\,safSg=AmfDemo\,safApp=AmfDemo1,safSi=AmfDemo1,safApp=AmfDemo1 saAmfSISUHAState=ACTIVE(1) Assignments after SU lock: safSISU=safSu=SU2\,safSg=AmfDemo\,safApp=AmfDemo1,safSi=AmfDemo,safApp=AmfDemo1 saAmfSISUHAState=ACTIVE(1) safSISU=safSu=SU2\,safSg=AmfDemo\,safApp=AmfDemo1,safSi=AmfDemo1,safApp=AmfDemo1 saAmfSISUHAState=ACTIVE(1) safSISU=safSu=SU3\,safSg=AmfDemo\,safApp=AmfDemo1,safSi=AmfDemo,safApp=AmfDemo1 saAmfSISUHAState=ACTIVE(1) safSISU=safSu=SU3\,safSg=AmfDemo\,safApp=AmfDemo1,safSi=AmfDemo1,safApp=AmfDemo1 saAmfSISUHAState=ACTIVE(1) Issue will be applicable to Nore lock/shutdown 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.-- ___ Opensaf-tickets mailing list Opensaf-tickets@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
