[tickets] [opensaf:tickets] #702 IMMTOOLS: creating an object using immcfg crashes when RDN value has a DN of an associated object
--- ** [tickets:#702] IMMTOOLS: creating an object using immcfg crashes when RDN value has a DN of an associated object** **Status:** assigned **Created:** Thu Jan 02, 2014 10:05 AM UTC by Zoran Milinkovic **Last Updated:** Thu Jan 02, 2014 10:05 AM UTC **Owner:** Zoran Milinkovic When trying to create a new object, which does not have a parent DN, and its RDN value has a DN of an associated object, immcfg crashes. Example: $ immcfg -c TestClass 'id=testid=1\,testid=5' Segmentation fault (core dumped) --- 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.-- Rapidly troubleshoot problems before they affect your business. Most IT organizations don't have a clear picture of how application performance affects their revenue. With AppDynamics, you get 100% visibility into your Java,.NET, PHP application. Start your 15-day FREE TRIAL of AppDynamics Pro! http://pubads.g.doubleclick.net/gampad/clk?id=84349831iu=/4140/ostg.clktrk___ Opensaf-tickets mailing list Opensaf-tickets@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
[tickets] [opensaf:tickets] #696 Application SUs do not get assignments if a failover happens when the cluster startup timer is running
- **status**: unassigned -- assigned - **assigned_to**: Nagendra Kumar --- ** [tickets:#696] Application SUs do not get assignments if a failover happens when the cluster startup timer is running** **Status:** assigned **Created:** Thu Dec 26, 2013 06:42 AM UTC by Sirisha Alla **Last Updated:** Thu Dec 26, 2013 06:42 AM UTC **Owner:** Nagendra Kumar The issue is observed on changeset 4733 + #220 patches corresponding to cs 4741 and cs 4742. The test setup is a 4 node SLES 64bit VMs.The setup is single PBE enabled loaded with 25k objects. This issue is always reproducible. Following are the steps: 1) Configure the application and set the cluster startup timer to some higher value than default say 200 seconds. 2) Reboot the cluster, bring up SC-1, SC-2 and PL-3 before timer expires. Do not bring PL-4 up. Since the entire cluster is not up, cluster startup timer will be running. 3) Before the expiry of cluster startup timer, reboot the active controller. Following are the logs: SLES-64BIT-SLOT2:~ # immlist safAmfCluster=myAmfCluster Name Type Value(s) safAmfCluster SA_STRING_T safAmfCluster=myAmfCluster saAmfClusterStartupTimeout SA_TIME_T2000 (0x2e90edd000, Thu Jan 1 05:33:20 1970) saAmfClusterClmCluster SA_NAME_T safCluster=myClmCluster (23) saAmfClusterAdminState SA_UINT32_T 1 (0x1) SaImmAttrImplementerName SA_STRING_T safAmfService SaImmAttrClassName SA_STRING_T SaAmfCluster SaImmAttrAdminOwnerNameSA_STRING_T IMMLOADER Active Controller syslog: Dec 26 11:07:15 SLES-64BIT-SLOT1 osafamfnd[4698]: NO Assigned 'safSi=SC-2N,safApp=OpenSAF' ACTIVE to 'safSu=SC-1,safSg=2N,safApp=OpenSAF' Dec 26 11:07:15 SLES-64BIT-SLOT1 opensafd: OpenSAF(4.4.M0) services successfully started Dec 26 11:07:15 SLES-64BIT-SLOT1 osafamfnd[4698]: NO 'safSu=SU1,safSg=AmfDemo,safApp=AmfDemo' Presence State UNINSTANTIATED = INSTANTIATING some thing is spawnd instantiate for safComp=AmfDemo1,safSu=SU1,safSg=AmfDemo,safApp=AmfDemo Dec 26 11:07:16 SLES-64BIT-SLOT1 osafamfd[4688]: NO Node 'PL-3' joined the cluster Dec 26 11:07:16 SLES-64BIT-SLOT1 osafamfd[4688]: NO Node 'SC-2' joined the cluster Dec 26 11:07:16 SLES-64BIT-SLOT1 osafimmd[4608]: NO Successfully announced dump at node 2010f. New Epoch:81 Dec 26 11:07:16 SLES-64BIT-SLOT1 osafimmnd[4618]: NO Epoch set to 81 in ImmModel Dec 26 11:07:16 SLES-64BIT-SLOT1 osafimmd[4608]: NO ACT: New Epoch for IMMND process at node 2020f old epoch: 80 new epoch:81 Dec 26 11:07:16 SLES-64BIT-SLOT1 osafimmd[4608]: NO ACT: New Epoch for IMMND process at node 2030f old epoch: 80 new epoch:81 Dec 26 11:07:16 SLES-64BIT-SLOT1 osafimmnd[4618]: NO Implementer connected: 14 (MsgQueueService131855) 0, 2030f Dec 26 11:07:17 SLES-64BIT-SLOT1 osafimmnd[4618]: NO Implementer connected: 15 (MsgQueueService131599) 0, 2020f some thing is spawnd instantiate for safComp=AmfDemo2,safSu=SU1,safSg=AmfDemo,safApp=AmfDemo Dec 26 11:07:20 SLES-64BIT-SLOT1 osafamfnd[4698]: NO 'safSu=SU1,safSg=AmfDemo,safApp=AmfDemo' Presence State INSTANTIATING = INSTANTIATED . Dec 26 11:07:49 SLES-64BIT-SLOT1 shutdown[4918]: shutting down for system reboot Dec 26 11:07:49 SLES-64BIT-SLOT1 init: Switching to runlevel: 6 Dec 26 11:07:50 SLES-64BIT-SLOT1 kernel: [ 2465.822609] bootsplash: status on console 0 changed to on Dec 26 11:07:50 SLES-64BIT-SLOT1 opensafd: Stopping OpenSAF Services After the cluster startup timer completion following is the status. SLES-64BIT-SLOT2:~ # date; amf-state siass Thu Dec 26 11:20:12 IST 2013 safSISU=safSu=SC-2\,safSg=NoRed\,safApp=OpenSAF,safSi=NoRed3,safApp=OpenSAF saAmfSISUHAState=ACTIVE(1) saAmfSISUHAReadinessState=READY_FOR_ASSIGNMENT(1) safSISU=safSu=PL-3\,safSg=NoRed\,safApp=OpenSAF,safSi=NoRed2,safApp=OpenSAF saAmfSISUHAState=ACTIVE(1) saAmfSISUHAReadinessState=READY_FOR_ASSIGNMENT(1) safSISU=safSu=SC-1\,safSg=2N\,safApp=OpenSAF,safSi=SC-2N,safApp=OpenSAF saAmfSISUHAState=STANDBY(2) saAmfSISUHAReadinessState=READY_FOR_ASSIGNMENT(1) safSISU=safSu=SC-1\,safSg=NoRed\,safApp=OpenSAF,safSi=NoRed1,safApp=OpenSAF saAmfSISUHAState=ACTIVE(1) saAmfSISUHAReadinessState=READY_FOR_ASSIGNMENT(1) safSISU=safSu=SC-2\,safSg=2N\,safApp=OpenSAF,safSi=SC-2N,safApp=OpenSAF saAmfSISUHAState=ACTIVE(1) saAmfSISUHAReadinessState=READY_FOR_ASSIGNMENT(1) SLES-64BIT-SLOT2:~ # amf-state su safSu=SC-1,safSg=2N,safApp=OpenSAF saAmfSUAdminState=UNLOCKED(1) saAmfSUOperState=ENABLED(1) saAmfSUPresenceState=INSTANTIATED(3) saAmfSUReadinessState=IN-SERVICE(2) safSu=SC-2,safSg=2N,safApp=OpenSAF
[tickets] [opensaf:tickets] #696 Application SUs do not get assignments if a failover happens when the cluster startup timer is running
- **status**: assigned -- wontfix - **Type**: defect -- enhancement - **Milestone**: future -- 4.4.FC --- ** [tickets:#696] Application SUs do not get assignments if a failover happens when the cluster startup timer is running** **Status:** wontfix **Created:** Thu Dec 26, 2013 06:42 AM UTC by Sirisha Alla **Last Updated:** Thu Jan 02, 2014 11:11 AM UTC **Owner:** Nagendra Kumar The issue is observed on changeset 4733 + #220 patches corresponding to cs 4741 and cs 4742. The test setup is a 4 node SLES 64bit VMs.The setup is single PBE enabled loaded with 25k objects. This issue is always reproducible. Following are the steps: 1) Configure the application and set the cluster startup timer to some higher value than default say 200 seconds. 2) Reboot the cluster, bring up SC-1, SC-2 and PL-3 before timer expires. Do not bring PL-4 up. Since the entire cluster is not up, cluster startup timer will be running. 3) Before the expiry of cluster startup timer, reboot the active controller. Following are the logs: SLES-64BIT-SLOT2:~ # immlist safAmfCluster=myAmfCluster Name Type Value(s) safAmfCluster SA_STRING_T safAmfCluster=myAmfCluster saAmfClusterStartupTimeout SA_TIME_T2000 (0x2e90edd000, Thu Jan 1 05:33:20 1970) saAmfClusterClmCluster SA_NAME_T safCluster=myClmCluster (23) saAmfClusterAdminState SA_UINT32_T 1 (0x1) SaImmAttrImplementerName SA_STRING_T safAmfService SaImmAttrClassName SA_STRING_T SaAmfCluster SaImmAttrAdminOwnerNameSA_STRING_T IMMLOADER Active Controller syslog: Dec 26 11:07:15 SLES-64BIT-SLOT1 osafamfnd[4698]: NO Assigned 'safSi=SC-2N,safApp=OpenSAF' ACTIVE to 'safSu=SC-1,safSg=2N,safApp=OpenSAF' Dec 26 11:07:15 SLES-64BIT-SLOT1 opensafd: OpenSAF(4.4.M0) services successfully started Dec 26 11:07:15 SLES-64BIT-SLOT1 osafamfnd[4698]: NO 'safSu=SU1,safSg=AmfDemo,safApp=AmfDemo' Presence State UNINSTANTIATED = INSTANTIATING some thing is spawnd instantiate for safComp=AmfDemo1,safSu=SU1,safSg=AmfDemo,safApp=AmfDemo Dec 26 11:07:16 SLES-64BIT-SLOT1 osafamfd[4688]: NO Node 'PL-3' joined the cluster Dec 26 11:07:16 SLES-64BIT-SLOT1 osafamfd[4688]: NO Node 'SC-2' joined the cluster Dec 26 11:07:16 SLES-64BIT-SLOT1 osafimmd[4608]: NO Successfully announced dump at node 2010f. New Epoch:81 Dec 26 11:07:16 SLES-64BIT-SLOT1 osafimmnd[4618]: NO Epoch set to 81 in ImmModel Dec 26 11:07:16 SLES-64BIT-SLOT1 osafimmd[4608]: NO ACT: New Epoch for IMMND process at node 2020f old epoch: 80 new epoch:81 Dec 26 11:07:16 SLES-64BIT-SLOT1 osafimmd[4608]: NO ACT: New Epoch for IMMND process at node 2030f old epoch: 80 new epoch:81 Dec 26 11:07:16 SLES-64BIT-SLOT1 osafimmnd[4618]: NO Implementer connected: 14 (MsgQueueService131855) 0, 2030f Dec 26 11:07:17 SLES-64BIT-SLOT1 osafimmnd[4618]: NO Implementer connected: 15 (MsgQueueService131599) 0, 2020f some thing is spawnd instantiate for safComp=AmfDemo2,safSu=SU1,safSg=AmfDemo,safApp=AmfDemo Dec 26 11:07:20 SLES-64BIT-SLOT1 osafamfnd[4698]: NO 'safSu=SU1,safSg=AmfDemo,safApp=AmfDemo' Presence State INSTANTIATING = INSTANTIATED . Dec 26 11:07:49 SLES-64BIT-SLOT1 shutdown[4918]: shutting down for system reboot Dec 26 11:07:49 SLES-64BIT-SLOT1 init: Switching to runlevel: 6 Dec 26 11:07:50 SLES-64BIT-SLOT1 kernel: [ 2465.822609] bootsplash: status on console 0 changed to on Dec 26 11:07:50 SLES-64BIT-SLOT1 opensafd: Stopping OpenSAF Services After the cluster startup timer completion following is the status. SLES-64BIT-SLOT2:~ # date; amf-state siass Thu Dec 26 11:20:12 IST 2013 safSISU=safSu=SC-2\,safSg=NoRed\,safApp=OpenSAF,safSi=NoRed3,safApp=OpenSAF saAmfSISUHAState=ACTIVE(1) saAmfSISUHAReadinessState=READY_FOR_ASSIGNMENT(1) safSISU=safSu=PL-3\,safSg=NoRed\,safApp=OpenSAF,safSi=NoRed2,safApp=OpenSAF saAmfSISUHAState=ACTIVE(1) saAmfSISUHAReadinessState=READY_FOR_ASSIGNMENT(1) safSISU=safSu=SC-1\,safSg=2N\,safApp=OpenSAF,safSi=SC-2N,safApp=OpenSAF saAmfSISUHAState=STANDBY(2) saAmfSISUHAReadinessState=READY_FOR_ASSIGNMENT(1) safSISU=safSu=SC-1\,safSg=NoRed\,safApp=OpenSAF,safSi=NoRed1,safApp=OpenSAF saAmfSISUHAState=ACTIVE(1) saAmfSISUHAReadinessState=READY_FOR_ASSIGNMENT(1) safSISU=safSu=SC-2\,safSg=2N\,safApp=OpenSAF,safSi=SC-2N,safApp=OpenSAF saAmfSISUHAState=ACTIVE(1) saAmfSISUHAReadinessState=READY_FOR_ASSIGNMENT(1) SLES-64BIT-SLOT2:~ # amf-state su safSu=SC-1,safSg=2N,safApp=OpenSAF saAmfSUAdminState=UNLOCKED(1) saAmfSUOperState=ENABLED(1) saAmfSUPresenceState=INSTANTIATED(3) saAmfSUReadinessState=IN-SERVICE(2) safSu=SC-2,safSg=2N,safApp=OpenSAF
[tickets] [opensaf:tickets] #696 Application SUs do not get assignments if a failover happens when the cluster startup timer is running
Since the cluster is not ready for assignment, failover and switchover are not supported. This has been documented at: 2.2.2 Compliance Report, section 8: Section 8.7: saAmfClusterStartupTimeout: 1. The timer will stop prematurely when all of the below conditions are achieved: All the configured nodes have joined the cluster. All the SUs eligible for instantiation are moved to either instantiated state (and hence operational state become enable) or moved to instantiation/termination failed state. 2. Before the timer expiry, failover and switchover are not supported. --- ** [tickets:#696] Application SUs do not get assignments if a failover happens when the cluster startup timer is running** **Status:** wontfix **Created:** Thu Dec 26, 2013 06:42 AM UTC by Sirisha Alla **Last Updated:** Thu Jan 02, 2014 11:11 AM UTC **Owner:** Nagendra Kumar The issue is observed on changeset 4733 + #220 patches corresponding to cs 4741 and cs 4742. The test setup is a 4 node SLES 64bit VMs.The setup is single PBE enabled loaded with 25k objects. This issue is always reproducible. Following are the steps: 1) Configure the application and set the cluster startup timer to some higher value than default say 200 seconds. 2) Reboot the cluster, bring up SC-1, SC-2 and PL-3 before timer expires. Do not bring PL-4 up. Since the entire cluster is not up, cluster startup timer will be running. 3) Before the expiry of cluster startup timer, reboot the active controller. Following are the logs: SLES-64BIT-SLOT2:~ # immlist safAmfCluster=myAmfCluster Name Type Value(s) safAmfCluster SA_STRING_T safAmfCluster=myAmfCluster saAmfClusterStartupTimeout SA_TIME_T2000 (0x2e90edd000, Thu Jan 1 05:33:20 1970) saAmfClusterClmCluster SA_NAME_T safCluster=myClmCluster (23) saAmfClusterAdminState SA_UINT32_T 1 (0x1) SaImmAttrImplementerName SA_STRING_T safAmfService SaImmAttrClassName SA_STRING_T SaAmfCluster SaImmAttrAdminOwnerNameSA_STRING_T IMMLOADER Active Controller syslog: Dec 26 11:07:15 SLES-64BIT-SLOT1 osafamfnd[4698]: NO Assigned 'safSi=SC-2N,safApp=OpenSAF' ACTIVE to 'safSu=SC-1,safSg=2N,safApp=OpenSAF' Dec 26 11:07:15 SLES-64BIT-SLOT1 opensafd: OpenSAF(4.4.M0) services successfully started Dec 26 11:07:15 SLES-64BIT-SLOT1 osafamfnd[4698]: NO 'safSu=SU1,safSg=AmfDemo,safApp=AmfDemo' Presence State UNINSTANTIATED = INSTANTIATING some thing is spawnd instantiate for safComp=AmfDemo1,safSu=SU1,safSg=AmfDemo,safApp=AmfDemo Dec 26 11:07:16 SLES-64BIT-SLOT1 osafamfd[4688]: NO Node 'PL-3' joined the cluster Dec 26 11:07:16 SLES-64BIT-SLOT1 osafamfd[4688]: NO Node 'SC-2' joined the cluster Dec 26 11:07:16 SLES-64BIT-SLOT1 osafimmd[4608]: NO Successfully announced dump at node 2010f. New Epoch:81 Dec 26 11:07:16 SLES-64BIT-SLOT1 osafimmnd[4618]: NO Epoch set to 81 in ImmModel Dec 26 11:07:16 SLES-64BIT-SLOT1 osafimmd[4608]: NO ACT: New Epoch for IMMND process at node 2020f old epoch: 80 new epoch:81 Dec 26 11:07:16 SLES-64BIT-SLOT1 osafimmd[4608]: NO ACT: New Epoch for IMMND process at node 2030f old epoch: 80 new epoch:81 Dec 26 11:07:16 SLES-64BIT-SLOT1 osafimmnd[4618]: NO Implementer connected: 14 (MsgQueueService131855) 0, 2030f Dec 26 11:07:17 SLES-64BIT-SLOT1 osafimmnd[4618]: NO Implementer connected: 15 (MsgQueueService131599) 0, 2020f some thing is spawnd instantiate for safComp=AmfDemo2,safSu=SU1,safSg=AmfDemo,safApp=AmfDemo Dec 26 11:07:20 SLES-64BIT-SLOT1 osafamfnd[4698]: NO 'safSu=SU1,safSg=AmfDemo,safApp=AmfDemo' Presence State INSTANTIATING = INSTANTIATED . Dec 26 11:07:49 SLES-64BIT-SLOT1 shutdown[4918]: shutting down for system reboot Dec 26 11:07:49 SLES-64BIT-SLOT1 init: Switching to runlevel: 6 Dec 26 11:07:50 SLES-64BIT-SLOT1 kernel: [ 2465.822609] bootsplash: status on console 0 changed to on Dec 26 11:07:50 SLES-64BIT-SLOT1 opensafd: Stopping OpenSAF Services After the cluster startup timer completion following is the status. SLES-64BIT-SLOT2:~ # date; amf-state siass Thu Dec 26 11:20:12 IST 2013 safSISU=safSu=SC-2\,safSg=NoRed\,safApp=OpenSAF,safSi=NoRed3,safApp=OpenSAF saAmfSISUHAState=ACTIVE(1) saAmfSISUHAReadinessState=READY_FOR_ASSIGNMENT(1) safSISU=safSu=PL-3\,safSg=NoRed\,safApp=OpenSAF,safSi=NoRed2,safApp=OpenSAF saAmfSISUHAState=ACTIVE(1) saAmfSISUHAReadinessState=READY_FOR_ASSIGNMENT(1) safSISU=safSu=SC-1\,safSg=2N\,safApp=OpenSAF,safSi=SC-2N,safApp=OpenSAF saAmfSISUHAState=STANDBY(2) saAmfSISUHAReadinessState=READY_FOR_ASSIGNMENT(1) safSISU=safSu=SC-1\,safSg=NoRed\,safApp=OpenSAF,safSi=NoRed1,safApp=OpenSAF saAmfSISUHAState=ACTIVE(1)
[tickets] [opensaf:tickets] #76 AMF: if all nodes have joined the cluster, cancel the assignment timer and assign anyway
Updated documentation: changeset: 76:0e1b2405dbbe tag: tip user:Nagendra Kumarnagendr...@oracle.com date:Thu Jan 02 16:47:49 2014 +0530 summary: amf: describe premature cluster timer expiry condition [#76] --- ** [tickets:#76] AMF: if all nodes have joined the cluster, cancel the assignment timer and assign anyway** **Status:** fixed **Created:** Mon May 13, 2013 04:25 AM UTC by Nagendra Kumar **Last Updated:** Tue Dec 03, 2013 12:25 PM UTC **Owner:** Nagendra Kumar Migrated from http://devel.opensaf.org/ticket/1791 If all nodes have joined the cluster there is no need to wait for the cluster startup timer to expire. --- 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.-- Rapidly troubleshoot problems before they affect your business. Most IT organizations don't have a clear picture of how application performance affects their revenue. With AppDynamics, you get 100% visibility into your Java,.NET, PHP application. Start your 15-day FREE TRIAL of AppDynamics Pro! http://pubads.g.doubleclick.net/gampad/clk?id=84349831iu=/4140/ostg.clktrk___ Opensaf-tickets mailing list Opensaf-tickets@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
[tickets] [opensaf:tickets] #696 Application SUs do not get assignments if a failover happens when the cluster startup timer is running
committed as changeset: 76:0e1b2405dbbe tag: tip user:Nagendra Kumarnagendr...@oracle.com date:Thu Jan 02 16:47:49 2014 +0530 summary: amf: describe premature cluster timer expiry condition [#76] --- ** [tickets:#696] Application SUs do not get assignments if a failover happens when the cluster startup timer is running** **Status:** wontfix **Created:** Thu Dec 26, 2013 06:42 AM UTC by Sirisha Alla **Last Updated:** Thu Jan 02, 2014 11:14 AM UTC **Owner:** Nagendra Kumar The issue is observed on changeset 4733 + #220 patches corresponding to cs 4741 and cs 4742. The test setup is a 4 node SLES 64bit VMs.The setup is single PBE enabled loaded with 25k objects. This issue is always reproducible. Following are the steps: 1) Configure the application and set the cluster startup timer to some higher value than default say 200 seconds. 2) Reboot the cluster, bring up SC-1, SC-2 and PL-3 before timer expires. Do not bring PL-4 up. Since the entire cluster is not up, cluster startup timer will be running. 3) Before the expiry of cluster startup timer, reboot the active controller. Following are the logs: SLES-64BIT-SLOT2:~ # immlist safAmfCluster=myAmfCluster Name Type Value(s) safAmfCluster SA_STRING_T safAmfCluster=myAmfCluster saAmfClusterStartupTimeout SA_TIME_T2000 (0x2e90edd000, Thu Jan 1 05:33:20 1970) saAmfClusterClmCluster SA_NAME_T safCluster=myClmCluster (23) saAmfClusterAdminState SA_UINT32_T 1 (0x1) SaImmAttrImplementerName SA_STRING_T safAmfService SaImmAttrClassName SA_STRING_T SaAmfCluster SaImmAttrAdminOwnerNameSA_STRING_T IMMLOADER Active Controller syslog: Dec 26 11:07:15 SLES-64BIT-SLOT1 osafamfnd[4698]: NO Assigned 'safSi=SC-2N,safApp=OpenSAF' ACTIVE to 'safSu=SC-1,safSg=2N,safApp=OpenSAF' Dec 26 11:07:15 SLES-64BIT-SLOT1 opensafd: OpenSAF(4.4.M0) services successfully started Dec 26 11:07:15 SLES-64BIT-SLOT1 osafamfnd[4698]: NO 'safSu=SU1,safSg=AmfDemo,safApp=AmfDemo' Presence State UNINSTANTIATED = INSTANTIATING some thing is spawnd instantiate for safComp=AmfDemo1,safSu=SU1,safSg=AmfDemo,safApp=AmfDemo Dec 26 11:07:16 SLES-64BIT-SLOT1 osafamfd[4688]: NO Node 'PL-3' joined the cluster Dec 26 11:07:16 SLES-64BIT-SLOT1 osafamfd[4688]: NO Node 'SC-2' joined the cluster Dec 26 11:07:16 SLES-64BIT-SLOT1 osafimmd[4608]: NO Successfully announced dump at node 2010f. New Epoch:81 Dec 26 11:07:16 SLES-64BIT-SLOT1 osafimmnd[4618]: NO Epoch set to 81 in ImmModel Dec 26 11:07:16 SLES-64BIT-SLOT1 osafimmd[4608]: NO ACT: New Epoch for IMMND process at node 2020f old epoch: 80 new epoch:81 Dec 26 11:07:16 SLES-64BIT-SLOT1 osafimmd[4608]: NO ACT: New Epoch for IMMND process at node 2030f old epoch: 80 new epoch:81 Dec 26 11:07:16 SLES-64BIT-SLOT1 osafimmnd[4618]: NO Implementer connected: 14 (MsgQueueService131855) 0, 2030f Dec 26 11:07:17 SLES-64BIT-SLOT1 osafimmnd[4618]: NO Implementer connected: 15 (MsgQueueService131599) 0, 2020f some thing is spawnd instantiate for safComp=AmfDemo2,safSu=SU1,safSg=AmfDemo,safApp=AmfDemo Dec 26 11:07:20 SLES-64BIT-SLOT1 osafamfnd[4698]: NO 'safSu=SU1,safSg=AmfDemo,safApp=AmfDemo' Presence State INSTANTIATING = INSTANTIATED . Dec 26 11:07:49 SLES-64BIT-SLOT1 shutdown[4918]: shutting down for system reboot Dec 26 11:07:49 SLES-64BIT-SLOT1 init: Switching to runlevel: 6 Dec 26 11:07:50 SLES-64BIT-SLOT1 kernel: [ 2465.822609] bootsplash: status on console 0 changed to on Dec 26 11:07:50 SLES-64BIT-SLOT1 opensafd: Stopping OpenSAF Services After the cluster startup timer completion following is the status. SLES-64BIT-SLOT2:~ # date; amf-state siass Thu Dec 26 11:20:12 IST 2013 safSISU=safSu=SC-2\,safSg=NoRed\,safApp=OpenSAF,safSi=NoRed3,safApp=OpenSAF saAmfSISUHAState=ACTIVE(1) saAmfSISUHAReadinessState=READY_FOR_ASSIGNMENT(1) safSISU=safSu=PL-3\,safSg=NoRed\,safApp=OpenSAF,safSi=NoRed2,safApp=OpenSAF saAmfSISUHAState=ACTIVE(1) saAmfSISUHAReadinessState=READY_FOR_ASSIGNMENT(1) safSISU=safSu=SC-1\,safSg=2N\,safApp=OpenSAF,safSi=SC-2N,safApp=OpenSAF saAmfSISUHAState=STANDBY(2) saAmfSISUHAReadinessState=READY_FOR_ASSIGNMENT(1) safSISU=safSu=SC-1\,safSg=NoRed\,safApp=OpenSAF,safSi=NoRed1,safApp=OpenSAF saAmfSISUHAState=ACTIVE(1) saAmfSISUHAReadinessState=READY_FOR_ASSIGNMENT(1) safSISU=safSu=SC-2\,safSg=2N\,safApp=OpenSAF,safSi=SC-2N,safApp=OpenSAF saAmfSISUHAState=ACTIVE(1) saAmfSISUHAReadinessState=READY_FOR_ASSIGNMENT(1) SLES-64BIT-SLOT2:~ # amf-state su safSu=SC-1,safSg=2N,safApp=OpenSAF saAmfSUAdminState=UNLOCKED(1) saAmfSUOperState=ENABLED(1)
[tickets] [opensaf:tickets] #703 saAmfSUMaintenanceCampaign attribute was not set during the campaign execution.
--- ** [tickets:#703] saAmfSUMaintenanceCampaign attribute was not set during the campaign execution.** **Status:** unassigned **Created:** Thu Jan 02, 2014 11:40 AM UTC by Hrishikesh **Last Updated:** Thu Jan 02, 2014 11:40 AM UTC **Owner:** nobody Setup was installed with ChangeSet #4733 with patches from ticket#220. Application upgrade campaign which modifies compType of the components was executed. It is observed that saAmfSUMaintenanceCampaign attribute of the effected app SU is not set during the execution. === SLES1:/hostfs # smf-state camp safSmfCampaign=campaign1.xml,safApp=safSmfService state=EXECUTION_SUSPENDED(4) error='' immlist safSu=dummy_NWay_1Norm_7,safSg=SG_dummy_n,safApp=N | grep saAmfSUMaintenanceCampaign saAmfSUMaintenanceCampaign SA_NAME_TEmpty === --- 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.-- Rapidly troubleshoot problems before they affect your business. Most IT organizations don't have a clear picture of how application performance affects their revenue. With AppDynamics, you get 100% visibility into your Java,.NET, PHP application. Start your 15-day FREE TRIAL of AppDynamics Pro! http://pubads.g.doubleclick.net/gampad/clk?id=84349831iu=/4140/ostg.clktrk___ Opensaf-tickets mailing list Opensaf-tickets@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
[tickets] [opensaf:tickets] #699 si assignments still show partially assigned
Analysis: 1)AMF performs quiesced SU1 honoring SI dependency. 2)Role failover of SI4 and SI5 in SU2. 3)Disabled event for SU2. delete sent for SU1 SUSIs deletion for SU2. 4)Deletion response for SU1. New susis in SU3 for active assignments. 5) Disabled event for SU3 deletion of SUSIs in SU3 New susis in Su4 6)Disabled event in SU4, deletion of SUSIs in SU4, New SUSIs in SU5 7)Disabled event in SU5 deletion of SUSIs in SU5 8)Node unlock request SUSIs creation in SU1 9)AMF gets disabled state from SU5 SUSIs are deleted Since no more SU is in enabled state in the system, so no further assignments from AMF side. The counter problem is similar to to lock operation on SU and fault in active callback #666. But this issue will also require fix of #663 to clear admin_node_pend_cbk.admin_oper. --- ** [tickets:#699] si assignments still show partially assigned ** **Status:** unassigned **Created:** Mon Dec 30, 2013 07:29 AM UTC by surender khetavath **Last Updated:** Mon Dec 30, 2013 07:29 AM UTC **Owner:** nobody changeset : 4733 model : 2n configuration : 1App,1SG,5SUs with 3comps each, 5SIs with 3CSIs each si-si deps configured as SI1-SI1-SI3-SI4 (chain of deps) SU1 mapped to PL-3,SU2 to PL-4 saAmfSGAutoRepair=0(False) SuFailover=1(True) Test: 1. perform node lock ( here PL-3) 2. The SU receiving active cbk will report error through ERR_REPORT() api call on self. 3. unlock the node. After continuous faults, SUs became disabled but Sis show partially assigned. si states safSi=TWONSI1,safApp=TWONAPP saAmfSIAdminState=UNLOCKED(1) saAmfSIAssignmentState=PARTIALLY_ASSIGNED(3) safSi=TWONSI2,safApp=TWONAPP saAmfSIAdminState=UNLOCKED(1) saAmfSIAssignmentState=UNASSIGNED(1) safSi=TWONSI4,safApp=TWONAPP saAmfSIAdminState=UNLOCKED(1) saAmfSIAssignmentState=UNASSIGNED(1) safSi=TWONSI3,safApp=TWONAPP saAmfSIAdminState=UNLOCKED(1) saAmfSIAssignmentState=UNASSIGNED(1) safSi=TWONSI5,safApp=TWONAPP saAmfSIAdminState=UNLOCKED(1) saAmfSIAssignmentState=PARTIALLY_ASSIGNED(3) su-si states /etc/init.d/opensafd status safSISU=safSu=SC-2\,safSg=2N\,safApp=OpenSAF,safSi=SC-2N,safApp=OpenSAF saAmfSISUHAState=STANDBY(2) safSISU=safSu=PL-3\,safSg=NoRed\,safApp=OpenSAF,safSi=NoRed3,safApp=OpenSAF saAmfSISUHAState=ACTIVE(1) safSISU=safSu=SC-2\,safSg=NoRed\,safApp=OpenSAF,safSi=NoRed1,safApp=OpenSAF saAmfSISUHAState=ACTIVE(1) safSISU=safSu=SC-1\,safSg=2N\,safApp=OpenSAF,safSi=SC-2N,safApp=OpenSAF saAmfSISUHAState=ACTIVE(1) safSISU=safSu=PL-4\,safSg=NoRed\,safApp=OpenSAF,safSi=NoRed4,safApp=OpenSAF saAmfSISUHAState=ACTIVE(1) safSISU=safSu=SC-1\,safSg=NoRed\,safApp=OpenSAF,safSi=NoRed2,safApp=OpenSAF saAmfSISUHAState=ACTIVE(1) safSISU=safSu=PL-5\,safSg=NoRed\,safApp=OpenSAF,safSi=NoRed5,safApp=OpenSAF saAmfSISUHAState=ACTIVE(1) Su states safSu=SU1,safSg=SGONE,safApp=TWONAPP saAmfSUAdminState=UNLOCKED(1) saAmfSUOperState=DISABLED(2) saAmfSUPresenceState=UNINSTANTIATED(1) saAmfSUReadinessState=OUT-OF-SERVICE(1) safSu=SU2,safSg=SGONE,safApp=TWONAPP saAmfSUAdminState=UNLOCKED(1) saAmfSUOperState=DISABLED(2) saAmfSUPresenceState=UNINSTANTIATED(1) saAmfSUReadinessState=OUT-OF-SERVICE(1) safSu=SU3,safSg=SGONE,safApp=TWONAPP saAmfSUAdminState=UNLOCKED(1) saAmfSUOperState=DISABLED(2) saAmfSUPresenceState=UNINSTANTIATED(1) saAmfSUReadinessState=OUT-OF-SERVICE(1) safSu=SU4,safSg=SGONE,safApp=TWONAPP saAmfSUAdminState=UNLOCKED(1) saAmfSUOperState=DISABLED(2) saAmfSUPresenceState=UNINSTANTIATED(1) saAmfSUReadinessState=OUT-OF-SERVICE(1) safSu=SU5,safSg=SGONE,safApp=TWONAPP saAmfSUAdminState=UNLOCKED(1) saAmfSUOperState=DISABLED(2) saAmfSUPresenceState=UNINSTANTIATED(1) saAmfSUReadinessState=OUT-OF-SERVICE(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.-- Rapidly troubleshoot problems before they affect your business. Most IT organizations don't have a clear picture of how application performance affects their revenue. With AppDynamics, you get 100% visibility into your Java,.NET, PHP application. Start your 15-day FREE TRIAL of AppDynamics Pro! http://pubads.g.doubleclick.net/gampad/clk?id=84349831iu=/4140/ostg.clktrk___ Opensaf-tickets mailing list Opensaf-tickets@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
[tickets] [opensaf:tickets] #702 IMMTOOLS: creating an object using immcfg crashes when RDN value has a DN of an associated object
- **status**: assigned -- review --- ** [tickets:#702] IMMTOOLS: creating an object using immcfg crashes when RDN value has a DN of an associated object** **Status:** review **Created:** Thu Jan 02, 2014 10:05 AM UTC by Zoran Milinkovic **Last Updated:** Thu Jan 02, 2014 10:05 AM UTC **Owner:** Zoran Milinkovic When trying to create a new object, which does not have a parent DN, and its RDN value has a DN of an associated object, immcfg crashes. Example: $ immcfg -c TestClass 'id=testid=1\,testid=5' Segmentation fault (core dumped) --- 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.-- Rapidly troubleshoot problems before they affect your business. Most IT organizations don't have a clear picture of how application performance affects their revenue. With AppDynamics, you get 100% visibility into your Java,.NET, PHP application. Start your 15-day FREE TRIAL of AppDynamics Pro! http://pubads.g.doubleclick.net/gampad/clk?id=84349831iu=/4140/ostg.clktrk___ Opensaf-tickets mailing list Opensaf-tickets@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
[tickets] [opensaf:tickets] #702 IMMTOOLS: creating an object using immcfg crashes when RDN value has a DN of an associated object
https://sourceforge.net/p/opensaf/mailman/message/31801584/ --- ** [tickets:#702] IMMTOOLS: creating an object using immcfg crashes when RDN value has a DN of an associated object** **Status:** review **Created:** Thu Jan 02, 2014 10:05 AM UTC by Zoran Milinkovic **Last Updated:** Thu Jan 02, 2014 10:05 AM UTC **Owner:** Zoran Milinkovic When trying to create a new object, which does not have a parent DN, and its RDN value has a DN of an associated object, immcfg crashes. Example: $ immcfg -c TestClass 'id=testid=1\,testid=5' Segmentation fault (core dumped) --- 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.-- Rapidly troubleshoot problems before they affect your business. Most IT organizations don't have a clear picture of how application performance affects their revenue. With AppDynamics, you get 100% visibility into your Java,.NET, PHP application. Start your 15-day FREE TRIAL of AppDynamics Pro! http://pubads.g.doubleclick.net/gampad/clk?id=84349831iu=/4140/ostg.clktrk___ Opensaf-tickets mailing list Opensaf-tickets@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
[tickets] [opensaf:tickets] #228 Populate saClmNodeAddress and saClmNodeAddressFamily in NodeInfo when TCP is the transport
[staging:d43fd2] changeset: 4775:d43fd2ea1cea user:Mathivanan N.P.mathi.naic...@oracle.com date:Thu Jan 02 22:14:35 2014 +0530 summary: clm: fill saClmNodeAddress and saClmNodeAddressFamily with ip info [#228] --- ** [tickets:#228] Populate saClmNodeAddress and saClmNodeAddressFamily in NodeInfo when TCP is the transport** **Status:** fixed **Created:** Wed May 15, 2013 10:29 AM UTC by Mathi Naickan **Last Updated:** Mon Dec 30, 2013 06:39 AM UTC **Owner:** nobody Placeholder for unsupported attributes. Background: The current CLM(4.**) was uplifted from B.01.01 and was separated from the AMFD process(during OpenSAF 3.0). The scope was primarily to provide cluster membership services and relies on MDS -tipc/tcp for cluster management. Some attributes are not supported during the contribution in 4.0. Now that MDS/TCP supports IPV6 and IPv4 and relatively more stable, CLM could provide support for attributes like saClmNodeAddressFamily saClmNodeCurrAddressFamily saClmNodeAddress saClmNodeCurrAddress and any other unsupported attribute. It will be an interesting task to pass on user configured saClmNodeAddress saClmNodeCurrAddress attributes down to the MDS and to the OS and vice-versa. --- 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.-- Rapidly troubleshoot problems before they affect your business. Most IT organizations don't have a clear picture of how application performance affects their revenue. With AppDynamics, you get 100% visibility into your Java,.NET, PHP application. Start your 15-day FREE TRIAL of AppDynamics Pro! http://pubads.g.doubleclick.net/gampad/clk?id=84349831iu=/4140/ostg.clktrk___ Opensaf-tickets mailing list Opensaf-tickets@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
[tickets] [opensaf:tickets] #228 Populate saClmNodeAddress and saClmNodeAddressFamily in NodeInfo when TCP is the transport
- **status**: review -- fixed --- ** [tickets:#228] Populate saClmNodeAddress and saClmNodeAddressFamily in NodeInfo when TCP is the transport** **Status:** fixed **Created:** Wed May 15, 2013 10:29 AM UTC by Mathi Naickan **Last Updated:** Mon Dec 30, 2013 06:39 AM UTC **Owner:** nobody Placeholder for unsupported attributes. Background: The current CLM(4.**) was uplifted from B.01.01 and was separated from the AMFD process(during OpenSAF 3.0). The scope was primarily to provide cluster membership services and relies on MDS -tipc/tcp for cluster management. Some attributes are not supported during the contribution in 4.0. Now that MDS/TCP supports IPV6 and IPv4 and relatively more stable, CLM could provide support for attributes like saClmNodeAddressFamily saClmNodeCurrAddressFamily saClmNodeAddress saClmNodeCurrAddress and any other unsupported attribute. It will be an interesting task to pass on user configured saClmNodeAddress saClmNodeCurrAddress attributes down to the MDS and to the OS and vice-versa. --- 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.-- Rapidly troubleshoot problems before they affect your business. Most IT organizations don't have a clear picture of how application performance affects their revenue. With AppDynamics, you get 100% visibility into your Java,.NET, PHP application. Start your 15-day FREE TRIAL of AppDynamics Pro! http://pubads.g.doubleclick.net/gampad/clk?id=84349831iu=/4140/ostg.clktrk___ Opensaf-tickets mailing list Opensaf-tickets@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
[tickets] [opensaf:tickets] #219 Fix failures in the CLM test suite
- **status**: review -- fixed --- ** [tickets:#219] Fix failures in the CLM test suite** **Status:** fixed **Created:** Wed May 15, 2013 09:09 AM UTC by Mathi Naickan **Last Updated:** Mon Dec 30, 2013 12:56 PM UTC **Owner:** nobody changed from opensaf compilation fails with --enable-tests to clmtest does not work build problem fixed in 2983 this ticket should fix the problems running clmtest. It seems it does not construct a proper DN for the local node. hasse@Vostro:~/opensaf-repos/opensaf-staging$ clmtest Suite 1: Life Cykel API 1 PASSED saClmInitialize with A.01.01 SA_AIS_OK 2 PASSED saClmInitialize_4 with A.04.01 SA_AIS_OK 3 PASSED saClmInitialize with NULL pointer to handle 4 PASSED saClmInitialize_4 with NULL pointer to handle 5 PASSED saClmInitialize with NULL pointer to callback 6 PASSED saClmInitialize_4 with NULL pointer to callback 7 PASSED 7 PASSED saClmInitialize saClmInitialize_4 with NULL pointer to callback Version 8 PASSED 8 PASSED saClmInitialize saClmInitialize_4 with uninitialized version 9 PASSED 9 PASSED saClmInitialize saClmInitialize_4 with too high release 10 PASSED 10 PASSED saClmInitialize saClmInitialize_4 with too high major version 11 PASSED 11 PASSED saClmInitialize saClmInitialize_4 with too low minor version 12 PASSED 12 PASSED saClmInitialize saClmInitialize_4 with B.0.0 version 13 PASSED saClmInitialize with multiple instance Suite 2: Test case for saClmFinalize 1 PASSED saClmSelectionObjectGet SA_AIS_OK 2 FAILED saClmSelectionObjectGet NULL handle SA_AIS_ERR_BAD_HANDLE (expected SA_AIS_ERR_INVALID_PARAM, got SA_AIS_ERR_BAD_HANDLE) 3 PASSED saClmSelectionObjectGet invalid handle SA_AIS_ERR_BAD_HANDLE 4 PASSED saClmSelectionObjectGet NULL selectionObject SA_AIS_ERR_INVALID_PARAM 5 PASSED 5 PASSED saClmFinalize SA_AIS_OK 6 PASSED saClmFinalize SA_AIS_ERR_BAD_HANDLE - invalid handle 7 PASSED saClmFinalize SA_AIS_ERR_BAD_HANDLE - handle already returned Suite 3: Life Cykel API 4 Inside nodeGetCallBack1error= 1 1 PASSED saClmDispatch - SA_AIS_OK SA_DISPATCH_ALL 2 PASSED saClmDispatch - invalid handle SA_AIS_ERR_BAD_HANDLE 3 PASSED saClmDispatch - zero flag SA_AIS_ERR_INVALID_PARAM Inside nodeGetCallBack1error= 1 4 PASSED saClmDispatch - SA_AIS_OK SA_DISPATCH_ONE Suite 4: CLM OI tests Object with DN 'Vostro' does not exist 1 FAILED CCB Object Modify saClmNodeLockCallbackTimeout (expected SA_AIS_NOT_VALID, got SA_AIS_OK) Object with DN 'Vostro' does not exist 2 FAILED CCB Object Modify saClmNodeDisableReboot (expected SA_AIS_NOT_VALID, got SA_AIS_OK) Object with DN 'Vostro' does not exist 3 PASSED CCB Object Modify saClmNodeAddressFamily Object with DN 'Vostro' does not exist 4 PASSED CCB Object Modify saClmNodeAddress Object with DN 'Vostro' does not exist 5 PASSED CCB Object Modify saClmNodeEE error - object does not exist 6 PASSED CCB Object Delete the member node Suite 5: Test case for saClmClusterNodeGet 1 FAILED saClmClusterNodeGet with valid arguments, SA_AIS_OK (expected SA_AIS_OK, got SA_AIS_ERR_TIMEOUT) 2 FAILED saClmClusterNodeGet_4 with valid arguments, SA_AIS_OK (expected SA_AIS_OK, got SA_AIS_ERR_TIMEOUT) 3 FAILED 3 FAILED 3 FAILED 3 FAILED saClmClusterNodeGet saClmClusterNodeGet_4 with Invalid handle (expected SA_AIS_ERR_BAD_HANDLE, got SA_AIS_ERR_TIMEOUT) 4 FAILED 4 FAILED saClmClusterNodeGet saClmClusterNodeGet_4 with NULL timeout (expected SA_AIS_ERR_INVALID_PARAM, got SA_AIS_ERR_TIMEOUT) 5 PASSED 5 PASSED saClmClusterNodeGet saClmClusterNodeGet_4 with NULL ClusterNode? 6 FAILED 6 FAILED saClmClusterNodeGet saClmClusterNodeGet_4 with nodeId which does not exist (expected SA_AIS_ERR_NOT_EXIST, got SA_AIS_ERR_TIMEOUT) 7 FAILED 7 FAILED saClmClusterNodeGet saClmClusterNodeGet_4 with nodeId of non member node (expected SA_AIS_ERR_NOT_EXIST, got SA_AIS_ERR_TIMEOUT) 8 FAILED 8 FAILED saClmClusterNodeGet saClmClusterNodeGet_4 call with cross version (expected SA_AIS_ERR_VERSION, got SA_AIS_ERR_TIMEOUT) 9 FAILED 9 FAILED saClmClusterNodeGet saClmClusterNodeGet_4 with nodeId as SA_CLM_LOCAL_NODE_ID (expected SA_AIS_OK, got SA_AIS_ERR_TIMEOUT) Suite 6: Test case for saClmClusterNodeGetAsync 1 PASSED saClmClusterNodeGetAsync with valid arguments, SA_AIS_OK Inside nodeGetCallBack4error= 1 2 PASSED saClmClusterNodeGetAsync_4 with valid arguments, SA_AIS_OK 3 FAILED 3 PASSED 3 FAILED 3 PASSED saClmClusterNodeGetAsync with invlaid handle 4 PASSED saClmClusterNodeGetAsync with null invocation 5 PASSED saClmClusterNodeGetAsync with null nodeId Inside nodeGetCallBack4error= 12 6 PASSED saClmClusterNodeGetAsync with nodeId which does not exist 7 PASSED saClmClusterNodeGetAsync with nodeId of non member node Inside nodeGetCallBack1error= 1 8 PASSED saClmClusterNodeGetAsync with nodeId as SA_CLM_LOCAL_NODE_ID 9 PASSED 9 PASSED saClmClusterNodeGetAsync with null callback Suite 7: Test case for saClmClusterTrack error: in ../../tests/clmsv/src/tet_saClmClusterTrack.c at 208: SA_AIS_ERR_NOT_EXIST, expected SA_AIS_OK - exiting --- Sent
[tickets] [opensaf:tickets] #697 dependent assignments are not removed though sponsor SI has partially assigned state.
- **status**: unassigned -- accepted - **assigned_to**: Praveen --- ** [tickets:#697] dependent assignments are not removed though sponsor SI has partially assigned state. ** **Status:** accepted **Created:** Thu Dec 26, 2013 10:02 AM UTC by surender khetavath **Last Updated:** Thu Dec 26, 2013 11:23 AM UTC **Owner:** Praveen changeset : 4733 model : 2n configuration : 1App,1SG,5SUs with 3comps each, 5SIs with 3CSIs each si-si deps configured as SI1-SI1-SI3-SI4 (chain of deps) SU1 mapped to PL-3,SU2 to PL-4 saAmfSGAutoRepair=0(False) SuFailover=1(True) SU1 is active and SU2 standby Test: 1.lock of SU1(active) 2.The component which receives active callback will call exit() 3.Unlock Su1 After continuous exits() by diff comp's..SU5 became active and SU1 standby. SI1 is partially assigned state. safSi=TWONSI1,safApp=TWONAPP saAmfSIAdminState=UNLOCKED(1) saAmfSIAssignmentState=PARTIALLY_ASSIGNED(3) safSi=TWONSI5,safApp=TWONAPP saAmfSIAdminState=UNLOCKED(1) saAmfSIAssignmentState=PARTIALLY_ASSIGNED(3) safSi=TWONSI2,safApp=TWONAPP saAmfSIAdminState=UNLOCKED(1) saAmfSIAssignmentState=FULLY_ASSIGNED(2) safSi=TWONSI3,safApp=TWONAPP saAmfSIAdminState=UNLOCKED(1) saAmfSIAssignmentState=FULLY_ASSIGNED(2) safSi=TWONSI4,safApp=TWONAPP saAmfSIAdminState=UNLOCKED(1) saAmfSIAssignmentState=FULLY_ASSIGNED(2) --- 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.-- Rapidly troubleshoot problems before they affect your business. Most IT organizations don't have a clear picture of how application performance affects their revenue. With AppDynamics, you get 100% visibility into your Java,.NET, PHP application. Start your 15-day FREE TRIAL of AppDynamics Pro! http://pubads.g.doubleclick.net/gampad/clk?id=84349831iu=/4140/ostg.clktrk___ Opensaf-tickets mailing list Opensaf-tickets@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
[tickets] [opensaf:tickets] #697 dependent assignments are not removed though sponsor SI has partially assigned state.
- **status**: accepted -- duplicate --- ** [tickets:#697] dependent assignments are not removed though sponsor SI has partially assigned state. ** **Status:** duplicate **Created:** Thu Dec 26, 2013 10:02 AM UTC by surender khetavath **Last Updated:** Fri Jan 03, 2014 06:35 AM UTC **Owner:** Praveen changeset : 4733 model : 2n configuration : 1App,1SG,5SUs with 3comps each, 5SIs with 3CSIs each si-si deps configured as SI1-SI1-SI3-SI4 (chain of deps) SU1 mapped to PL-3,SU2 to PL-4 saAmfSGAutoRepair=0(False) SuFailover=1(True) SU1 is active and SU2 standby Test: 1.lock of SU1(active) 2.The component which receives active callback will call exit() 3.Unlock Su1 After continuous exits() by diff comp's..SU5 became active and SU1 standby. SI1 is partially assigned state. safSi=TWONSI1,safApp=TWONAPP saAmfSIAdminState=UNLOCKED(1) saAmfSIAssignmentState=PARTIALLY_ASSIGNED(3) safSi=TWONSI5,safApp=TWONAPP saAmfSIAdminState=UNLOCKED(1) saAmfSIAssignmentState=PARTIALLY_ASSIGNED(3) safSi=TWONSI2,safApp=TWONAPP saAmfSIAdminState=UNLOCKED(1) saAmfSIAssignmentState=FULLY_ASSIGNED(2) safSi=TWONSI3,safApp=TWONAPP saAmfSIAdminState=UNLOCKED(1) saAmfSIAssignmentState=FULLY_ASSIGNED(2) safSi=TWONSI4,safApp=TWONAPP saAmfSIAdminState=UNLOCKED(1) saAmfSIAssignmentState=FULLY_ASSIGNED(2) --- 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.-- Rapidly troubleshoot problems before they affect your business. Most IT organizations don't have a clear picture of how application performance affects their revenue. With AppDynamics, you get 100% visibility into your Java,.NET, PHP application. Start your 15-day FREE TRIAL of AppDynamics Pro! http://pubads.g.doubleclick.net/gampad/clk?id=84349831iu=/4140/ostg.clktrk___ Opensaf-tickets mailing list Opensaf-tickets@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
[tickets] [opensaf:tickets] #704 SI of type2 doesn't get assigned to SU of type2
--- ** [tickets:#704] SI of type2 doesn't get assigned to SU of type2** **Status:** unassigned **Created:** Fri Jan 03, 2014 07:10 AM UTC by surender khetavath **Last Updated:** Fri Jan 03, 2014 07:10 AM UTC **Owner:** nobody changeset : 4733 model : 2n configuration : 1App,1SG,2SUs(SU,SU1) of type1 and type2.Each Su has one component of type1 and type2 resp. 2SIs(SI,SI1) of type1 and type2 resp. Each SI has one CSI(CSI,CSI1) of type1 and type2 resp.SU1 and SU2 are mapped to SC-1 saAmfSGAutoRepair=0(False) SuFailover=1(True) Test: 1. bring up the model. Unlock-in/unlock of SU1. 2. Unlock-in/unlock of Su2 At step1, SI gets assigned to SU At step2, SI1 doesn't get assigned to SU1. states: safSu=SU,safSg=SG,safApp=mycompApp saAmfSUAdminState=UNLOCKED(1) saAmfSUOperState=ENABLED(1) saAmfSUPresenceState=INSTANTIATED(3) saAmfSUReadinessState=IN-SERVICE(2) safSu=SU1,safSg=SG,safApp=mycompApp saAmfSUAdminState=UNLOCKED(1) saAmfSUOperState=ENABLED(1) saAmfSUPresenceState=INSTANTIATED(3) saAmfSUReadinessState=IN-SERVICE(2) safSISU=safSu=SC-1\,safSg=NoRed\,safApp=OpenSAF,safSi=NoRed2,safApp=OpenSAF saAmfSISUHAState=ACTIVE(1) safSISU=safSu=SC-1\,safSg=2N\,safApp=OpenSAF,safSi=SC-2N,safApp=OpenSAF saAmfSISUHAState=ACTIVE(1) safSISU=safSu=SU\,safSg=SG\,safApp=mycompApp,safSi=SI,safApp=mycompApp saAmfSISUHAState=ACTIVE(1) safSISU=safSu=SC-2\,safSg=2N\,safApp=OpenSAF,safSi=SC-2N,safApp=OpenSAF saAmfSISUHAState=STANDBY(2) safSISU=safSu=SC-2\,safSg=NoRed\,safApp=OpenSAF,safSi=NoRed1,safApp=OpenSAF saAmfSISUHAState=ACTIVE(1) safSi=SI1,safApp=mycompApp saAmfSIAdminState=UNLOCKED(1) saAmfSIAssignmentState=UNASSIGNED(1) safSi=SI,safApp=mycompApp saAmfSIAdminState=UNLOCKED(1) saAmfSIAssignmentState=PARTIALLY_ASSIGNED(3) /var/log/messages Jan 3 12:32:06 SC-1 osafamfnd[7880]: NO 'safSu=SU,safSg=SG,safApp=mycompApp' Presence State UNINSTANTIATED = INSTANTIATING Jan 3 12:32:06 SC-1 osafamfnd[7880]: NO 'safSu=SU,safSg=SG,safApp=mycompApp' Presence State INSTANTIATING = INSTANTIATED Jan 3 12:32:10 SC-1 osafamfd[7870]: ER avd_new_assgn_susi: Component type missing for SU 'safSu=SU,safSg=SG,safApp=mycompApp' Jan 3 12:32:10 SC-1 osafamfd[7870]: ER avd_new_assgn_susi: Component type missing for CSI 'safCsi=csi1,safSi=SI1,safApp=mycompApp' Jan 3 12:32:10 SC-1 osafamfd[7870]: ER sg_2n_fsm.cc:611: safSi=SI1,safApp=mycompApp Jan 3 12:32:10 SC-1 osafamfnd[7880]: NO Assigning 'safSi=SI,safApp=mycompApp' ACTIVE to 'safSu=SU,safSg=SG,safApp=mycompApp' Jan 3 12:32:10 SC-1 osafamfnd[7880]: NO Assigned 'safSi=SI,safApp=mycompApp' ACTIVE to 'safSu=SU,safSg=SG,safApp=mycompApp' Jan 3 12:32:10 SC-1 osafamfd[7870]: ER avd_new_assgn_susi: Component type missing for SU 'safSu=SU,safSg=SG,safApp=mycompApp' Jan 3 12:32:10 SC-1 osafamfd[7870]: ER avd_new_assgn_susi: Component type missing for CSI 'safCsi=csi1,safSi=SI1,safApp=mycompApp' Jan 3 12:32:10 SC-1 osafamfd[7870]: ER sg_2n_fsm.cc:611: safSi=SI1,safApp=mycompApp Jan 3 12:32:26 SC-1 osafamfnd[7880]: NO saAmfCtDefQuiescingCompleteTimeout for 'safVersion=4.0.0,safCompType=compbasetype1' initialized with saAmfCtDefCallbackTimeout Jan 3 12:32:26 SC-1 osafamfnd[7880]: NO 'safSu=SU1,safSg=SG,safApp=mycompApp' Presence State UNINSTANTIATED = INSTANTIATING Jan 3 12:32:26 SC-1 osafamfnd[7880]: NO 'safSu=SU1,safSg=SG,safApp=mycompApp' Presence State INSTANTIATING = INSTANTIATED Jan 3 12:32:30 SC-1 osafamfd[7870]: ER avd_new_assgn_susi: Component type missing for SU 'safSu=SU,safSg=SG,safApp=mycompApp' Jan 3 12:32:30 SC-1 osafamfd[7870]: ER avd_new_assgn_susi: Component type missing for CSI 'safCsi=csi1,safSi=SI1,safApp=mycompApp' Jan 3 12:32:30 SC-1 osafamfd[7870]: ER sg_2n_fsm.cc:611: safSi=SI1,safApp=mycompApp Jan 3 12:32:30 SC-1 osafamfd[7870]: ER avd_new_assgn_susi: Component type missing for SU 'safSu=SU1,safSg=SG,safApp=mycompApp' Jan 3 12:32:30 SC-1 osafamfd[7870]: ER avd_new_assgn_susi: Component type missing for CSI 'safCsi=csi,safSi=SI,safApp=mycompApp' Jan 3 12:32:30 SC-1 osafamfd[7870]: ER sg_2n_fsm.cc:669: safSi=SI,safApp=mycompApp --- 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.-- Rapidly troubleshoot problems before they affect your business. Most IT organizations don't have a clear picture of how application performance affects their revenue. With AppDynamics, you get 100% visibility into your Java,.NET, PHP application. Start your 15-day FREE TRIAL of AppDynamics Pro!
