[tickets] [opensaf:tickets] #1389 AMF: Node state is not correct after unlock-in nodegroup
--- ** [tickets:#1389] AMF: Node state is not correct after unlock-in nodegroup** **Status:** unassigned **Milestone:** future **Created:** Tue Jun 16, 2015 09:24 AM UTC by Quyen Dao **Last Updated:** Tue Jun 16, 2015 09:24 AM UTC **Owner:** nobody Steps to reproduce -- * Start UML cluster * Create a node group containing PL-3 and PL-4 with admin state as LOCKED-INSTANTIATION * Admin lock then lock-in PL-4 - admin state of PL4 is LOCKED-INSTANTIATION, PL3 is UNLOCKED * Admin unlock-in node group Observed behaviour -- - Admin states of PL-3 and PL-4 are LOCKED Expected behaviour -- - Admin state of PL-4 is LOCKED and PL-3 remains UNLOCKED. --- 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] #1591 AMF: amfd crashes when changing saAmfNodeAutoRepair to ""
--- ** [tickets:#1591] AMF: amfd crashes when changing saAmfNodeAutoRepair to ""** **Status:** unassigned **Milestone:** 4.6.2 **Created:** Tue Nov 10, 2015 09:24 AM UTC by Quyen Dao **Last Updated:** Tue Nov 10, 2015 09:24 AM UTC **Owner:** nobody **Attachments:** - [amfd_bt.txt](https://sourceforge.net/p/opensaf/tickets/1591/attachment/amfd_bt.txt) (13.7 kB; text/plain) amfd crashes when changing saAmfNodeAutoRepair to "" changeset: 7100:a44b87201911 **Command log** root@SC-1:~# immcfg -a saAmfNodeAutoRepair="" safAmfNode=PL-3,safAmfCluster=myAmfCluster error - saImmOmCcbApply FAILED: SA_AIS_ERR_FAILED_OPERATION (21) root@SC-1:~# Connection to 10.0.3.101 closed by remote host. Backtrace is attached --- 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] #1593 AMF: amfd crashes when changing component type attributes to ""
--- ** [tickets:#1593] AMF: amfd crashes when changing component type attributes to ""** **Status:** unassigned **Milestone:** 4.6.2 **Created:** Thu Nov 12, 2015 04:45 AM UTC by Quyen Dao **Last Updated:** Thu Nov 12, 2015 04:45 AM UTC **Owner:** nobody These are the commands to cause amfd crash immcfg -a saAmfCtDefQuiescingCompleteTimeout="" safVersion=4.0.0,safCompType=OpenSafCompTypeAMFWDOG immcfg -a saAmfCtDefInstantiationLevel="" safVersion=4.0.0,safCompType=OpenSafCompTypeAMFWDOG immcfg -a saAmfCtDefDisableRestart="" safVersion=4.0.0,safCompType=OpenSafCompTypeAMFWDOG --- 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] #1595 AMF: amfd crashes when changing SU attributes to ""
--- ** [tickets:#1595] AMF: amfd crashes when changing SU attributes to ""** **Status:** unassigned **Milestone:** 4.6.2 **Created:** Thu Nov 12, 2015 04:55 AM UTC by Quyen Dao **Last Updated:** Thu Nov 12, 2015 04:55 AM UTC **Owner:** nobody These are the commands to cause amfd crash immcfg -a saAmfSUHostNodeOrNodeGroup="" safSu=SC-2,safSg=2N,safApp=OpenSAF immcfg -a saAmfSURank="" safSu=SC-2,safSg=2N,safApp=OpenSAF --- 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] #1592 AMF: amfd crashes when changing component attributes to ""
--- ** [tickets:#1592] AMF: amfd crashes when changing component attributes to ""** **Status:** unassigned **Milestone:** 4.6.2 **Created:** Thu Nov 12, 2015 04:34 AM UTC by Quyen Dao **Last Updated:** Thu Nov 12, 2015 04:34 AM UTC **Owner:** nobody These are the commands to cause amfd crash immcfg -a saAmfCompNumMaxAmStopAttempts="" safComp=AMFWDOG,safSu=PL-3,safSg=NoRed,safApp=OpenSAF immcfg -a saAmfCompNumMaxAmStartAttempts="" safComp=AMFWDOG,safSu=PL-3,safSg=NoRed,safApp=OpenSAF immcfg -a osafAmfCompHcCmdArgv="" safComp=AMFWDOG,safSu=PL-3,safSg=NoRed,safApp=OpenSAF --- 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] #1594 AMF: amfd crashes when changing saAmfSGSuHostNodeGroup to ""
--- ** [tickets:#1594] AMF: amfd crashes when changing saAmfSGSuHostNodeGroup to ""** **Status:** unassigned **Milestone:** 4.6.2 **Created:** Thu Nov 12, 2015 04:50 AM UTC by Quyen Dao **Last Updated:** Thu Nov 12, 2015 04:50 AM UTC **Owner:** nobody command to cause amfd crash: immcfg -a saAmfSGSuHostNodeGroup="" safSg=2N,safApp=OpenSAF --- 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] #1525 AMF: SU presence state transition is missing UNINSTANTIATED during restart
--- ** [tickets:#1525] AMF: SU presence state transition is missing UNINSTANTIATED during restart** **Status:** unassigned **Milestone:** 4.5.2 **Created:** Wed Oct 07, 2015 07:34 AM UTC by Quyen Dao **Last Updated:** Wed Oct 07, 2015 07:34 AM UTC **Owner:** nobody Admin restart for SU with 3 components and 1 is non-restartable, the SU presence state transition during restart is as below: INSTANTIATED => TERMINATING => INSTANTIATING => INSTANTIATED I think it is missing state UNINSTANTIATED? **Syslog** Oct 7 13:12:15 PL-3 osafamfnd[417]: NO Admin Restart request for 'safSu=1,safSg=1,safApp=osaftest' Oct 7 13:12:15 PL-3 C[558]: componentTerminateCallback, invocation 4280287243 Oct 7 13:12:15 PL-3 C[558]: saAmfResponse(inv=4280287243, error=1) Oct 7 13:12:15 PL-3 C[558]: terminate: safComp=C,safSu=1,safSg=1,safApp=osaftest - 0 Oct 7 13:12:15 PL-3 C[558]: Exiting Oct 7 13:12:15 PL-3 osafamfnd[417]: NO 'safSu=1,safSg=1,safApp=osaftest' Presence State INSTANTIATED => TERMINATING Oct 7 13:12:15 PL-3 B[552]: componentTerminateCallback, invocation 4287627274 Oct 7 13:12:16 PL-3 B[552]: saAmfResponse(inv=4287627274, error=1) Oct 7 13:12:16 PL-3 B[552]: terminate: safComp=B,safSu=1,safSg=1,safApp=osaftest - 0 Oct 7 13:12:16 PL-3 B[552]: Exiting Oct 7 13:12:16 PL-3 A[546]: componentTerminateCallback, invocation 4287627275 Oct 7 13:12:17 PL-3 A[546]: saAmfResponse(inv=4287627275, error=1) Oct 7 13:12:17 PL-3 A[546]: terminate: safComp=A,safSu=1,safSg=1,safApp=osaftest - 0 Oct 7 13:12:17 PL-3 A[546]: Exiting Oct 7 13:12:17 PL-3 amfclccli[579]: INSTANTIATE request 'safComp=A,safSu=1,safSg=1,safApp=osaftest' Oct 7 13:12:17 PL-3 amfclccli[579]: INSTANTIATE response 'instantiate' argument '' Oct 7 13:12:17 PL-3 A[583]: started 'safComp=A,safSu=1,safSg=1,safApp=osaftest', listening at port=45157 Oct 7 13:12:17 PL-3 A[583]: saAmfComponentRegister(safComp=A,safSu=1,safSg=1,safApp=osaftest, ) Oct 7 13:12:17 PL-3 osafamfnd[417]: NO 'safSu=1,safSg=1,safApp=osaftest' Presence State TERMINATING => INSTANTIATING Oct 7 13:12:17 PL-3 amfclccli[586]: INSTANTIATE request 'safComp=B,safSu=1,safSg=1,safApp=osaftest' Oct 7 13:12:18 PL-3 amfclccli[586]: INSTANTIATE response 'instantiate' argument '' Oct 7 13:12:18 PL-3 B[589]: started 'safComp=B,safSu=1,safSg=1,safApp=osaftest', listening at port=36898 Oct 7 13:12:18 PL-3 B[589]: saAmfComponentRegister(safComp=B,safSu=1,safSg=1,safApp=osaftest, ) Oct 7 13:12:18 PL-3 amfclccli[592]: INSTANTIATE request 'safComp=C,safSu=1,safSg=1,safApp=osaftest' Oct 7 13:12:18 PL-3 amfclccli[592]: INSTANTIATE response 'instantiate' argument '' Oct 7 13:12:18 PL-3 C[595]: started 'safComp=C,safSu=1,safSg=1,safApp=osaftest', listening at port=34216 Oct 7 13:12:18 PL-3 C[595]: saAmfComponentRegister(safComp=C,safSu=1,safSg=1,safApp=osaftest, ) Oct 7 13:12:18 PL-3 osafamfnd[417]: NO 'safSu=1,safSg=1,safApp=osaftest' Presence State INSTANTIATING => INSTANTIATED --- 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.-- Full-scale, agent-less Infrastructure Monitoring from a single dashboard Integrate with 40+ ManageEngine ITSM Solutions for complete visibility Physical-Virtual-Cloud Infrastructure monitoring from one console Real user monitoring with APM Insights and performance trend reports Learn More http://pubads.g.doubleclick.net/gampad/clk?id=247754911=/4140___ Opensaf-tickets mailing list Opensaf-tickets@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
[tickets] [opensaf:tickets] #1525 AMF: SU presence state transition is missing UNINSTANTIATED during restart
Thanks for the explanation! --- ** [tickets:#1525] AMF: SU presence state transition is missing UNINSTANTIATED during restart** **Status:** unassigned **Milestone:** 4.5.2 **Created:** Wed Oct 07, 2015 07:34 AM UTC by Quyen Dao **Last Updated:** Wed Oct 07, 2015 08:46 AM UTC **Owner:** nobody Admin restart for SU with 3 components and 1 is non-restartable, the SU presence state transition during restart is as below: INSTANTIATED => TERMINATING => INSTANTIATING => INSTANTIATED I think it is missing state UNINSTANTIATED? **Syslog** Oct 7 13:12:15 PL-3 osafamfnd[417]: NO Admin Restart request for 'safSu=1,safSg=1,safApp=osaftest' Oct 7 13:12:15 PL-3 C[558]: componentTerminateCallback, invocation 4280287243 Oct 7 13:12:15 PL-3 C[558]: saAmfResponse(inv=4280287243, error=1) Oct 7 13:12:15 PL-3 C[558]: terminate: safComp=C,safSu=1,safSg=1,safApp=osaftest - 0 Oct 7 13:12:15 PL-3 C[558]: Exiting Oct 7 13:12:15 PL-3 osafamfnd[417]: NO 'safSu=1,safSg=1,safApp=osaftest' Presence State INSTANTIATED => TERMINATING Oct 7 13:12:15 PL-3 B[552]: componentTerminateCallback, invocation 4287627274 Oct 7 13:12:16 PL-3 B[552]: saAmfResponse(inv=4287627274, error=1) Oct 7 13:12:16 PL-3 B[552]: terminate: safComp=B,safSu=1,safSg=1,safApp=osaftest - 0 Oct 7 13:12:16 PL-3 B[552]: Exiting Oct 7 13:12:16 PL-3 A[546]: componentTerminateCallback, invocation 4287627275 Oct 7 13:12:17 PL-3 A[546]: saAmfResponse(inv=4287627275, error=1) Oct 7 13:12:17 PL-3 A[546]: terminate: safComp=A,safSu=1,safSg=1,safApp=osaftest - 0 Oct 7 13:12:17 PL-3 A[546]: Exiting Oct 7 13:12:17 PL-3 amfclccli[579]: INSTANTIATE request 'safComp=A,safSu=1,safSg=1,safApp=osaftest' Oct 7 13:12:17 PL-3 amfclccli[579]: INSTANTIATE response 'instantiate' argument '' Oct 7 13:12:17 PL-3 A[583]: started 'safComp=A,safSu=1,safSg=1,safApp=osaftest', listening at port=45157 Oct 7 13:12:17 PL-3 A[583]: saAmfComponentRegister(safComp=A,safSu=1,safSg=1,safApp=osaftest, ) Oct 7 13:12:17 PL-3 osafamfnd[417]: NO 'safSu=1,safSg=1,safApp=osaftest' Presence State TERMINATING => INSTANTIATING Oct 7 13:12:17 PL-3 amfclccli[586]: INSTANTIATE request 'safComp=B,safSu=1,safSg=1,safApp=osaftest' Oct 7 13:12:18 PL-3 amfclccli[586]: INSTANTIATE response 'instantiate' argument '' Oct 7 13:12:18 PL-3 B[589]: started 'safComp=B,safSu=1,safSg=1,safApp=osaftest', listening at port=36898 Oct 7 13:12:18 PL-3 B[589]: saAmfComponentRegister(safComp=B,safSu=1,safSg=1,safApp=osaftest, ) Oct 7 13:12:18 PL-3 amfclccli[592]: INSTANTIATE request 'safComp=C,safSu=1,safSg=1,safApp=osaftest' Oct 7 13:12:18 PL-3 amfclccli[592]: INSTANTIATE response 'instantiate' argument '' Oct 7 13:12:18 PL-3 C[595]: started 'safComp=C,safSu=1,safSg=1,safApp=osaftest', listening at port=34216 Oct 7 13:12:18 PL-3 C[595]: saAmfComponentRegister(safComp=C,safSu=1,safSg=1,safApp=osaftest, ) Oct 7 13:12:18 PL-3 osafamfnd[417]: NO 'safSu=1,safSg=1,safApp=osaftest' Presence State INSTANTIATING => INSTANTIATED --- 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.-- Full-scale, agent-less Infrastructure Monitoring from a single dashboard Integrate with 40+ ManageEngine ITSM Solutions for complete visibility Physical-Virtual-Cloud Infrastructure monitoring from one console Real user monitoring with APM Insights and performance trend reports Learn More http://pubads.g.doubleclick.net/gampad/clk?id=247754911=/4140___ Opensaf-tickets mailing list Opensaf-tickets@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
[tickets] [opensaf:tickets] #1525 AMF: SU presence state transition is missing UNINSTANTIATED during restart
- **status**: unassigned --> invalid --- ** [tickets:#1525] AMF: SU presence state transition is missing UNINSTANTIATED during restart** **Status:** invalid **Milestone:** 4.5.2 **Created:** Wed Oct 07, 2015 07:34 AM UTC by Quyen Dao **Last Updated:** Wed Oct 07, 2015 09:18 AM UTC **Owner:** nobody Admin restart for SU with 3 components and 1 is non-restartable, the SU presence state transition during restart is as below: INSTANTIATED => TERMINATING => INSTANTIATING => INSTANTIATED I think it is missing state UNINSTANTIATED? **Syslog** Oct 7 13:12:15 PL-3 osafamfnd[417]: NO Admin Restart request for 'safSu=1,safSg=1,safApp=osaftest' Oct 7 13:12:15 PL-3 C[558]: componentTerminateCallback, invocation 4280287243 Oct 7 13:12:15 PL-3 C[558]: saAmfResponse(inv=4280287243, error=1) Oct 7 13:12:15 PL-3 C[558]: terminate: safComp=C,safSu=1,safSg=1,safApp=osaftest - 0 Oct 7 13:12:15 PL-3 C[558]: Exiting Oct 7 13:12:15 PL-3 osafamfnd[417]: NO 'safSu=1,safSg=1,safApp=osaftest' Presence State INSTANTIATED => TERMINATING Oct 7 13:12:15 PL-3 B[552]: componentTerminateCallback, invocation 4287627274 Oct 7 13:12:16 PL-3 B[552]: saAmfResponse(inv=4287627274, error=1) Oct 7 13:12:16 PL-3 B[552]: terminate: safComp=B,safSu=1,safSg=1,safApp=osaftest - 0 Oct 7 13:12:16 PL-3 B[552]: Exiting Oct 7 13:12:16 PL-3 A[546]: componentTerminateCallback, invocation 4287627275 Oct 7 13:12:17 PL-3 A[546]: saAmfResponse(inv=4287627275, error=1) Oct 7 13:12:17 PL-3 A[546]: terminate: safComp=A,safSu=1,safSg=1,safApp=osaftest - 0 Oct 7 13:12:17 PL-3 A[546]: Exiting Oct 7 13:12:17 PL-3 amfclccli[579]: INSTANTIATE request 'safComp=A,safSu=1,safSg=1,safApp=osaftest' Oct 7 13:12:17 PL-3 amfclccli[579]: INSTANTIATE response 'instantiate' argument '' Oct 7 13:12:17 PL-3 A[583]: started 'safComp=A,safSu=1,safSg=1,safApp=osaftest', listening at port=45157 Oct 7 13:12:17 PL-3 A[583]: saAmfComponentRegister(safComp=A,safSu=1,safSg=1,safApp=osaftest, ) Oct 7 13:12:17 PL-3 osafamfnd[417]: NO 'safSu=1,safSg=1,safApp=osaftest' Presence State TERMINATING => INSTANTIATING Oct 7 13:12:17 PL-3 amfclccli[586]: INSTANTIATE request 'safComp=B,safSu=1,safSg=1,safApp=osaftest' Oct 7 13:12:18 PL-3 amfclccli[586]: INSTANTIATE response 'instantiate' argument '' Oct 7 13:12:18 PL-3 B[589]: started 'safComp=B,safSu=1,safSg=1,safApp=osaftest', listening at port=36898 Oct 7 13:12:18 PL-3 B[589]: saAmfComponentRegister(safComp=B,safSu=1,safSg=1,safApp=osaftest, ) Oct 7 13:12:18 PL-3 amfclccli[592]: INSTANTIATE request 'safComp=C,safSu=1,safSg=1,safApp=osaftest' Oct 7 13:12:18 PL-3 amfclccli[592]: INSTANTIATE response 'instantiate' argument '' Oct 7 13:12:18 PL-3 C[595]: started 'safComp=C,safSu=1,safSg=1,safApp=osaftest', listening at port=34216 Oct 7 13:12:18 PL-3 C[595]: saAmfComponentRegister(safComp=C,safSu=1,safSg=1,safApp=osaftest, ) Oct 7 13:12:18 PL-3 osafamfnd[417]: NO 'safSu=1,safSg=1,safApp=osaftest' Presence State INSTANTIATING => INSTANTIATED --- 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.-- Full-scale, agent-less Infrastructure Monitoring from a single dashboard Integrate with 40+ ManageEngine ITSM Solutions for complete visibility Physical-Virtual-Cloud Infrastructure monitoring from one console Real user monitoring with APM Insights and performance trend reports Learn More http://pubads.g.doubleclick.net/gampad/clk?id=247754911=/4140___ Opensaf-tickets mailing list Opensaf-tickets@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
[tickets] [opensaf:tickets] #1500 AMF: Fails to repair failed SU when failed component has attribute saAmfCompDisableRestart=1
I could reproduce the problem on the latest changeset (6994:092665e82e11). Please find attached the test log, syslog and trace. Attachments: - [1500.trace.zip](https://sourceforge.net/p/opensaf/tickets/_discuss/thread/7329c35a/396c/attachment/1500.trace.zip) (292.6 kB; application/zip) --- ** [tickets:#1500] AMF: Fails to repair failed SU when failed component has attribute saAmfCompDisableRestart=1** **Status:** unassigned **Milestone:** 4.5.2 **Created:** Thu Sep 24, 2015 01:16 PM UTC by Quyen Dao **Last Updated:** Tue Oct 13, 2015 05:21 AM UTC **Owner:** nobody **Attachments:** - [AppConfig-2N.xml](https://sourceforge.net/p/opensaf/tickets/1500/attachment/AppConfig-2N.xml) (9.2 kB; text/xml) **Steps to reproduce** * Load the attached model * Change saAmfCompDisableRestart=1 on the component in SU1 * Change to component CLC-CLI script to return 1 for cleanup * Trigger component termination failed by killing the component in SU1 * Repair SU1 -> Result: SU1 fails to repair. **command log** root@PL-3:~# immcfg -a saAmfCompDisableRestart=1 safComp=AmfDemo,safSu=SU1,safSg=AmfDemo,safApp=AmfDemo1 root@PL-3:~# amf-state su all safSu=SU1,safSg=AmfDemo,safApp=AmfDemo1 safSu=SU1,safSg=AmfDemo,safApp=AmfDemo1 saAmfSUAdminState=UNLOCKED(1) saAmfSUOperState=ENABLED(1) saAmfSUPresenceState=INSTANTIATED(3) saAmfSUReadinessState=IN-SERVICE(2) root@PL-3:~# pkill amf_demo root@PL-3:~# amf-state su all safSu=SU1,safSg=AmfDemo,safApp=AmfDemo1 safSu=SU1,safSg=AmfDemo,safApp=AmfDemo1 saAmfSUAdminState=UNLOCKED(1) saAmfSUOperState=DISABLED(2) saAmfSUPresenceState=TERMINATION-FAILED(7) saAmfSUReadinessState=OUT-OF-SERVICE(1) root@PL-3:~# root@PL-3:~# amf-adm repaired safSu=SU1,safSg=AmfDemo,safApp=AmfDemo1 root@PL-3:~# amf-state su all safSu=SU1,safSg=AmfDemo,safApp=AmfDemo1 safSu=SU1,safSg=AmfDemo,safApp=AmfDemo1 saAmfSUAdminState=UNLOCKED(1) saAmfSUOperState=DISABLED(2) saAmfSUPresenceState=TERMINATION-FAILED(7) saAmfSUReadinessState=OUT-OF-SERVICE(1) root@PL-3:~# **syslog** Sep 24 20:14:05 PL-3 osafamfnd[417]: NO saAmfCompDisableRestart changed to 1 for 'safComp=AmfDemo,safSu=SU1,safSg=AmfDemo,safApp=AmfDemo1' Sep 24 20:14:05 PL-3 osafimmnd[389]: NO Ccb 3 COMMITTED (immcfg_PL-3_641) Sep 24 20:14:05 PL-3 amf_demo[585]: exiting (caught term signal) Sep 24 20:14:05 PL-3 osafamfnd[417]: NO saAmfCompDisableRestart is true for 'safComp=AmfDemo,safSu=SU1,safSg=AmfDemo,safApp=AmfDemo1' Sep 24 20:14:05 PL-3 osafamfnd[417]: NO recovery action 'comp restart' escalated to 'comp failover' Sep 24 20:14:05 PL-3 osafamfnd[417]: NO saAmfSUFailover is true for 'safSu=SU1,safSg=AmfDemo,safApp=AmfDemo1' Sep 24 20:14:05 PL-3 osafamfnd[417]: NO SU failover probation timer started (timeout: 12000 ns) Sep 24 20:14:05 PL-3 osafamfnd[417]: NO Performing failover of 'safSu=SU1,safSg=AmfDemo,safApp=AmfDemo1' (SU failover count: 1) Sep 24 20:14:05 PL-3 osafamfnd[417]: NO 'safComp=AmfDemo,safSu=SU1,safSg=AmfDemo,safApp=AmfDemo1' recovery action escalated from 'componentRestart' to 'suFailover' Sep 24 20:14:05 PL-3 osafamfnd[417]: NO 'safComp=AmfDemo,safSu=SU1,safSg=AmfDemo,safApp=AmfDemo1' faulted due to 'avaDown' : Recovery is 'suFailover' Sep 24 20:14:05 PL-3 osafamfnd[417]: NO Terminating components of 'safSu=SU1,safSg=AmfDemo,safApp=AmfDemo1'(abruptly & unordered) Sep 24 20:14:05 PL-3 osafamfnd[417]: NO 'safSu=SU1,safSg=AmfDemo,safApp=AmfDemo1' Presence State INSTANTIATED => TERMINATING Sep 24 20:14:05 PL-3 osafamfnd[417]: NO Cleanup of 'safComp=AmfDemo,safSu=SU1,safSg=AmfDemo,safApp=AmfDemo1' failed Sep 24 20:14:05 PL-3 osafamfnd[417]: NO Reason:'Exec of script success, but script exits with non-zero status' Sep 24 20:14:05 PL-3 osafamfnd[417]: NO Exit code: 1 Sep 24 20:14:05 PL-3 osafamfnd[417]: WA 'safComp=AmfDemo,safSu=SU1,safSg=AmfDemo,safApp=AmfDemo1' Presence State TERMINATING => TERMINATION_FAILED Sep 24 20:14:05 PL-3 osafamfnd[417]: NO 'safSu=SU1,safSg=AmfDemo,safApp=AmfDemo1' Presence State TERMINATING => TERMINATION_FAILED Sep 24 20:14:14 PL-3 osafamfnd[417]: ER ncsmds_api for 0 FAILED, dest=2030f0249 Sep 24 20:14:22 PL-3 osafamfnd[417]: NO Repair request for 'safSu=SU1,safSg=AmfDemo,safApp=AmfDemo1' Sep 24 20:14:22 PL-3 osafamfnd[417]: NO 'safSu=SU1,safSg=AmfDemo,safApp=AmfDemo1' Presence State TERMINATION_FAILED => UNINSTANTIATED Sep 24 20:14:22 PL-3 osafamfnd[417]: NO 'safSu=SU1,safSg=AmfDemo,safApp=AmfDemo1' Presence State UNINSTANTIATED => INSTANTIATING Sep 24 20:14:22 PL-3 amf_demo[734]: 'safComp=AmfDemo,safSu=SU1,safSg=AmfDemo,safApp=AmfDemo1' started Sep 24 20:14:22 PL-3 osafamfnd[417]: NO 'safSu=SU1,safSg=AmfDemo,safApp=AmfDemo1' Presence State INSTANTIATING => INSTANTIATED Sep 24 20:14:22 PL-3 osafamfnd[417]: NO Assigning 'safSi=AmfDemo,safApp=AmfDemo1' STANDBY to 'safSu=SU1,safSg=AmfDemo,safApp=AmfDemo1' Sep 24 20:14:22 PL-3 amf_demo[734]: saA
[tickets] [opensaf:tickets] #1518 AMF: SU presence state transition is not correct during admin op restart
--- ** [tickets:#1518] AMF: SU presence state transition is not correct during admin op restart** **Status:** unassigned **Milestone:** 4.5.2 **Created:** Tue Oct 06, 2015 07:41 AM UTC by Quyen Dao **Last Updated:** Tue Oct 06, 2015 07:41 AM UTC **Owner:** nobody >From my observation, the su and component presence state transition is as >below during admin su (with all restartable components) restart: su: INSTANTIATED => RESTARTING => INSTANTIATING => INSTANTIATED component: INSTANTIATED => RESTARTING => INSTANTIATED In my opinion, the presence state transition of su should be the same as component for this case: INSTANTIATED => RESTARTING => INSTANTIATED According to AIS-AMF-B.04.01-Table 5 Presence State of Components of a Service Unit Page 74, if all components are RESTARTING, then SU should be RESTARTING (not INSTANTIATING) as well. **syslog for su presence state transition** Oct 6 12:24:50 PL-3 osafamfnd[418]: NO Admin Restart request for 'safSu=SU1,safSg=AmfDemo,safApp=AmfDemo1' Oct 6 12:24:50 PL-3 osafamfnd[418]: NO 'safSu=SU1,safSg=AmfDemo,safApp=AmfDemo1' Presence State INSTANTIATED => RESTARTING Oct 6 12:24:50 PL-3 amf_demo[757]: Terminating Oct 6 12:24:50 PL-3 osafamfnd[418]: NO 'safSu=SU1,safSg=AmfDemo,safApp=AmfDemo1' Presence State RESTARTING => INSTANTIATING Oct 6 12:24:50 PL-3 amf_demo[985]: 'safComp=AmfDemo,safSu=SU1,safSg=AmfDemo,safApp=AmfDemo1' started Oct 6 12:24:50 PL-3 osafamfnd[418]: NO 'safSu=SU1,safSg=AmfDemo,safApp=AmfDemo1' Presence State INSTANTIATING => INSTANTIATED Oct 6 12:24:50 PL-3 osafamfnd[418]: NO Assigning 'safSi=AmfDemo,safApp=AmfDemo1' ACTIVE to 'safSu=SU1,safSg=AmfDemo,safApp=AmfDemo1' Oct 6 12:24:50 PL-3 amf_demo[985]: Registered with AMF and HC started Oct 6 12:24:50 PL-3 amf_demo[985]: CSI Set - add 'safCsi=AmfDemo,safSi=AmfDemo,safApp=AmfDemo1' HAState Active Oct 6 12:24:50 PL-3 osafamfnd[418]: NO Assigned 'safSi=AmfDemo,safApp=AmfDemo1' ACTIVE to 'safSu=SU1,safSg=AmfDemo,safApp=AmfDemo1' --- 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] #1473 AMF: Component Termination Failed alarm is raised then cleared immediately
--- ** [tickets:#1473] AMF: Component Termination Failed alarm is raised then cleared immediately** **Status:** unassigned **Milestone:** 4.5.2 **Created:** Thu Sep 10, 2015 09:52 AM UTC by Quyen Dao **Last Updated:** Thu Sep 10, 2015 09:52 AM UTC **Owner:** nobody **Attachments:** - [AppConfig-2N.xml](https://sourceforge.net/p/opensaf/tickets/1473/attachment/AppConfig-2N.xml) (9.3 kB; text/xml) Steps to reproduce: * Load the attached model * Change the clc-cli script of the component to always return 1 for cleanup * Kill the component Result: Component Termination Failed alarm is raised then cleared immediately and presence state of the failed component is UNINSTANTIATED instead TERMINATION-FAILED. Log root@PL-3:~# ntfread === Sep 10 15:51:42 - Alarm === eventType = SA_NTF_ALARM_PROCESSING notificationObject = "safComp=AmfDemo,safSu=SU1,safSg=AmfDemo,safApp=AmfDemo1" notifyingObject = "safApp=safAmfService" notificationClassId = SA_NTF_VENDOR_ID_SAF.SA_SVC_AMF.3 (0x3) additionalText = "Cleanup of Component safComp=AmfDemo,safSu=SU1,safSg=AmfDemo,safApp=AmfDemo1 failed" - additionalInfo: 0 - infoId = 1 infoType = 10 infoValue = "safAmfNode=PL-3,safAmfCluster=myAmfCluster" probableCause = SA_NTF_SOFTWARE_ERROR perceivedSeverity = SA_NTF_SEVERITY_MAJOR === Sep 10 15:51:42 - Alarm === eventType = SA_NTF_ALARM_PROCESSING notificationObject = "safComp=AmfDemo,safSu=SU1,safSg=AmfDemo,safApp=AmfDemo1" notifyingObject = "safApp=safAmfService" notificationClassId = SA_NTF_VENDOR_ID_SAF.SA_SVC_AMF.3 (0x3) additionalText = "Previous raised alarm of safComp=AmfDemo,safSu=SU1,safSg=AmfDemo,safApp=AmfDemo1 is now cleared" probableCause = SA_NTF_SOFTWARE_ERROR perceivedSeverity = SA_NTF_SEVERITY_CLEARED root@PL-3:~# amf-state su all safSu=SU1,safSg=AmfDemo,safApp=AmfDemo1 safSu=SU1,safSg=AmfDemo,safApp=AmfDemo1 saAmfSUAdminState=UNLOCKED(1) saAmfSUOperState=DISABLED(2) saAmfSUPresenceState=TERMINATION-FAILED(7) saAmfSUReadinessState=OUT-OF-SERVICE(1) root@PL-3:~# root@PL-3:~# amf-state comp all safComp=AmfDemo,safSu=SU1,safSg=AmfDemo,safApp=AmfDemo1 safComp=AmfDemo,safSu=SU1,safSg=AmfDemo,safApp=AmfDemo1 saAmfCompOperState=DISABLED(2) saAmfCompPresenceState=UNINSTANTIATED(1) saAmfCompReadinessState=OUT-OF-SERVICE(1) root@PL-3:~# --- 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.-- Monitor Your Dynamic Infrastructure at Any Scale With Datadog! Get real-time metrics from all of your servers, apps and tools in one place. SourceForge users - Click here to start your Free Trial of Datadog now! http://pubads.g.doubleclick.net/gampad/clk?id=241902991=/4140___ Opensaf-tickets mailing list Opensaf-tickets@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
[tickets] [opensaf:tickets] #1500 AMF: Fails to repair failed SU when failed component has attribute saAmfCompDisableRestart=1
--- ** [tickets:#1500] AMF: Fails to repair failed SU when failed component has attribute saAmfCompDisableRestart=1** **Status:** unassigned **Milestone:** 4.5.2 **Created:** Thu Sep 24, 2015 01:16 PM UTC by Quyen Dao **Last Updated:** Thu Sep 24, 2015 01:16 PM UTC **Owner:** nobody **Attachments:** - [AppConfig-2N.xml](https://sourceforge.net/p/opensaf/tickets/1500/attachment/AppConfig-2N.xml) (9.2 kB; text/xml) **Steps to reproduce** * Load the attached model * Change saAmfCompDisableRestart=1 on the component in SU1 * Change to component CLC-CLI script to return 1 for cleanup * Trigger component termination failed by killing the component in SU1 * Repair SU1 -> Result: SU1 fails to repair. **command log** root@PL-3:~# immcfg -a saAmfCompDisableRestart=1 safComp=AmfDemo,safSu=SU1,safSg=AmfDemo,safApp=AmfDemo1 root@PL-3:~# amf-state su all safSu=SU1,safSg=AmfDemo,safApp=AmfDemo1 safSu=SU1,safSg=AmfDemo,safApp=AmfDemo1 saAmfSUAdminState=UNLOCKED(1) saAmfSUOperState=ENABLED(1) saAmfSUPresenceState=INSTANTIATED(3) saAmfSUReadinessState=IN-SERVICE(2) root@PL-3:~# pkill amf_demo root@PL-3:~# amf-state su all safSu=SU1,safSg=AmfDemo,safApp=AmfDemo1 safSu=SU1,safSg=AmfDemo,safApp=AmfDemo1 saAmfSUAdminState=UNLOCKED(1) saAmfSUOperState=DISABLED(2) saAmfSUPresenceState=TERMINATION-FAILED(7) saAmfSUReadinessState=OUT-OF-SERVICE(1) root@PL-3:~# root@PL-3:~# amf-adm repaired safSu=SU1,safSg=AmfDemo,safApp=AmfDemo1 root@PL-3:~# amf-state su all safSu=SU1,safSg=AmfDemo,safApp=AmfDemo1 safSu=SU1,safSg=AmfDemo,safApp=AmfDemo1 saAmfSUAdminState=UNLOCKED(1) saAmfSUOperState=DISABLED(2) saAmfSUPresenceState=TERMINATION-FAILED(7) saAmfSUReadinessState=OUT-OF-SERVICE(1) root@PL-3:~# **syslog** Sep 24 20:14:05 PL-3 osafamfnd[417]: NO saAmfCompDisableRestart changed to 1 for 'safComp=AmfDemo,safSu=SU1,safSg=AmfDemo,safApp=AmfDemo1' Sep 24 20:14:05 PL-3 osafimmnd[389]: NO Ccb 3 COMMITTED (immcfg_PL-3_641) Sep 24 20:14:05 PL-3 amf_demo[585]: exiting (caught term signal) Sep 24 20:14:05 PL-3 osafamfnd[417]: NO saAmfCompDisableRestart is true for 'safComp=AmfDemo,safSu=SU1,safSg=AmfDemo,safApp=AmfDemo1' Sep 24 20:14:05 PL-3 osafamfnd[417]: NO recovery action 'comp restart' escalated to 'comp failover' Sep 24 20:14:05 PL-3 osafamfnd[417]: NO saAmfSUFailover is true for 'safSu=SU1,safSg=AmfDemo,safApp=AmfDemo1' Sep 24 20:14:05 PL-3 osafamfnd[417]: NO SU failover probation timer started (timeout: 12000 ns) Sep 24 20:14:05 PL-3 osafamfnd[417]: NO Performing failover of 'safSu=SU1,safSg=AmfDemo,safApp=AmfDemo1' (SU failover count: 1) Sep 24 20:14:05 PL-3 osafamfnd[417]: NO 'safComp=AmfDemo,safSu=SU1,safSg=AmfDemo,safApp=AmfDemo1' recovery action escalated from 'componentRestart' to 'suFailover' Sep 24 20:14:05 PL-3 osafamfnd[417]: NO 'safComp=AmfDemo,safSu=SU1,safSg=AmfDemo,safApp=AmfDemo1' faulted due to 'avaDown' : Recovery is 'suFailover' Sep 24 20:14:05 PL-3 osafamfnd[417]: NO Terminating components of 'safSu=SU1,safSg=AmfDemo,safApp=AmfDemo1'(abruptly & unordered) Sep 24 20:14:05 PL-3 osafamfnd[417]: NO 'safSu=SU1,safSg=AmfDemo,safApp=AmfDemo1' Presence State INSTANTIATED => TERMINATING Sep 24 20:14:05 PL-3 osafamfnd[417]: NO Cleanup of 'safComp=AmfDemo,safSu=SU1,safSg=AmfDemo,safApp=AmfDemo1' failed Sep 24 20:14:05 PL-3 osafamfnd[417]: NO Reason:'Exec of script success, but script exits with non-zero status' Sep 24 20:14:05 PL-3 osafamfnd[417]: NO Exit code: 1 Sep 24 20:14:05 PL-3 osafamfnd[417]: WA 'safComp=AmfDemo,safSu=SU1,safSg=AmfDemo,safApp=AmfDemo1' Presence State TERMINATING => TERMINATION_FAILED Sep 24 20:14:05 PL-3 osafamfnd[417]: NO 'safSu=SU1,safSg=AmfDemo,safApp=AmfDemo1' Presence State TERMINATING => TERMINATION_FAILED Sep 24 20:14:14 PL-3 osafamfnd[417]: ER ncsmds_api for 0 FAILED, dest=2030f0249 Sep 24 20:14:22 PL-3 osafamfnd[417]: NO Repair request for 'safSu=SU1,safSg=AmfDemo,safApp=AmfDemo1' Sep 24 20:14:22 PL-3 osafamfnd[417]: NO 'safSu=SU1,safSg=AmfDemo,safApp=AmfDemo1' Presence State TERMINATION_FAILED => UNINSTANTIATED Sep 24 20:14:22 PL-3 osafamfnd[417]: NO 'safSu=SU1,safSg=AmfDemo,safApp=AmfDemo1' Presence State UNINSTANTIATED => INSTANTIATING Sep 24 20:14:22 PL-3 amf_demo[734]: 'safComp=AmfDemo,safSu=SU1,safSg=AmfDemo,safApp=AmfDemo1' started Sep 24 20:14:22 PL-3 osafamfnd[417]: NO 'safSu=SU1,safSg=AmfDemo,safApp=AmfDemo1' Presence State INSTANTIATING => INSTANTIATED Sep 24 20:14:22 PL-3 osafamfnd[417]: NO Assigning 'safSi=AmfDemo,safApp=AmfDemo1' STANDBY to 'safSu=SU1,safSg=AmfDemo,safApp=AmfDemo1' Sep 24 20:14:22 PL-3 amf_demo[734]: saAmfHealthcheckStart FAILED - 14 Sep 24 20:14:22 PL-3 osafamfnd[417]: NO saAmfCompDisableRestart is true for 'safComp=AmfDemo,safSu=SU1,safSg=AmfDemo,safApp=AmfDemo1' Sep 24 20:14:22 PL-3 osafamfnd[417]: NO recovery action 'comp restart' escalated to 'comp failover' Sep 24 20
[tickets] [opensaf:tickets] #1637 AMF: Remove amfnd mbscv code
--- ** [tickets:#1637] AMF: Remove amfnd mbscv code** **Status:** assigned **Milestone:** 5.0.FC **Created:** Tue Dec 15, 2015 04:39 AM UTC by Quyen Dao **Last Updated:** Tue Dec 15, 2015 04:39 AM UTC **Owner:** Quyen Dao Remove amfnd mbscv related code as it's not used --- 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] #1637 AMF: Remove amfnd mbcsv code
- **summary**: AMF: Remove amfnd mbscv code --> AMF: Remove amfnd mbcsv code - Description has changed: Diff: --- old +++ new @@ -1 +1 @@ -Remove amfnd mbscv related code as it's not used +Remove amfnd mbcsv related code as it's not used --- ** [tickets:#1637] AMF: Remove amfnd mbcsv code** **Status:** assigned **Milestone:** 5.0.FC **Created:** Tue Dec 15, 2015 04:39 AM UTC by Quyen Dao **Last Updated:** Tue Dec 15, 2015 04:39 AM UTC **Owner:** Quyen Dao Remove amfnd mbcsv related code as it's not used --- 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] #1653 AMF: Component keeps restarting during admin RESTART SU
--- ** [tickets:#1653] AMF: Component keeps restarting during admin RESTART SU** **Status:** unassigned **Milestone:** 4.6.2 **Created:** Tue Dec 29, 2015 12:01 PM UTC by Quyen Dao **Last Updated:** Tue Dec 29, 2015 12:01 PM UTC **Owner:** nobody Component keeps restarting during admin RESTART SU if it fails to instantiate. changeset: 7198:835719950bcb **Steps to reproduce** 1. Load AppConfig-2N.xml 2. Unlock-in safSu=SU1,safSg=AmfDemo,safApp=AmfDemo1 3. Change the amf_demo_script to always exit(1) for instantiate command 4. admin restart safSu=SU1,safSg=AmfDemo,safApp=AmfDemo1 Results: amfnd keeps restarting component **syslog** 2015-12-29 18:44:50 SC-1 osafamfnd[501]: NO 'safSu=SU1,safSg=AmfDemo,safApp=AmfDemo1' Presence State UNINSTANTIATED => INSTANTIATING 2015-12-29 18:44:50 SC-1 amf_demo[784]: 'safComp=AmfDemo,safSu=SU1,safSg=AmfDemo,safApp=AmfDemo1' started 2015-12-29 18:44:50 SC-1 osafamfnd[501]: NO 'safSu=SU1,safSg=AmfDemo,safApp=AmfDemo1' Presence State INSTANTIATING => INSTANTIATED 2015-12-29 18:44:50 SC-1 amf_demo[784]: Registered with AMF and HC started 2015-12-29 18:44:50 SC-1 amf_demo[784]: Health check 1 2015-12-29 18:45:00 SC-1 amf_demo[784]: Health check 2 2015-12-29 18:45:10 SC-1 amf_demo[784]: Health check 3 2015-12-29 18:45:20 SC-1 amf_demo[784]: Health check 4 2015-12-29 18:45:30 SC-1 amf_demo[784]: Health check 5 2015-12-29 18:45:40 SC-1 amf_demo[784]: Health check 6 2015-12-29 18:45:43 SC-1 osafamfnd[501]: NO Admin Restart request for 'safSu=SU1,safSg=AmfDemo,safApp=AmfDemo1' 2015-12-29 18:45:43 SC-1 osafamfnd[501]: NO 'safSu=SU1,safSg=AmfDemo,safApp=AmfDemo1' Presence State INSTANTIATED => RESTARTING 2015-12-29 18:45:43 SC-1 amf_demo[784]: Terminating 2015-12-29 18:45:43 SC-1 osafamfnd[501]: NO Instantiation of 'safComp=AmfDemo,safSu=SU1,safSg=AmfDemo,safApp=AmfDemo1' failed 2015-12-29 18:45:43 SC-1 osafamfnd[501]: NO Reason:'Exec of script success, but script exits with non-zero status' 2015-12-29 18:45:43 SC-1 osafamfnd[501]: NO Exit code: 1 2015-12-29 18:45:43 SC-1 osafamfnd[501]: NO Instantiation of 'safComp=AmfDemo,safSu=SU1,safSg=AmfDemo,safApp=AmfDemo1' failed 2015-12-29 18:45:43 SC-1 osafamfnd[501]: NO Reason:'Exec of script success, but script exits with non-zero status' 2015-12-29 18:45:43 SC-1 osafamfnd[501]: NO Exit code: 1 2015-12-29 18:45:43 SC-1 osafamfnd[501]: NO Instantiation of 'safComp=AmfDemo,safSu=SU1,safSg=AmfDemo,safApp=AmfDemo1' failed 2015-12-29 18:45:43 SC-1 osafamfnd[501]: NO Reason:'Exec of script success, but script exits with non-zero status' 2015-12-29 18:45:43 SC-1 osafamfnd[501]: NO Exit code: 1 2015-12-29 18:45:43 SC-1 osafamfnd[501]: NO Instantiation of 'safComp=AmfDemo,safSu=SU1,safSg=AmfDemo,safApp=AmfDemo1' failed 2015-12-29 18:45:43 SC-1 osafamfnd[501]: NO Reason:'Exec of script success, but script exits with non-zero status' 2015-12-29 18:45:43 SC-1 osafamfnd[501]: NO Exit code: 1 2015-12-29 18:45:43 SC-1 osafamfnd[501]: NO Instantiation of 'safComp=AmfDemo,safSu=SU1,safSg=AmfDemo,safApp=AmfDemo1' failed 2015-12-29 18:45:43 SC-1 osafamfnd[501]: NO Reason:'Exec of script success, but script exits with non-zero status' 2015-12-29 18:45:43 SC-1 osafamfnd[501]: NO Exit code: 1 2015-12-29 18:45:43 SC-1 osafamfnd[501]: NO Instantiation of 'safComp=AmfDemo,safSu=SU1,safSg=AmfDemo,safApp=AmfDemo1' failed 2015-12-29 18:45:43 SC-1 osafamfnd[501]: NO Reason:'Exec of script success, but script exits with non-zero status' 2015-12-29 18:45:43 SC-1 osafamfnd[501]: NO Exit code: 1 2015-12-29 18:45:43 SC-1 osafamfnd[501]: NO Instantiation of 'safComp=AmfDemo,safSu=SU1,safSg=AmfDemo,safApp=AmfDemo1' failed 2015-12-29 18:45:43 SC-1 osafamfnd[501]: NO Reason:'Exec of script success, but script exits with non-zero status' 2015-12-29 18:45:43 SC-1 osafamfnd[501]: NO Exit code: 1 2015-12-29 18:45:43 SC-1 osafamfnd[501]: NO Instantiation of 'safComp=AmfDemo,safSu=SU1,safSg=AmfDemo,safApp=AmfDemo1' failed 2015-12-29 18:45:43 SC-1 osafamfnd[501]: NO Reason:'Exec of script success, but script exits with non-zero status' 2015-12-29 18:45:43 SC-1 osafamfnd[501]: NO Exit code: 1 2015-12-29 18:45:43 SC-1 osafamfnd[501]: NO Instantiation of 'safComp=AmfDemo,safSu=SU1,safSg=AmfDemo,safApp=AmfDemo1' failed 2015-12-29 18:45:43 SC-1 osafamfnd[501]: NO Reason:'Exec of script success, but script exits with non-zero status' 2015-12-29 18:45:43 SC-1 osafamfnd[501]: NO Exit code: 1 2015-12-29 18:45:43 SC-1 osafamfnd[501]: NO Instantiation of 'safComp=AmfDemo,safSu=SU1,safSg=AmfDemo,safApp=AmfDemo1' failed 2015-12-29 18:45:43 SC-1 osafamfnd[501]: NO Reason:'Exec of script success, but script exits with non-zero status' 2015-12-29 18:45:43 SC-1 osafamfnd[501]: NO Exit code: 1 2015-12-29 18:45:43 SC-1 osafamfnd[501]: NO Instantiation of 'safComp=AmfDemo,safSu=SU1,safSg=AmfDemo,safApp=AmfDemo1' failed 2015-12-29 18:45:43 SC-1 osafamfnd[501]: NO Reason:'Exec of script success, but script exits with non-zero status' 2015-12-29 18:4
[tickets] [opensaf:tickets] #1612 AMF: amfd crashes when changing compGlobalAttribute attributes to ""
--- ** [tickets:#1612] AMF: amfd crashes when changing compGlobalAttribute attributes to "" ** **Status:** unassigned **Milestone:** 4.6.2 **Created:** Fri Nov 27, 2015 06:03 AM UTC by Quyen Dao **Last Updated:** Fri Nov 27, 2015 06:03 AM UTC **Owner:** nobody These are the commands to cause amfd crash: immcfg -a saAmfNumMaxInstantiateWithoutDelay="" safRdn=compGlobalAttributes,safApp=safAmfService immcfg -a saAmfNumMaxInstantiateWithDelay="" safRdn=compGlobalAttributes,safApp=safAmfService immcfg -a saAmfNumMaxAmStopAttempts="" safRdn=compGlobalAttributes,safApp=safAmfService immcfg -a saAmfNumMaxAmStartAttempts="" safRdn=compGlobalAttributes,safApp=safAmfService immcfg -a saAmfDelayBetweenInstantiateAttempts="" safRdn=compGlobalAttributes,safApp=safAmfService --- 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] #1737 pyosaf: Add __str__ method to SaNameT class
- **status**: unassigned --> assigned - **assigned_to**: Quyen Dao - **Milestone**: future --> 5.1.FC --- ** [tickets:#1737] pyosaf: Add __str__ method to SaNameT class** **Status:** assigned **Milestone:** 5.1.FC **Created:** Thu Apr 07, 2016 07:56 AM UTC by Quyen Dao **Last Updated:** Thu Apr 07, 2016 07:57 AM UTC **Owner:** Quyen Dao Add __str__ method into non extended SaNameT class. Note: exteneded SaNameT class already has this method. with this change, user can call str(sa_name_t_obj) to convert SaNameT to str without caring it's extended or non extended. --- 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.-- Mobile security can be enabling, not merely restricting. Employees who bring their own devices (BYOD) to work are irked by the imposition of MDM restrictions. Mobile Device Manager Plus allows you to control only the apps on BYO-devices by containerizing them, leaving personal data untouched! https://ad.doubleclick.net/ddm/clk/304595813;131938128;j___ Opensaf-tickets mailing list Opensaf-tickets@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
[tickets] [opensaf:tickets] #1737 pyosaf: Add __str__ method to SaNameT class
- **status**: assigned --> review --- ** [tickets:#1737] pyosaf: Add __str__ method to SaNameT class** **Status:** review **Milestone:** 5.1.FC **Created:** Thu Apr 07, 2016 07:56 AM UTC by Quyen Dao **Last Updated:** Wed May 25, 2016 03:50 AM UTC **Owner:** Quyen Dao Add __str__ method into non extended SaNameT class. Note: exteneded SaNameT class already has this method. with this change, user can call str(sa_name_t_obj) to convert SaNameT to str without caring it's extended or non extended. --- 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.-- Mobile security can be enabling, not merely restricting. Employees who bring their own devices (BYOD) to work are irked by the imposition of MDM restrictions. Mobile Device Manager Plus allows you to control only the apps on BYO-devices by containerizing them, leaving personal data untouched! https://ad.doubleclick.net/ddm/clk/304595813;131938128;j___ Opensaf-tickets mailing list Opensaf-tickets@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
[tickets] [opensaf:tickets] #1676 pyosaf: AIS interface for the extended SaNameT
- **status**: assigned --> review --- ** [tickets:#1676] pyosaf: AIS interface for the extended SaNameT** **Status:** review **Milestone:** 5.0.FC **Created:** Wed Feb 03, 2016 02:02 AM UTC by Quyen Dao **Last Updated:** Wed Feb 03, 2016 02:02 AM UTC **Owner:** Quyen Dao Add support for extended SaNameT in saAis.py --- 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.-- Site24x7 APM Insight: Get Deep Visibility into Application Performance APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month Monitor end-to-end web transactions and take corrective actions now Troubleshoot faster and improve end-user experience. Signup Now! http://pubads.g.doubleclick.net/gampad/clk?id=267308311=/4140___ Opensaf-tickets mailing list Opensaf-tickets@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
[tickets] [opensaf:tickets] #1678 ntf: ntftest suite 35 result is not stable
--- ** [tickets:#1678] ntf: ntftest suite 35 result is not stable** **Status:** unassigned **Milestone:** 4.6.2 **Created:** Thu Feb 04, 2016 07:44 AM UTC by Quyen Dao **Last Updated:** Thu Feb 04, 2016 07:44 AM UTC **Owner:** nobody root@SC-1:~# immcfg -a longDnsAllowed=1 opensafImm=opensafImm,safApp=safImmService root@SC-1:~# ntftest 35 Suite 35: CM notification test for extended name attribute 1 PASSED CREATE, runtime (OsafNtfCmTestRT) object, extended name attribute; 2 PASSED runtime, attr ch, REPLACE (EXTENDED NAME, ANY); 3 PASSED runtime, attr ch, ADD (EXTENDED NAME); 4 PASSED DELETE, runtime (OsafNtfCmTestRT) object; 5 PASSED CREATE, config (OsafNtfCmTestCFG) object, extended name attribute; 6 PASSED config, attr ch, REPLACE (EXTENDED NAME, ANY); 7 PASSED config, attr ch, ADD (EXTENDED NAME); 8 PASSED DELETE, config (OsafNtfCmTestCFG) object; = Test Result: Total: 8 Passed: 8 Failed: 0 root@SC-1:~# root@SC-1:~# ntftest 35 Suite 35: CM notification test for extended name attribute 1 PASSED CREATE, runtime (OsafNtfCmTestRT) object, extended name attribute; 2 PASSED runtime, attr ch, REPLACE (EXTENDED NAME, ANY); 3 PASSED runtime, attr ch, ADD (EXTENDED NAME); 4 PASSED DELETE, runtime (OsafNtfCmTestRT) object; 5 PASSED CREATE, config (OsafNtfCmTestCFG) object, extended name attribute; error: in test_ntf_imcn.c at 4679: SA_AIS_ERR_TRY_AGAIN, expected SA_AIS_OK - exiting root@SC-1:~# root@SC-1:~# ntftest 35 Suite 35: CM notification test for extended name attribute 1 PASSED CREATE, runtime (OsafNtfCmTestRT) object, extended name attribute; 2 PASSED runtime, attr ch, REPLACE (EXTENDED NAME, ANY); 3 PASSED runtime, attr ch, ADD (EXTENDED NAME); 4 PASSED DELETE, runtime (OsafNtfCmTestRT) object; error - saImmOmCcbObjectCreate_2 FAILED with SA_AIS_ERR_EXIST (14) 5 FAILED CREATE, config (OsafNtfCmTestCFG) object, extended name attribute (expected SA_AIS_OK, got SA_AIS_ERR_FAILED_OPERATION); 6 PASSED config, attr ch, REPLACE (EXTENDED NAME, ANY); 7 PASSED config, attr ch, ADD (EXTENDED NAME); 8 PASSED DELETE, config (OsafNtfCmTestCFG) object; = Test Result: Total: 8 Passed: 7 Failed: 1 root@SC-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.-- Site24x7 APM Insight: Get Deep Visibility into Application Performance APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month Monitor end-to-end web transactions and take corrective actions now Troubleshoot faster and improve end-user experience. Signup Now! http://pubads.g.doubleclick.net/gampad/clk?id=272487151=/4140___ Opensaf-tickets mailing list Opensaf-tickets@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
[tickets] [opensaf:tickets] #1637 AMF: Remove amfnd mbcsv code
https://sourceforge.net/p/opensaf/mailman/message/34695823/ changeset: 7236:a473355f7891 user:Quyen Dao <quyen@dektech.com.au> date:Tue Jan 19 09:35:44 2016 +0100 summary: amfnd: Remove mbcsv code from amfnd [#1637] --- ** [tickets:#1637] AMF: Remove amfnd mbcsv code** **Status:** fixed **Milestone:** 5.0.FC **Created:** Tue Dec 15, 2015 04:39 AM UTC by Quyen Dao **Last Updated:** Tue Jan 19, 2016 11:20 AM UTC **Owner:** Quyen Dao Remove amfnd mbcsv related code as it's not used --- 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.-- Site24x7 APM Insight: Get Deep Visibility into Application Performance APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month Monitor end-to-end web transactions and take corrective actions now Troubleshoot faster and improve end-user experience. Signup Now! http://pubads.g.doubleclick.net/gampad/clk?id=267308311=/4140___ Opensaf-tickets mailing list Opensaf-tickets@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
[tickets] [opensaf:tickets] #1680 IMM: immnd crashes when configuring saAmfToleranceTime for safDepend object
--- ** [tickets:#1680] IMM: immnd crashes when configuring saAmfToleranceTime for safDepend object** **Status:** unassigned **Milestone:** 4.6.2 **Created:** Tue Feb 16, 2016 07:06 AM UTC by Quyen Dao **Last Updated:** Tue Feb 16, 2016 07:06 AM UTC **Owner:** nobody **cmd log** root@SC-1:~# immcfg -a saAmfToleranceTime=1 "safDepend=safSi=AmfDemo1_2\,safApp=AmfDemo1,safSi=AmfDemo1_1,safApp=AmfDemo1" error - saImmOmCcbObjectModify_2 FAILED: SA_AIS_ERR_BAD_HANDLE (9) error - saImmOmCcbApply FAILED: SA_AIS_ERR_FAILED_OPERATION (21) root@SC-1:~# **syslog** 2016-02-16 13:54:54 SC-1 osafimmnd[424]: ImmModel.cc:7093: canonicalizeAttrModification: Assertion 'omuti != ccb->mMutations.end()' failed. 2016-02-16 13:54:54 SC-1 osafimmpbed: WA PBE lost contact with parent IMMND - Exiting 2016-02-16 13:54:54 SC-1 osafamfnd[494]: NO 'safSu=SC-1,safSg=NoRed,safApp=OpenSAF' component restart probation timer started (timeout: 600 ns) 2016-02-16 13:54:54 SC-1 osafamfnd[494]: NO Restarting a component of 'safSu=SC-1,safSg=NoRed,safApp=OpenSAF' (comp restart count: 1) 2016-02-16 13:54:54 SC-1 osafamfnd[494]: NO 'safComp=IMMND,safSu=SC-1,safSg=NoRed,safApp=OpenSAF' faulted due to 'avaDown' : Recovery is 'componentRestart' 2016-02-16 13:54:54 SC-1 osafntfimcnd[455]: NO saImmOiDispatch() Fail SA_AIS_ERR_BAD_HANDLE (9) 2016-02-16 13:54:54 SC-1 osafimmd[414]: WA IMMND coordinator at 2010f apparently crashed => electing new coord 2016-02-16 13:54:54 SC-1 osafimmd[414]: NO New coord elected, resides at 2020f 2016-02-16 13:54:54 SC-1 osafimmnd[1144]: Started **backtrace** (gdb) bt #0 0x7f1d76f69cc9 in __GI_raise (sig=sig@entry=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:56 #1 0x7f1d76f6d0d8 in __GI_abort () at abort.c:89 #2 0x7f1d77c653ce in __osafassert_fail (__file=, __line=, __func=, __assertion=) at sysf_def.c:281 #3 0x00428afe in ImmModel::canonicalizeAttrModification (this=0x1e6b420, req=req@entry=0x7fff0cba1220) at ImmModel.cc:7093 #4 0x00428bfc in immModel_canonicalizeAttrModification (cb=cb@entry=0x698580 <_immnd_cb>, req=req@entry=0x7fff0cba1220) at ImmModel.cc:723 #5 0x00405248 in immnd_evt_proc_object_modify (cb=cb@entry=0x698580 <_immnd_cb>, evt=evt@entry=0x7fff0cba1210, originatedAtThisNd=originatedAtThisNd@entry=SA_TRUE, clnt_hdl=clnt_hdl@entry=1172526203151, reply_dest=564113889558952) at immnd_evt.c:6277 #6 0x00416a74 in immnd_evt_proc_fevs_dispatch (cb=cb@entry=0x698580 <_immnd_cb>, msg=msg@entry=0x7f1d70004608, originatedAtThisNd=originatedAtThisNd@entry=SA_TRUE, clnt_hdl=clnt_hdl@entry=1172526203151, reply_dest=reply_dest@entry=564113889558952, msgNo=msgNo@entry=1343) at immnd_evt.c:8107 #7 0x0041895d in immnd_evt_proc_fevs_rcv (sinfo=0x7f1d70004720, evt=0x7f1d700045e0, cb=0x698580 <_immnd_cb>) at immnd_evt.c:8973 #8 immnd_process_evt () at immnd_evt.c:681 #9 0x0040b226 in main (argc=, argv=) at immnd_main.c:348 (gdb) --- 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.-- Site24x7 APM Insight: Get Deep Visibility into Application Performance APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month Monitor end-to-end web transactions and take corrective actions now Troubleshoot faster and improve end-user experience. Signup Now! http://pubads.g.doubleclick.net/gampad/clk?id=272487151=/4140___ Opensaf-tickets mailing list Opensaf-tickets@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
[tickets] [opensaf:tickets] #1697 AMF: standby amfd crashes right after creating AMF entities for application with nway model
- **status**: assigned --> review --- ** [tickets:#1697] AMF: standby amfd crashes right after creating AMF entities for application with nway model** **Status:** review **Milestone:** 4.6.2 **Created:** Wed Mar 09, 2016 09:24 AM UTC by Quyen Dao **Last Updated:** Wed Mar 09, 2016 09:42 AM UTC **Owner:** Quyen Dao **Attachments:** - [osafamfd.sc_1](https://sourceforge.net/p/opensaf/tickets/1697/attachment/osafamfd.sc_1) (9.5 MB; application/octet-stream) - [osafamfd.sc_2](https://sourceforge.net/p/opensaf/tickets/1697/attachment/osafamfd.sc_2) (6.1 MB; application/octet-stream) There is a rare case that after loading the nway application configuration or creating all the AMF entities objects in IMM, standby amfd crashes due to the following assertion. 2016-03-09 13:35:21 SC-2 osafamfd[507]: ckpt_dec.cc:1222: dec_sg_fsm_state: Assertion 'sg != nullptr' failed. trace files are attached **Backtrace** (gdb) bt #0 0x7f03c1debcc9 in __GI_raise (sig=sig@entry=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:56 #1 0x7f03c1def0d8 in __GI_abort () at abort.c:89 #2 0x7f03c356fade in __osafassert_fail (__file=, __line=, __func=, __assertion=) at sysf_def.c:281 #3 0x0040e71f in dec_sg_fsm_state (cb=0x6c6400 <_control_block>, dec=) at ckpt_dec.cc:1222 #4 0x0040a007 in avsv_dequeue_async_update_msgs (cb=cb@entry=0x6c6400 <_control_block>, pr_or_fr=pr_or_fr@entry=true) at chkop.cc:1262 #5 0x0040ab27 in avsv_mbcsv_process_dec_cb (arg=0x7ffd0a964fb0, cb=0x6c6400 <_control_block>) at chkop.cc:329 #6 avsv_mbcsv_cb (arg=0x7ffd0a964fb0) at chkop.cc:171 #7 0x7f03c357fbe6 in ncs_mbscv_rcv_decode (peer=peer@entry=0x1493c10, evt=evt@entry=0x7f03bc007f60) at mbcsv_act.c:393 #8 0x7f03c357fdb6 in ncs_mbcsv_rcv_async_update (peer=0x1493c10, evt=0x7f03bc007f60) at mbcsv_act.c:440 #9 0x7f03c35869a0 in mbcsv_process_events (rcvd_evt=0x7f03bc007f60, mbcsv_hdl=mbcsv_hdl@entry=4293918753) at mbcsv_pr_evts.c:168 #10 0x7f03c3586b0b in mbcsv_hdl_dispatch_all (mbcsv_hdl=4293918753, mbx=mbx@entry=4288675841) at mbcsv_pr_evts.c:272 #11 0x7f03c3581332 in mbcsv_process_dispatch_request (arg=0x7ffd0a965120) at mbcsv_api.c:423 #12 0x00409a42 in avsv_mbcsv_dispatch (cb=cb@entry=0x6c6400 <_control_block>, flag=flag@entry=2) at chkop.cc:839 #13 0x00405a0d in main_loop () at main.cc:715 #14 main (argc=, argv=) at main.cc:851 (gdb) --- 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.-- Transform Data into Opportunity. Accelerate data analysis in your applications with Intel Data Analytics Acceleration Library. Click to learn more. http://pubads.g.doubleclick.net/gampad/clk?id=278785111=/4140___ Opensaf-tickets mailing list Opensaf-tickets@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
[tickets] [opensaf:tickets] #1610 AMF: Add directory and Makefile.am for amfa and amfnd unit test.
- **status**: review --> fixed - **Comment**: changeset: 7156:d187a526ec0d parent: 7153:2273a66aac93 user: Quyen Dao <quyen@dektech.com.au> date:Wed Dec 02 09:10:51 2015 +0100 summary: amf: Setup directory and Makefile.am for amfa and amfnd google unit test [#1610] --- ** [tickets:#1610] AMF: Add directory and Makefile.am for amfa and amfnd unit test.** **Status:** fixed **Milestone:** 5.0.FC **Created:** Thu Nov 26, 2015 06:47 AM UTC by Quyen Dao **Last Updated:** Thu Nov 26, 2015 08:00 AM UTC **Owner:** Quyen Dao Add directory and Makefile.am for amfa and amfnd google unit test. --- 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.-- Transform Data into Opportunity. Accelerate data analysis in your applications with Intel Data Analytics Acceleration Library. Click to learn more. http://pubads.g.doubleclick.net/gampad/clk?id=278785231=/4140___ Opensaf-tickets mailing list Opensaf-tickets@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
[tickets] [opensaf:tickets] #1737 pyosaf: Add __str__ method for the SaNameT class
--- ** [tickets:#1737] pyosaf: Add __str__ method for the SaNameT class** **Status:** unassigned **Milestone:** future **Created:** Thu Apr 07, 2016 07:56 AM UTC by Quyen Dao **Last Updated:** Thu Apr 07, 2016 07:56 AM UTC **Owner:** nobody Add __str__ method into non extended SaNameT class. Note: exteneded SaNameT class already has this method. with this change, user can call str(sa_name_t_obj) to convert SaNameT to str without caring it's extended or non extended. --- 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] #1737 pyosaf: Add __str__ method to SaNameT class
- **summary**: pyosaf: Add __str__ method for the SaNameT class --> pyosaf: Add __str__ method to SaNameT class --- ** [tickets:#1737] pyosaf: Add __str__ method to SaNameT class** **Status:** unassigned **Milestone:** future **Created:** Thu Apr 07, 2016 07:56 AM UTC by Quyen Dao **Last Updated:** Thu Apr 07, 2016 07:56 AM UTC **Owner:** nobody Add __str__ method into non extended SaNameT class. Note: exteneded SaNameT class already has this method. with this change, user can call str(sa_name_t_obj) to convert SaNameT to str without caring it's extended or non extended. --- 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] #1730 LOG: group ownership of log file is not correct after failover
--- ** [tickets:#1730] LOG: group ownership of log file is not correct after failover** **Status:** unassigned **Milestone:** 4.6.2 **Created:** Wed Apr 06, 2016 09:16 AM UTC by Quyen Dao **Last Updated:** Wed Apr 06, 2016 09:16 AM UTC **Owner:** nobody *Steps to reproduce* 1. Create test_data_group_1 on active SC 2. Create test_data_group_2 then test_data_group_1 on standby SC 3. Add user who owned the osaflogd process to test_data_group_1 on both SC 4. Configure log data group to test_data_group_1 by immcfg command 5. Reboot the active SC 6. On standby SC, list the log files with group name and it results like below. Result: The group ownership of notifcation log stream is test_data_group_2 instead test_data_group_1 after failover. Note: * The saflog directory is in the shared file system. * opensafd is started as root root@SC-2:~# ll /srv/shared/saflog/ total 44 drwxrwxrwx 4 root root 4096 Mar 23 13:53 ./ drwxrwxrwx 7 ubuntu ubuntu4096 Mar 22 14:51 ../ drwxrwxr-x 2 ubuntu ubuntu4096 Mar 23 13:51 repo/ -rw-r--r-- 1 root root 138 Mar 23 13:53 saLogAlarm.cfg -rw-r--r-- 1 root root 138 Mar 22 17:35 saLogAlarm_20160322_173951.cfg -rw-r- 1 root test_data_group_1 200 Mar 23 13:53 saLogAlarm_20160323_135207.log -rw-r--r-- 1 root root 138 Mar 23 13:52 saLogNotification.cfg -rw-r- 1 root test_data_group_20 Mar 23 13:52 saLogNotification_20160323_135207.log -rw-r--r-- 1 root root 143 Mar 23 13:53 saLogSystem.cfg -rw-r- 1 root test_data_group_1 6876 Mar 23 13:53 saLogSystem_20160323_135207.log root@SC-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.-- ___ Opensaf-tickets mailing list Opensaf-tickets@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
[tickets] [opensaf:tickets] #1676 pyosaf: AIS interface for the extended SaNameT
- **status**: review --> fixed - **assigned_to**: Quyen Dao --> nobody - **Comment**: changeset: 7355:22f5236624cb tag: tip user: Quyen Dao <quyen@dektech.com.au> date:Thu Mar 24 08:38:04 2016 +0100 summary: pyosaf: Add support for extended SaNameT in saAis.py [#1676] --- ** [tickets:#1676] pyosaf: AIS interface for the extended SaNameT** **Status:** fixed **Milestone:** 5.0.FC **Created:** Wed Feb 03, 2016 02:02 AM UTC by Quyen Dao **Last Updated:** Wed Feb 03, 2016 09:02 AM UTC **Owner:** nobody Add support for extended SaNameT in saAis.py --- 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.-- Transform Data into Opportunity. Accelerate data analysis in your applications with Intel Data Analytics Acceleration Library. Click to learn more. http://pubads.g.doubleclick.net/gampad/clk?id=278785351=/4140___ Opensaf-tickets mailing list Opensaf-tickets@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
[tickets] [opensaf:tickets] #1676 pyosaf: AIS interface for the extended SaNameT
- **assigned_to**: Quyen Dao --- ** [tickets:#1676] pyosaf: AIS interface for the extended SaNameT** **Status:** fixed **Milestone:** 5.0.FC **Created:** Wed Feb 03, 2016 02:02 AM UTC by Quyen Dao **Last Updated:** Fri Mar 25, 2016 03:48 AM UTC **Owner:** Quyen Dao Add support for extended SaNameT in saAis.py --- 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.-- Transform Data into Opportunity. Accelerate data analysis in your applications with Intel Data Analytics Acceleration Library. Click to learn more. http://pubads.g.doubleclick.net/gampad/clk?id=278785351=/4140___ Opensaf-tickets mailing list Opensaf-tickets@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
[tickets] [opensaf:tickets] #1697 AMF: standby amfd crashes right after creating AMF entities for application with nway model
- **status**: unassigned --> assigned - **assigned_to**: Quyen Dao --- ** [tickets:#1697] AMF: standby amfd crashes right after creating AMF entities for application with nway model** **Status:** assigned **Milestone:** 4.6.2 **Created:** Wed Mar 09, 2016 09:24 AM UTC by Quyen Dao **Last Updated:** Wed Mar 09, 2016 09:24 AM UTC **Owner:** Quyen Dao **Attachments:** - [osafamfd.sc_1](https://sourceforge.net/p/opensaf/tickets/1697/attachment/osafamfd.sc_1) (9.5 MB; application/octet-stream) - [osafamfd.sc_2](https://sourceforge.net/p/opensaf/tickets/1697/attachment/osafamfd.sc_2) (6.1 MB; application/octet-stream) There is a rare case that after loading the nway application configuration or creating all the AMF entities objects in IMM, standby amfd crashes due to the following assertion. 2016-03-09 13:35:21 SC-2 osafamfd[507]: ckpt_dec.cc:1222: dec_sg_fsm_state: Assertion 'sg != nullptr' failed. trace files are attached **Backtrace** (gdb) bt #0 0x7f03c1debcc9 in __GI_raise (sig=sig@entry=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:56 #1 0x7f03c1def0d8 in __GI_abort () at abort.c:89 #2 0x7f03c356fade in __osafassert_fail (__file=, __line=, __func=, __assertion=) at sysf_def.c:281 #3 0x0040e71f in dec_sg_fsm_state (cb=0x6c6400 <_control_block>, dec=) at ckpt_dec.cc:1222 #4 0x0040a007 in avsv_dequeue_async_update_msgs (cb=cb@entry=0x6c6400 <_control_block>, pr_or_fr=pr_or_fr@entry=true) at chkop.cc:1262 #5 0x0040ab27 in avsv_mbcsv_process_dec_cb (arg=0x7ffd0a964fb0, cb=0x6c6400 <_control_block>) at chkop.cc:329 #6 avsv_mbcsv_cb (arg=0x7ffd0a964fb0) at chkop.cc:171 #7 0x7f03c357fbe6 in ncs_mbscv_rcv_decode (peer=peer@entry=0x1493c10, evt=evt@entry=0x7f03bc007f60) at mbcsv_act.c:393 #8 0x7f03c357fdb6 in ncs_mbcsv_rcv_async_update (peer=0x1493c10, evt=0x7f03bc007f60) at mbcsv_act.c:440 #9 0x7f03c35869a0 in mbcsv_process_events (rcvd_evt=0x7f03bc007f60, mbcsv_hdl=mbcsv_hdl@entry=4293918753) at mbcsv_pr_evts.c:168 #10 0x7f03c3586b0b in mbcsv_hdl_dispatch_all (mbcsv_hdl=4293918753, mbx=mbx@entry=4288675841) at mbcsv_pr_evts.c:272 #11 0x7f03c3581332 in mbcsv_process_dispatch_request (arg=0x7ffd0a965120) at mbcsv_api.c:423 #12 0x00409a42 in avsv_mbcsv_dispatch (cb=cb@entry=0x6c6400 <_control_block>, flag=flag@entry=2) at chkop.cc:839 #13 0x00405a0d in main_loop () at main.cc:715 #14 main (argc=, argv=) at main.cc:851 (gdb) --- 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.-- Transform Data into Opportunity. Accelerate data analysis in your applications with Intel Data Analytics Acceleration Library. Click to learn more. http://pubads.g.doubleclick.net/gampad/clk?id=278785111=/4140___ Opensaf-tickets mailing list Opensaf-tickets@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
[tickets] [opensaf:tickets] #1697 AMF: standby amfd crashes right after creating AMF entities for application with nway model
- **status**: review --> fixed --- ** [tickets:#1697] AMF: standby amfd crashes right after creating AMF entities for application with nway model** **Status:** fixed **Milestone:** 4.6.2 **Created:** Wed Mar 09, 2016 09:24 AM UTC by Quyen Dao **Last Updated:** Wed Mar 09, 2016 10:36 AM UTC **Owner:** Quyen Dao **Attachments:** - [osafamfd.sc_1](https://sourceforge.net/p/opensaf/tickets/1697/attachment/osafamfd.sc_1) (9.5 MB; application/octet-stream) - [osafamfd.sc_2](https://sourceforge.net/p/opensaf/tickets/1697/attachment/osafamfd.sc_2) (6.1 MB; application/octet-stream) There is a rare case that after loading the nway application configuration or creating all the AMF entities objects in IMM, standby amfd crashes due to the following assertion. 2016-03-09 13:35:21 SC-2 osafamfd[507]: ckpt_dec.cc:1222: dec_sg_fsm_state: Assertion 'sg != nullptr' failed. trace files are attached **Backtrace** (gdb) bt #0 0x7f03c1debcc9 in __GI_raise (sig=sig@entry=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:56 #1 0x7f03c1def0d8 in __GI_abort () at abort.c:89 #2 0x7f03c356fade in __osafassert_fail (__file=, __line=, __func=, __assertion=) at sysf_def.c:281 #3 0x0040e71f in dec_sg_fsm_state (cb=0x6c6400 <_control_block>, dec=) at ckpt_dec.cc:1222 #4 0x0040a007 in avsv_dequeue_async_update_msgs (cb=cb@entry=0x6c6400 <_control_block>, pr_or_fr=pr_or_fr@entry=true) at chkop.cc:1262 #5 0x0040ab27 in avsv_mbcsv_process_dec_cb (arg=0x7ffd0a964fb0, cb=0x6c6400 <_control_block>) at chkop.cc:329 #6 avsv_mbcsv_cb (arg=0x7ffd0a964fb0) at chkop.cc:171 #7 0x7f03c357fbe6 in ncs_mbscv_rcv_decode (peer=peer@entry=0x1493c10, evt=evt@entry=0x7f03bc007f60) at mbcsv_act.c:393 #8 0x7f03c357fdb6 in ncs_mbcsv_rcv_async_update (peer=0x1493c10, evt=0x7f03bc007f60) at mbcsv_act.c:440 #9 0x7f03c35869a0 in mbcsv_process_events (rcvd_evt=0x7f03bc007f60, mbcsv_hdl=mbcsv_hdl@entry=4293918753) at mbcsv_pr_evts.c:168 #10 0x7f03c3586b0b in mbcsv_hdl_dispatch_all (mbcsv_hdl=4293918753, mbx=mbx@entry=4288675841) at mbcsv_pr_evts.c:272 #11 0x7f03c3581332 in mbcsv_process_dispatch_request (arg=0x7ffd0a965120) at mbcsv_api.c:423 #12 0x00409a42 in avsv_mbcsv_dispatch (cb=cb@entry=0x6c6400 <_control_block>, flag=flag@entry=2) at chkop.cc:839 #13 0x00405a0d in main_loop () at main.cc:715 #14 main (argc=, argv=) at main.cc:851 (gdb) --- 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.-- Transform Data into Opportunity. Accelerate data analysis in your applications with Intel Data Analytics Acceleration Library. Click to learn more. http://pubads.g.doubleclick.net/gampad/clk?id=278785471=/4140___ Opensaf-tickets mailing list Opensaf-tickets@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
[tickets] [opensaf:tickets] #1697 AMF: standby amfd crashes right after creating AMF entities for application with nway model
changeset: 7385:1d0eadb294c2 user:Quyen Dao <quyen@dektech.com.au> date:Fri Apr 01 13:16:12 2016 +1100 summary: amfd: do not checkpoint the nway sg fsm in case of no change [#1697] changeset: 7388:faa66a07301c branch: opensaf-4.7.x user: Quyen Dao <quyen@dektech.com.au> date:Fri Apr 01 14:34:21 2016 +1100 summary: amfd: do not checkpoint the nway sg fsm in case of no change [#1697] changeset: 7389:5c4cf3922071 branch: opensaf-4.6.x parent: 7367:7c228f63b498 user: Quyen Dao <quyen@dektech.com.au> date:Fri Apr 01 14:34:43 2016 +1100 summary: amfd: do not checkpoint the nway sg fsm in case of no change [#1697] --- ** [tickets:#1697] AMF: standby amfd crashes right after creating AMF entities for application with nway model** **Status:** fixed **Milestone:** 4.6.2 **Created:** Wed Mar 09, 2016 09:24 AM UTC by Quyen Dao **Last Updated:** Fri Apr 01, 2016 03:09 AM UTC **Owner:** Quyen Dao **Attachments:** - [osafamfd.sc_1](https://sourceforge.net/p/opensaf/tickets/1697/attachment/osafamfd.sc_1) (9.5 MB; application/octet-stream) - [osafamfd.sc_2](https://sourceforge.net/p/opensaf/tickets/1697/attachment/osafamfd.sc_2) (6.1 MB; application/octet-stream) There is a rare case that after loading the nway application configuration or creating all the AMF entities objects in IMM, standby amfd crashes due to the following assertion. 2016-03-09 13:35:21 SC-2 osafamfd[507]: ckpt_dec.cc:1222: dec_sg_fsm_state: Assertion 'sg != nullptr' failed. trace files are attached **Backtrace** (gdb) bt #0 0x7f03c1debcc9 in __GI_raise (sig=sig@entry=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:56 #1 0x7f03c1def0d8 in __GI_abort () at abort.c:89 #2 0x7f03c356fade in __osafassert_fail (__file=, __line=, __func=, __assertion=) at sysf_def.c:281 #3 0x0040e71f in dec_sg_fsm_state (cb=0x6c6400 <_control_block>, dec=) at ckpt_dec.cc:1222 #4 0x0040a007 in avsv_dequeue_async_update_msgs (cb=cb@entry=0x6c6400 <_control_block>, pr_or_fr=pr_or_fr@entry=true) at chkop.cc:1262 #5 0x0040ab27 in avsv_mbcsv_process_dec_cb (arg=0x7ffd0a964fb0, cb=0x6c6400 <_control_block>) at chkop.cc:329 #6 avsv_mbcsv_cb (arg=0x7ffd0a964fb0) at chkop.cc:171 #7 0x7f03c357fbe6 in ncs_mbscv_rcv_decode (peer=peer@entry=0x1493c10, evt=evt@entry=0x7f03bc007f60) at mbcsv_act.c:393 #8 0x7f03c357fdb6 in ncs_mbcsv_rcv_async_update (peer=0x1493c10, evt=0x7f03bc007f60) at mbcsv_act.c:440 #9 0x7f03c35869a0 in mbcsv_process_events (rcvd_evt=0x7f03bc007f60, mbcsv_hdl=mbcsv_hdl@entry=4293918753) at mbcsv_pr_evts.c:168 #10 0x7f03c3586b0b in mbcsv_hdl_dispatch_all (mbcsv_hdl=4293918753, mbx=mbx@entry=4288675841) at mbcsv_pr_evts.c:272 #11 0x7f03c3581332 in mbcsv_process_dispatch_request (arg=0x7ffd0a965120) at mbcsv_api.c:423 #12 0x00409a42 in avsv_mbcsv_dispatch (cb=cb@entry=0x6c6400 <_control_block>, flag=flag@entry=2) at chkop.cc:839 #13 0x00405a0d in main_loop () at main.cc:715 #14 main (argc=, argv=) at main.cc:851 (gdb) --- 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.-- Transform Data into Opportunity. Accelerate data analysis in your applications with Intel Data Analytics Acceleration Library. Click to learn more. http://pubads.g.doubleclick.net/gampad/clk?id=278785471=/4140___ Opensaf-tickets mailing list Opensaf-tickets@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
[tickets] [opensaf:tickets] #2032 ckpt: ckpttest for long dn (5 55, 5 57, 7 12) is failing
--- ** [tickets:#2032] ckpt: ckpttest for long dn (5 55, 5 57, 7 12) is failing** **Status:** unassigned **Milestone:** 5.1.RC2 **Created:** Wed Sep 14, 2016 04:40 AM UTC by Quyen Dao **Last Updated:** Wed Sep 14, 2016 04:40 AM UTC **Owner:** nobody Changeset: 8064:99410ba8cc21 root@SC-1:~# immcfg -a longDnsAllowed=1 opensafImm=opensafImm,safApp=safImmService root@SC-1:~# export SA_ENABLE_EXTENDED_NAMES=1 root@SC-1:~# ckpttest 5 55 Suite 5: CKPT API saCkptCheckpointOpen() 55 FAILED To verify creating a ckpt with invalid extended name length (expected OUT_OF_RANGE, got SA_AIS_OK (1)); = Test Result: Total: 1 Passed: 0 Failed: 1 root@SC-1:~# ckpttest 5 57 Suite 5: CKPT API saCkptCheckpointOpen() 57 FAILED To verify openAsync a ckpt with invalid extended name length (expected OUT_OF_RANGE, got SA_AIS_OK (1)); = Test Result: Total: 1 Passed: 0 Failed: 1 root@SC-1:~# ckpttest 7 12 Suite 7: CKPT API saCkptCheckpointUnlink() 12 FAILED To test unlink a ckpt with invalid extended name (expected OUT_OF_RANGE, got SA_AIS_OK (1)); = Test Result: Total: 1 Passed: 0 Failed: 1 root@SC-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] #2177 MDS: mdstest 10 1 failed
--- ** [tickets:#2177] MDS: mdstest 10 1 failed** **Status:** unassigned **Milestone:** 5.2.FC **Created:** Tue Nov 08, 2016 06:48 AM UTC by Quyen Dao **Last Updated:** Tue Nov 08, 2016 06:48 AM UTC **Owner:** nobody **Attachments:** - [mdstest_10_1_mds.log](https://sourceforge.net/p/opensaf/tickets/2177/attachment/mdstest_10_1_mds.log) (121.2 kB; application/octet-stream) Changeset: 8287:bcc7af78a5a7 OS: Ubuntu 16.04 MDS transport: TCP root@SC-1:~# export MDS_LOG_LEVEL=5 root@SC-1:~# mdstest 10 1 Suite 10: Send All test cases Test Case 1: Sender service installed with i_fail_no_active_sends = true and there is no-active instance of the receiver service Setting up the setup /ntet_initialise_setup: Get an ADEST handle,Create PWE=2 on ADEST,Install EXTMIN and INTMIN svc on ADEST,Install INTMIN,EXTMIN services on ADEST's PWE=2, Create VDEST 100 and VDEST 200,Change the role of VDEST 200 to ACTIVE, Install EXTMIN service on VDEST 100,Install INTMIN, EXTMIN services on VDEST 200 ADEST <2010f020a > : GET_HDLS is SUCCESSFUL 100 : VDEST_CREATE is SUCCESSFUL 200 : VDEST_CREATE is SUCCESSFUL VDEST_CHANGE ROLE to 1 is SUCCESSFULL PWE_CREATE is SUCCESSFUL : PWE = 2 256 : SERVICE INSTALL is SUCCESSFULL 512 : SERVICE INSTALL is SUCCESSFULL 256 : SERVICE INSTALL is SUCCESSFULL 512 : SERVICE INSTALL is SUCCESSFULL 512 : SERVICE INSTALL is SUCCESSFULL 256 : SERVICE INSTALL is SUCCESSFULL 512 : SERVICE INSTALL is SUCCESSFULL MDS SERVICE SUBSCRIBE is SUCCESSFULL VDEST_CHANGE ROLE to 2 is SUCCESSFULL MDS RETRIEVE is SUCCESSFULL Sending the message to no active instance Encoding the message sent Sender svc = 512 with msg fmt ver =0 Successfully encoded message for Receiver svc = 512 MDS SEND is SUCCESSFULL Fail Sendack to the no active instance MDS SEND ACK has failed as there is no active instance Success Send response to the no active instance Request to ncsmds_api: MDS SEND RESPONSE has no active instance Change role to active VDEST_CHANGE ROLE to 1 is SUCCESSFULL The Subscriber Service id = 512 is on ADEST UP: Subscribed Svc = 512 with svc pvt ver = 1 is UP on dest= anchor= <0> role= 1 with PWE id = 1 on node = 2010f The Subscriber Service id = 512 is on ADEST UP: Subscribed Svc = 512 with svc pvt ver = 3 is UP on dest= <2010f020a> anchor= <0> role= 1 with PWE id = 1 on node = 2010f The Subscriber Service id = 512 is on ADEST NO ACTIVE: Received NO ACTIVE Event In the system no active instance of Subscribed srv= 512 with svc pvt ver = 1 on dest= found The Subscriber Service id = 512 is on ADEST NEW ACTIVE: Received NEW_ACTIVE Event In the system atleast one active instance of Subscribed service = 512 with svc pvt ver = 1 on destinatin = found MDS RETRIEVE is SUCCESSFULL Task has been Created Inside Receiver Thread The service which is sending the message is = 512 The service to which the message needs to be delivered = 512 Got the message: trying to retreive it The Sender service = 512 is on destination = with anchor = <2010f020a> Node 2010f and msg fmt ver = 3 The Receiver service = 512 is on destination =<2010f020a> Received Message len = 30 The message is= Hi Receiver! Are you there? MDS RETRIEVE is SUCCESSFULL VDEST_CHANGE ROLE to 2 is SUCCESSFULL The service which is sending the message is = 512 The service to which the message needs to be delivered = 512 MDS RESPONSE is SUCCESSFULL MDS SEND RESPONSE is SUCCESSFULL The response got from the receiver is : message length = 33 message = Hi Sender! My Name is RECEIVER Success TASK is released MDS CANCEL SUBSCRIBE is SUCCESSFULLUninstalling the services on both VDESTs and ADEST UnInstalling the Services on both the VDESTs MDS RETRIEVE is SUCCESSFULL 512 : SERVICE UNINSTALL is SUCCESSFULL MDS RETRIEVE is SUCCESSFULL 256 : SERVICE UNINSTALL is SUCCESSFULL MDS RETRIEVE is SUCCESSFULL 512 : SERVICE UNINSTALL is SUCCESSFULL Destroying the VDESTS Destroying both the VDESTs and PWE=2 on ADEST VDEST_CHANGE ROLE to 2 is SUCCESSFULL 200 : VDEST_DESTROY is SUCCESSFULL VDEST_CHANGE ROLE to 2 is SUCCESSFULL 100 : VDEST_DESTROY is SUCCESSFULL The Subscriber Service id = 512 is on ADEST NO ACTIVE: Received NO ACTIVE Event In the system no active instance of Subscribed srv= 512 with svc pvt ver = 1 on dest= found MDS RETRIEVE is SUCCESSFULL 512 : SERVICE UNINSTALL is SUCCESSFULL MDS RETRIEVE is SUCCESSFULL 256 : SERVICE UNINSTALL is SUCCESSFULL ADEST : PWE 2 : Uninstalling Services 2000/INTMIN MDS RETRIEVE is SUCCESSFULL 512 : SERVICE UNINSTALL is SUCCESSFULL MDS RETRIEVE is SUCCESSFULL 256 : SERVICE UNINSTALL is SUCCESSFULL ADEST PWE2 Destroyed ADEST: PWE_DESTROY is SUCCESSFUL1 FAILED Sender service installed with i_fail_no_active_sends = true and there is no-active instance of the receiver service (exp
[tickets] [opensaf:tickets] #2174 MDS: mdstest 5 1 failed
--- ** [tickets:#2174] MDS: mdstest 5 1 failed** **Status:** unassigned **Milestone:** 5.2.FC **Created:** Tue Nov 08, 2016 06:29 AM UTC by Quyen Dao **Last Updated:** Tue Nov 08, 2016 06:29 AM UTC **Owner:** nobody **Attachments:** - [mdstest_5_1_mds.log](https://sourceforge.net/p/opensaf/tickets/2174/attachment/mdstest_5_1_mds.log) (29.2 kB; application/octet-stream) Changeset: 8287:bcc7af78a5a7 OS: Ubuntu 16.04 MDS transport: TCP root@SC-1:~# export MDS_LOG_LEVEL=5 root@SC-1:~# mdstest 5 1 Suite 5: Subscribe ADEST Test Case 1: 500 Subscription to:600,700 where Install scope = Subscription scope Getting an ADEST handle ADEST <2010f01f3 > : GET_HDLS is SUCCESSFUL Installing the services 500,600,700 with CHASSIS scope 500 : SERVICE INSTALL is SUCCESSFULL 600 : SERVICE INSTALL is SUCCESSFULL 700 : SERVICE INSTALL is SUCCESSFULL Action: Retrieve only ONE event MDS SERVICE SUBSCRIBE is SUCCESSFULL Action: Retrieve only ONE event Request to ncsmds_api: MDS RETRIEVE has FAILED Fail, retrieve ONE Action: Retrieve ALL event The Subscriber Service id = 500 is on ADEST UP: Subscribed Svc = 600 with svc pvt ver = 1 is UP on dest= <2010f01f3> anchor= <0> role= 1 with PWE id = 1 on node = 2010f The Subscriber Service id = 500 is on ADEST UP: Subscribed Svc = 700 with svc pvt ver = 1 is UP on dest= <2010f01f3> anchor= <0> role= 1 with PWE id = 1 on node = 2010f MDS RETRIEVE is SUCCESSFULL Success Action: Cancel subscription 500 MDS CANCEL SUBSCRIBE is SUCCESSFULL Success Uninstalling all the services on this ADESt 700 : SERVICE UNINSTALL is SUCCESSFULL 600 : SERVICE UNINSTALL is SUCCESSFULL 500 : SERVICE UNINSTALL is SUCCESSFULL1 FAILEDIn the NO_ACTIVE event notification, the remote service subpart version is set to the last active instance.s remote-service sub-part version (expected OUT_OF_RANGE, got SA_AIS_OK (1)); = Test Result: Total: 1 Passed: 0 Failed: 1 root@SC-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.-- Developer Access Program for Intel Xeon Phi Processors Access to Intel Xeon Phi processor-based developer platforms. With one year of Intel Parallel Studio XE. Training and support from Colfax. Order your platform today. http://sdm.link/xeonphi___ Opensaf-tickets mailing list Opensaf-tickets@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
[tickets] [opensaf:tickets] #2176 MDS: mdstest 5 9 failed
--- ** [tickets:#2176] MDS: mdstest 5 9 failed** **Status:** unassigned **Milestone:** 5.2.FC **Created:** Tue Nov 08, 2016 06:38 AM UTC by Quyen Dao **Last Updated:** Tue Nov 08, 2016 06:38 AM UTC **Owner:** nobody **Attachments:** - [mdstest_5_9_mds.log](https://sourceforge.net/p/opensaf/tickets/2176/attachment/mdstest_5_9_mds.log) (29.8 kB; application/octet-stream) Changeset: 8287:bcc7af78a5a7 OS: Ubuntu 16.04 MDS transport: TCP root@SC-1:~# export MDS_LOG_LEVEL=5 root@SC-1:~# mdstest 5 9 Suite 5: Subscribe ADEST Getting an ADEST handle ADEST <2010f0205 > : GET_HDLS is SUCCESSFUL Installing the services 500,600,700 with CHASSIS scope 500 : SERVICE INSTALL is SUCCESSFULL 600 : SERVICE INSTALL is SUCCESSFULL 700 : SERVICE INSTALL is SUCCESSFULL Test Case 9: 500 Subscription to:600,700 in two seperate Subscription calls but Cancels both in a single cancellation call Action: Subscribe 500 to 600 MDS SERVICE SUBSCRIBE is SUCCESSFULL Action: Subscribe 500 to 700 MDS SERVICE SUBSCRIBE is SUCCESSFULL Action: Retreive three times, third shall fail Request to ncsmds_api: MDS RETRIEVE has FAILED Fail mds_service_retrieve Request to ncsmds_api: MDS RETRIEVE has FAILED Fail mds_service_retrieve Request to ncsmds_api: MDS RETRIEVE has FAILED Action: Cancel subscription MDS CANCEL SUBSCRIBE is SUCCESSFULL Success Uninstalling all the services on this ADESt 700 : SERVICE UNINSTALL is SUCCESSFULL 600 : SERVICE UNINSTALL is SUCCESSFULL 500 : SERVICE UNINSTALL is SUCCESSFULL9 FAILED500 Subscription to:600,700 in two seperate Subscription calls but Cancels both in a single cancellation call (expected OUT_OF_RANGE, got SA_AIS_OK (1)); = Test Result: Total: 1 Passed: 0 Failed: 1 root@SC-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.-- Developer Access Program for Intel Xeon Phi Processors Access to Intel Xeon Phi processor-based developer platforms. With one year of Intel Parallel Studio XE. Training and support from Colfax. Order your platform today. http://sdm.link/xeonphi___ Opensaf-tickets mailing list Opensaf-tickets@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
[tickets] [opensaf:tickets] #2178 MDS: mdstest 13 14 failed
--- ** [tickets:#2178] MDS: mdstest 13 14 failed** **Status:** unassigned **Milestone:** 5.2.FC **Created:** Tue Nov 08, 2016 06:58 AM UTC by Quyen Dao **Last Updated:** Tue Nov 08, 2016 06:58 AM UTC **Owner:** nobody **Attachments:** - [mdstest_13_14_mds.log](https://sourceforge.net/p/opensaf/tickets/2178/attachment/mdstest_13_14_mds.log) (65.8 kB; application/octet-stream) Changeset: 8287:bcc7af78a5a7 OS: Ubuntu 16.04 MDS transport: TCP root@SC-1:~# export MDS_LOG_LEVEL=5 root@SC-1:~# mdstest 13 14 Suite 13: Direct Just Send test cases /ntet_initialise_setup: Get an ADEST handle,Create PWE=2 on ADEST,Install EXTMIN and INTMIN svc on ADEST,Install INTMIN,EXTMIN services on ADEST's PWE=2, Create VDEST 100 and VDEST 200,Change the role of VDEST 200 to ACTIVE, Install EXTMIN service on VDEST 100,Install INTMIN, EXTMIN services on VDEST 200 ADEST <2010f021f > : GET_HDLS is SUCCESSFUL 100 : VDEST_CREATE is SUCCESSFUL 200 : VDEST_CREATE is SUCCESSFUL VDEST_CHANGE ROLE to 1 is SUCCESSFULL PWE_CREATE is SUCCESSFUL : PWE = 2 256 : SERVICE INSTALL is SUCCESSFULL 512 : SERVICE INSTALL is SUCCESSFULL 256 : SERVICE INSTALL is SUCCESSFULL 512 : SERVICE INSTALL is SUCCESSFULL 512 : SERVICE INSTALL is SUCCESSFULL 256 : SERVICE INSTALL is SUCCESSFULL 512 : SERVICE INSTALL is SUCCESSFULL MDS SERVICE SUBSCRIBE is SUCCESSFULL The Subscriber Service id = 512 is on ADEST UP: Subscribed Svc = 512 with svc pvt ver = 1 is UP on dest= anchor= <0> role= 1 with PWE id = 1 on node = 2010f The Subscriber Service id = 512 is on ADEST UP: Subscribed Svc = 512 with svc pvt ver = 3 is UP on dest= <2010f021f> anchor= <0> role= 1 with PWE id = 1 on node = 2010f MDS RETRIEVE is SUCCESSFULL Test Case 14: Not able to send a message of size >(MDS_DIRECT_BUF_MAXSIZE) to 2000 Request to ncsmds_api: MDS DIRECT SEND is SUCCESSFULL Fail Cancel subscription MDS CANCEL SUBSCRIBE is SUCCESSFULLUninstalling the services on both VDESTs and ADEST UnInstalling the Services on both the VDESTs MDS RETRIEVE is SUCCESSFULL 512 : SERVICE UNINSTALL is SUCCESSFULL MDS RETRIEVE is SUCCESSFULL 256 : SERVICE UNINSTALL is SUCCESSFULL MDS RETRIEVE is SUCCESSFULL 512 : SERVICE UNINSTALL is SUCCESSFULL Destroying the VDESTS Destroying both the VDESTs and PWE=2 on ADEST VDEST_CHANGE ROLE to 2 is SUCCESSFULL 200 : VDEST_DESTROY is SUCCESSFULL VDEST_CHANGE ROLE to 2 is SUCCESSFULL 100 : VDEST_DESTROY is SUCCESSFULL Direct Receive callback The Sender service is = 512 is on <2010f021f> destination with anchor = <2010f021f> on Node = 2010f with msg fmt ver=1 The Receiver service is = 512 is on <2010f021f> destination Received Message len = 8002 and the message is=sss s ss
[tickets] [opensaf:tickets] Re: #2174 MDS: mdstest 5 1 failed
no special confugration was used to produce this bug. 2 SCs + 3 PLs OS: Ubuntu 16.04 MDS transport: TCP The attachment (mdstest_5_1_mds.log) is not enough for troubleshooting? I will try to reproduce again, in case I can reproduce what else (log, trace) that you need? --- ** [tickets:#2174] MDS: mdstest 5 1 failed** **Status:** accepted **Milestone:** 5.2.RC2 **Created:** Tue Nov 08, 2016 06:29 AM UTC by Quyen Dao **Last Updated:** Thu Mar 23, 2017 06:39 AM UTC **Owner:** A V Mahesh (AVM) **Attachments:** - [mdstest_5_1_mds.log](https://sourceforge.net/p/opensaf/tickets/2174/attachment/mdstest_5_1_mds.log) (29.2 kB; application/octet-stream) Changeset: 8287:bcc7af78a5a7 OS: Ubuntu 16.04 MDS transport: TCP root@SC-1:~# export MDS_LOG_LEVEL=5 root@SC-1:~# mdstest 5 1 Suite 5: Subscribe ADEST Test Case 1: 500 Subscription to:600,700 where Install scope = Subscription scope Getting an ADEST handle ADEST <2010f01f3 > : GET_HDLS is SUCCESSFUL Installing the services 500,600,700 with CHASSIS scope 500 : SERVICE INSTALL is SUCCESSFULL 600 : SERVICE INSTALL is SUCCESSFULL 700 : SERVICE INSTALL is SUCCESSFULL Action: Retrieve only ONE event MDS SERVICE SUBSCRIBE is SUCCESSFULL Action: Retrieve only ONE event Request to ncsmds_api: MDS RETRIEVE has FAILED Fail, retrieve ONE Action: Retrieve ALL event The Subscriber Service id = 500 is on ADEST UP: Subscribed Svc = 600 with svc pvt ver = 1 is UP on dest= <2010f01f3> anchor= <0> role= 1 with PWE id = 1 on node = 2010f The Subscriber Service id = 500 is on ADEST UP: Subscribed Svc = 700 with svc pvt ver = 1 is UP on dest= <2010f01f3> anchor= <0> role= 1 with PWE id = 1 on node = 2010f MDS RETRIEVE is SUCCESSFULL Success Action: Cancel subscription 500 MDS CANCEL SUBSCRIBE is SUCCESSFULL Success Uninstalling all the services on this ADESt 700 : SERVICE UNINSTALL is SUCCESSFULL 600 : SERVICE UNINSTALL is SUCCESSFULL 500 : SERVICE UNINSTALL is SUCCESSFULL1 FAILEDIn the NO_ACTIVE event notification, the remote service subpart version is set to the last active instance.s remote-service sub-part version (expected OUT_OF_RANGE, got SA_AIS_OK (1)); = Test Result: Total: 1 Passed: 0 Failed: 1 root@SC-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.-- 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] #2177 MDS: mdstest 10 1 failed
I can't reproduce the problem again. In case the mdstest_10_1_mds.log is not enough for troubleshooting, please help move the status to not-reproducible. --- ** [tickets:#2177] MDS: mdstest 10 1 failed** **Status:** accepted **Milestone:** 5.2.RC2 **Created:** Tue Nov 08, 2016 06:48 AM UTC by Quyen Dao **Last Updated:** Thu Mar 23, 2017 07:01 AM UTC **Owner:** A V Mahesh (AVM) **Attachments:** - [mdstest_10_1_mds.log](https://sourceforge.net/p/opensaf/tickets/2177/attachment/mdstest_10_1_mds.log) (121.2 kB; application/octet-stream) Changeset: 8287:bcc7af78a5a7 OS: Ubuntu 16.04 MDS transport: TCP root@SC-1:~# export MDS_LOG_LEVEL=5 root@SC-1:~# mdstest 10 1 Suite 10: Send All test cases Test Case 1: Sender service installed with i_fail_no_active_sends = true and there is no-active instance of the receiver service Setting up the setup /ntet_initialise_setup: Get an ADEST handle,Create PWE=2 on ADEST,Install EXTMIN and INTMIN svc on ADEST,Install INTMIN,EXTMIN services on ADEST's PWE=2, Create VDEST 100 and VDEST 200,Change the role of VDEST 200 to ACTIVE, Install EXTMIN service on VDEST 100,Install INTMIN, EXTMIN services on VDEST 200 ADEST <2010f020a > : GET_HDLS is SUCCESSFUL 100 : VDEST_CREATE is SUCCESSFUL 200 : VDEST_CREATE is SUCCESSFUL VDEST_CHANGE ROLE to 1 is SUCCESSFULL PWE_CREATE is SUCCESSFUL : PWE = 2 256 : SERVICE INSTALL is SUCCESSFULL 512 : SERVICE INSTALL is SUCCESSFULL 256 : SERVICE INSTALL is SUCCESSFULL 512 : SERVICE INSTALL is SUCCESSFULL 512 : SERVICE INSTALL is SUCCESSFULL 256 : SERVICE INSTALL is SUCCESSFULL 512 : SERVICE INSTALL is SUCCESSFULL MDS SERVICE SUBSCRIBE is SUCCESSFULL VDEST_CHANGE ROLE to 2 is SUCCESSFULL MDS RETRIEVE is SUCCESSFULL Sending the message to no active instance Encoding the message sent Sender svc = 512 with msg fmt ver =0 Successfully encoded message for Receiver svc = 512 MDS SEND is SUCCESSFULL Fail Sendack to the no active instance MDS SEND ACK has failed as there is no active instance Success Send response to the no active instance Request to ncsmds_api: MDS SEND RESPONSE has no active instance Change role to active VDEST_CHANGE ROLE to 1 is SUCCESSFULL The Subscriber Service id = 512 is on ADEST UP: Subscribed Svc = 512 with svc pvt ver = 1 is UP on dest= anchor= <0> role= 1 with PWE id = 1 on node = 2010f The Subscriber Service id = 512 is on ADEST UP: Subscribed Svc = 512 with svc pvt ver = 3 is UP on dest= <2010f020a> anchor= <0> role= 1 with PWE id = 1 on node = 2010f The Subscriber Service id = 512 is on ADEST NO ACTIVE: Received NO ACTIVE Event In the system no active instance of Subscribed srv= 512 with svc pvt ver = 1 on dest= found The Subscriber Service id = 512 is on ADEST NEW ACTIVE: Received NEW_ACTIVE Event In the system atleast one active instance of Subscribed service = 512 with svc pvt ver = 1 on destinatin = found MDS RETRIEVE is SUCCESSFULL Task has been Created Inside Receiver Thread The service which is sending the message is = 512 The service to which the message needs to be delivered = 512 Got the message: trying to retreive it The Sender service = 512 is on destination = with anchor = <2010f020a> Node 2010f and msg fmt ver = 3 The Receiver service = 512 is on destination =<2010f020a> Received Message len = 30 The message is= Hi Receiver! Are you there? MDS RETRIEVE is SUCCESSFULL VDEST_CHANGE ROLE to 2 is SUCCESSFULL The service which is sending the message is = 512 The service to which the message needs to be delivered = 512 MDS RESPONSE is SUCCESSFULL MDS SEND RESPONSE is SUCCESSFULL The response got from the receiver is : message length = 33 message = Hi Sender! My Name is RECEIVER Success TASK is released MDS CANCEL SUBSCRIBE is SUCCESSFULLUninstalling the services on both VDESTs and ADEST UnInstalling the Services on both the VDESTs MDS RETRIEVE is SUCCESSFULL 512 : SERVICE UNINSTALL is SUCCESSFULL MDS RETRIEVE is SUCCESSFULL 256 : SERVICE UNINSTALL is SUCCESSFULL MDS RETRIEVE is SUCCESSFULL 512 : SERVICE UNINSTALL is SUCCESSFULL Destroying the VDESTS Destroying both the VDESTs and PWE=2 on ADEST VDEST_CHANGE ROLE to 2 is SUCCESSFULL 200 : VDEST_DESTROY is SUCCESSFULL VDEST_CHANGE ROLE to 2 is SUCCESSFULL 100 : VDEST_DESTROY is SUCCESSFULL The Subscriber Service id = 512 is on ADEST NO ACTIVE: Received NO ACTIVE Event In the system no active instance of Subscribed srv= 512 with svc pvt ver = 1 on dest= found MDS RETRIEVE is SUCCESSFULL 512 : SERVICE UNINSTALL is SUCCESSFULL MDS RETRIEVE is SUCCESSFULL 256 : SERVICE UNINSTALL is SUCCESSFULL ADEST : PWE 2 : Uninstalling Services 2000/INTMIN MDS RETRIEVE is SUCCESSFULL 512 : SERVICE UNINSTALL is SUCCESSFULL MDS RETRIEVE is SUCCESSFULL 256 : SERVICE UNINSTALL is SUCCESSFULL ADEST PWE2 Destroyed ADEST: PWE_DESTROY is SUCCESSFUL1 FAILED Sender service installed with i_fail_no_active
[tickets] [opensaf:tickets] #2174 MDS: mdstest 5 1 failed
I can't reproduce the problem again. In case the mdstest_5_1_mds.log is not enough for troubleshooting, please move the status to not-reproducible. --- ** [tickets:#2174] MDS: mdstest 5 1 failed** **Status:** accepted **Milestone:** 5.2.RC2 **Created:** Tue Nov 08, 2016 06:29 AM UTC by Quyen Dao **Last Updated:** Thu Mar 23, 2017 06:39 AM UTC **Owner:** A V Mahesh (AVM) **Attachments:** - [mdstest_5_1_mds.log](https://sourceforge.net/p/opensaf/tickets/2174/attachment/mdstest_5_1_mds.log) (29.2 kB; application/octet-stream) Changeset: 8287:bcc7af78a5a7 OS: Ubuntu 16.04 MDS transport: TCP root@SC-1:~# export MDS_LOG_LEVEL=5 root@SC-1:~# mdstest 5 1 Suite 5: Subscribe ADEST Test Case 1: 500 Subscription to:600,700 where Install scope = Subscription scope Getting an ADEST handle ADEST <2010f01f3 > : GET_HDLS is SUCCESSFUL Installing the services 500,600,700 with CHASSIS scope 500 : SERVICE INSTALL is SUCCESSFULL 600 : SERVICE INSTALL is SUCCESSFULL 700 : SERVICE INSTALL is SUCCESSFULL Action: Retrieve only ONE event MDS SERVICE SUBSCRIBE is SUCCESSFULL Action: Retrieve only ONE event Request to ncsmds_api: MDS RETRIEVE has FAILED Fail, retrieve ONE Action: Retrieve ALL event The Subscriber Service id = 500 is on ADEST UP: Subscribed Svc = 600 with svc pvt ver = 1 is UP on dest= <2010f01f3> anchor= <0> role= 1 with PWE id = 1 on node = 2010f The Subscriber Service id = 500 is on ADEST UP: Subscribed Svc = 700 with svc pvt ver = 1 is UP on dest= <2010f01f3> anchor= <0> role= 1 with PWE id = 1 on node = 2010f MDS RETRIEVE is SUCCESSFULL Success Action: Cancel subscription 500 MDS CANCEL SUBSCRIBE is SUCCESSFULL Success Uninstalling all the services on this ADESt 700 : SERVICE UNINSTALL is SUCCESSFULL 600 : SERVICE UNINSTALL is SUCCESSFULL 500 : SERVICE UNINSTALL is SUCCESSFULL1 FAILEDIn the NO_ACTIVE event notification, the remote service subpart version is set to the last active instance.s remote-service sub-part version (expected OUT_OF_RANGE, got SA_AIS_OK (1)); = Test Result: Total: 1 Passed: 0 Failed: 1 root@SC-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.-- 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] #2176 MDS: mdstest 5 9 failed
I can't reproduce the problem again. In case the mdstest_5_9_mds.log is not enough for troubleshooting, please help move the status to not-reproducible. --- ** [tickets:#2176] MDS: mdstest 5 9 failed** **Status:** accepted **Milestone:** 5.2.RC2 **Created:** Tue Nov 08, 2016 06:38 AM UTC by Quyen Dao **Last Updated:** Thu Mar 23, 2017 06:57 AM UTC **Owner:** A V Mahesh (AVM) **Attachments:** - [mdstest_5_9_mds.log](https://sourceforge.net/p/opensaf/tickets/2176/attachment/mdstest_5_9_mds.log) (29.8 kB; application/octet-stream) Changeset: 8287:bcc7af78a5a7 OS: Ubuntu 16.04 MDS transport: TCP root@SC-1:~# export MDS_LOG_LEVEL=5 root@SC-1:~# mdstest 5 9 Suite 5: Subscribe ADEST Getting an ADEST handle ADEST <2010f0205 > : GET_HDLS is SUCCESSFUL Installing the services 500,600,700 with CHASSIS scope 500 : SERVICE INSTALL is SUCCESSFULL 600 : SERVICE INSTALL is SUCCESSFULL 700 : SERVICE INSTALL is SUCCESSFULL Test Case 9: 500 Subscription to:600,700 in two seperate Subscription calls but Cancels both in a single cancellation call Action: Subscribe 500 to 600 MDS SERVICE SUBSCRIBE is SUCCESSFULL Action: Subscribe 500 to 700 MDS SERVICE SUBSCRIBE is SUCCESSFULL Action: Retreive three times, third shall fail Request to ncsmds_api: MDS RETRIEVE has FAILED Fail mds_service_retrieve Request to ncsmds_api: MDS RETRIEVE has FAILED Fail mds_service_retrieve Request to ncsmds_api: MDS RETRIEVE has FAILED Action: Cancel subscription MDS CANCEL SUBSCRIBE is SUCCESSFULL Success Uninstalling all the services on this ADESt 700 : SERVICE UNINSTALL is SUCCESSFULL 600 : SERVICE UNINSTALL is SUCCESSFULL 500 : SERVICE UNINSTALL is SUCCESSFULL9 FAILED500 Subscription to:600,700 in two seperate Subscription calls but Cancels both in a single cancellation call (expected OUT_OF_RANGE, got SA_AIS_OK (1)); = Test Result: Total: 1 Passed: 0 Failed: 1 root@SC-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.-- 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] #2360 mdstest 14 4 failed
I can't reproduce the problem again. In case the full stack trace is not enough
for troubleshooting, please help move the status to not-reproducible.
---
** [tickets:#2360] mdstest 14 4 failed**
**Status:** accepted
**Milestone:** 5.2.RC2
**Created:** Fri Mar 10, 2017 02:31 AM UTC by Quyen Dao
**Last Updated:** Thu Mar 23, 2017 07:05 AM UTC
**Owner:** A V Mahesh (AVM)
changset: 8521:05a15c96f745
mdstest 14 4 failed and coredump was also generated.
**mdstest output**
(Suite 14): Direct send a message with i_msg_fmt_ver < i_rem_svc_pvt_ver for
all send types
Command: 'mdstest 14 4'
rc: 139 - output:
Suite 14: Direct Send All test cases
/ntet_initialise_setup: Get an ADEST handle,Create PWE=2 on ADEST,Install
EXTMIN and INTMIN svc on ADEST,Install INTMIN,EXTMIN services on ADEST's PWE=2,
Create VDEST 100 and VDEST 200,Change the role of VDEST 200 to ACTIVE,
Install EXTMIN service on VDEST 100,Install INTMIN, EXTMIN services on VDEST 200
ADEST <2010f0578 > : GET_HDLS is SUCCESSFUL
100 : VDEST_CREATE is SUCCESSFUL
200 : VDEST_CREATE is SUCCESSFUL
VDEST_CHANGE ROLE to 1 is SUCCESSFULL
PWE_CREATE is SUCCESSFUL : PWE = 2
256 : SERVICE INSTALL is SUCCESSFULL
512 : SERVICE INSTALL is SUCCESSFULL
256 : SERVICE INSTALL is SUCCESSFULL
512 : SERVICE INSTALL is SUCCESSFULL
512 : SERVICE INSTALL is SUCCESSFULL
256 : SERVICE INSTALL is SUCCESSFULL
512 : SERVICE INSTALL is SUCCESSFULL
MDS SERVICE SUBSCRIBE is SUCCESSFULL
MDS RETRIEVE is SUCCESSFULL
Test Case 4: Direct send a message with i_msg_fmt_ver < i_rem_svc_pvt_ver for
all send types
Direct sending the message
Request to ncsmds_api: MDS DIRECT SEND is SUCCESSFULL
Success
Direct send with ack
Request to ncsmds_api: MDS DIRECT SEND is SUCCESSFULL
Success
Direct send with rsp
Task has been Created
Inside Receiver Thread
Direct Receive callback
The Sender service is = 512 is on <2010f0578> destination with anchor =
<2010f0578> on Node = 2010f with msg fmt ver=2
The Receiver service is = 512 is on <2010f0578> destination
Received Message len = 15 and the message is=Direct Message
Direct Receive callback
The Sender service is = 512 is on <2010f0578> destination with anchor =
<2010f0578> on Node = 2010f with msg fmt ver=2
The Receiver service is = 512 is on <2010f0578> destination
Received Message len = 15 and the message is=Direct Message
MDS RETRIEVE is SUCCESSFULL
**Full stacktrace**
2017-02-28 00:19:46,582 INFO - Printing stack trace of
core.1488237250.mdstest.1400.SC-1 which occurs on 2017-02-28 00:14:10 - OpenSAF
5.2.M0 - 8521:05a15c96f745:default
2017-02-28 00:19:46,617 DEBUG - exec cmd 'ls /usr/local/lib/opensaf/mdstest' on
SC-1
2017-02-28 00:19:46,617 DEBUG - SC-1: command: timeout 180 ssh
-oStrictHostKeyChecking=no -oLogLevel=quiet -l root 10.0.3.101 'ls
/usr/local/lib/opensaf/mdstest'
2017-02-28 00:19:46,721 DEBUG - SC-1: output: ls: cannot access
/usr/local/lib/opensaf/mdstest: No such file or directory
2017-02-28 00:19:46,722 DEBUG - exec cmd 'ls /usr/local/bin/mdstest' on SC-1
2017-02-28 00:19:46,722 DEBUG - SC-1: command: timeout 180 ssh
-oStrictHostKeyChecking=no -oLogLevel=quiet -l root 10.0.3.101 'ls
/usr/local/bin/mdstest'
2017-02-28 00:19:46,813 DEBUG - SC-1: output: /usr/local/bin/mdstest
2017-02-28 00:19:47,324 INFO - Stack trace of core.1488237250.mdstest.1400.SC-1
[New LWP 1400]
[New LWP 1403]
[New LWP 1402]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
Core was generated by `mdstest 14 4'.
Program terminated with signal SIGSEGV, Segmentation fault.
#0 __GI___libc_free (mem=0x2) at malloc.c:2929
Thread 3 (Thread 0x7f09902dcb00 (LWP 1402)):
#0 0x7f098f89cfdd in poll () at ../sysdeps/unix/syscall-template.S:81
No locals.
#1 0x7f098fdf342f in osaf_poll_no_timeout (io_fds=0x7f09902dc290, i_nfds=1)
at src/base/osaf_poll.c:32
result = 32521
#2 0x7f098fdf35dc in osaf_ppoll (io_fds=0x7f09902dc290, i_nfds=1,
i_timeout_ts=0x0, i_sigmask=0x0) at src/base/osaf_poll.c:79
millisecond_round_up = {tv_sec = 0, tv_nsec = 99}
max_possible_timeout = {tv_sec = 2147483, tv_nsec = 64700}
start_time = {tv_sec = 17179869186, tv_nsec = 139679050353408}
time_left_ts = {tv_sec = 1, tv_nsec = 1}
result = -1881212185
#3 0x7f098fe03e72 in ncs_tmr_wait () at src/base/sysf_tmr.c:406
rc = 1
inds_rmvd = 1
next_delay = 0
tv = {tv_sec = 16777215, tv_usec = 0}
ts_current = {tv_sec = 1690320, tv_nsec = 555370206}
ts = {tv_sec = 16777215, tv_nsec = 0}
set = {fd = 4, events = 1, revents = 0}
#4 0x7f098fb7d184 in start_thread (arg=0x7f09902dcb00) at
pthread_create.c:312
__res =
pd = 0x7f09902dcb00
now =
unwind_buf = {cancel_jmp_buf = {{jmp_buf = {139679050353408,
3247344970407365903, 1, 1, 139679050354112, 139679050353408,
-3241532557782135537, -3241469800302359281}, mask_was_saved = 0}}, priv = {pad
= {0x0, 0x0, 0x0, 0x0}, data = {prev = 0x0, cleanup =
[tickets] [opensaf:tickets] #2360 mdstest 14 4 failed
---
** [tickets:#2360] mdstest 14 4 failed**
**Status:** unassigned
**Milestone:** 5.2.RC1
**Created:** Fri Mar 10, 2017 02:31 AM UTC by Quyen Dao
**Last Updated:** Fri Mar 10, 2017 02:31 AM UTC
**Owner:** nobody
changset: 8521:05a15c96f745
mdstest 14 4 failed and coredump was also generated.
**mdstest output**
(Suite 14): Direct send a message with i_msg_fmt_ver < i_rem_svc_pvt_ver for
all send types
Command: 'mdstest 14 4'
rc: 139 - output:
Suite 14: Direct Send All test cases
/ntet_initialise_setup: Get an ADEST handle,Create PWE=2 on ADEST,Install
EXTMIN and INTMIN svc on ADEST,Install INTMIN,EXTMIN services on ADEST's PWE=2,
Create VDEST 100 and VDEST 200,Change the role of VDEST 200 to ACTIVE,
Install EXTMIN service on VDEST 100,Install INTMIN, EXTMIN services on VDEST 200
ADEST <2010f0578 > : GET_HDLS is SUCCESSFUL
100 : VDEST_CREATE is SUCCESSFUL
200 : VDEST_CREATE is SUCCESSFUL
VDEST_CHANGE ROLE to 1 is SUCCESSFULL
PWE_CREATE is SUCCESSFUL : PWE = 2
256 : SERVICE INSTALL is SUCCESSFULL
512 : SERVICE INSTALL is SUCCESSFULL
256 : SERVICE INSTALL is SUCCESSFULL
512 : SERVICE INSTALL is SUCCESSFULL
512 : SERVICE INSTALL is SUCCESSFULL
256 : SERVICE INSTALL is SUCCESSFULL
512 : SERVICE INSTALL is SUCCESSFULL
MDS SERVICE SUBSCRIBE is SUCCESSFULL
MDS RETRIEVE is SUCCESSFULL
Test Case 4: Direct send a message with i_msg_fmt_ver < i_rem_svc_pvt_ver for
all send types
Direct sending the message
Request to ncsmds_api: MDS DIRECT SEND is SUCCESSFULL
Success
Direct send with ack
Request to ncsmds_api: MDS DIRECT SEND is SUCCESSFULL
Success
Direct send with rsp
Task has been Created
Inside Receiver Thread
Direct Receive callback
The Sender service is = 512 is on <2010f0578> destination with anchor =
<2010f0578> on Node = 2010f with msg fmt ver=2
The Receiver service is = 512 is on <2010f0578> destination
Received Message len = 15 and the message is=Direct Message
Direct Receive callback
The Sender service is = 512 is on <2010f0578> destination with anchor =
<2010f0578> on Node = 2010f with msg fmt ver=2
The Receiver service is = 512 is on <2010f0578> destination
Received Message len = 15 and the message is=Direct Message
MDS RETRIEVE is SUCCESSFULL
**Full stacktrace**
2017-02-28 00:19:46,582 INFO - Printing stack trace of
core.1488237250.mdstest.1400.SC-1 which occurs on 2017-02-28 00:14:10 - OpenSAF
5.2.M0 - 8521:05a15c96f745:default
2017-02-28 00:19:46,617 DEBUG - exec cmd 'ls /usr/local/lib/opensaf/mdstest' on
SC-1
2017-02-28 00:19:46,617 DEBUG - SC-1: command: timeout 180 ssh
-oStrictHostKeyChecking=no -oLogLevel=quiet -l root 10.0.3.101 'ls
/usr/local/lib/opensaf/mdstest'
2017-02-28 00:19:46,721 DEBUG - SC-1: output: ls: cannot access
/usr/local/lib/opensaf/mdstest: No such file or directory
2017-02-28 00:19:46,722 DEBUG - exec cmd 'ls /usr/local/bin/mdstest' on SC-1
2017-02-28 00:19:46,722 DEBUG - SC-1: command: timeout 180 ssh
-oStrictHostKeyChecking=no -oLogLevel=quiet -l root 10.0.3.101 'ls
/usr/local/bin/mdstest'
2017-02-28 00:19:46,813 DEBUG - SC-1: output: /usr/local/bin/mdstest
2017-02-28 00:19:47,324 INFO - Stack trace of core.1488237250.mdstest.1400.SC-1
[New LWP 1400]
[New LWP 1403]
[New LWP 1402]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
Core was generated by `mdstest 14 4'.
Program terminated with signal SIGSEGV, Segmentation fault.
#0 __GI___libc_free (mem=0x2) at malloc.c:2929
Thread 3 (Thread 0x7f09902dcb00 (LWP 1402)):
#0 0x7f098f89cfdd in poll () at ../sysdeps/unix/syscall-template.S:81
No locals.
#1 0x7f098fdf342f in osaf_poll_no_timeout (io_fds=0x7f09902dc290, i_nfds=1)
at src/base/osaf_poll.c:32
result = 32521
#2 0x7f098fdf35dc in osaf_ppoll (io_fds=0x7f09902dc290, i_nfds=1,
i_timeout_ts=0x0, i_sigmask=0x0) at src/base/osaf_poll.c:79
millisecond_round_up = {tv_sec = 0, tv_nsec = 99}
max_possible_timeout = {tv_sec = 2147483, tv_nsec = 64700}
start_time = {tv_sec = 17179869186, tv_nsec = 139679050353408}
time_left_ts = {tv_sec = 1, tv_nsec = 1}
result = -1881212185
#3 0x7f098fe03e72 in ncs_tmr_wait () at src/base/sysf_tmr.c:406
rc = 1
inds_rmvd = 1
next_delay = 0
tv = {tv_sec = 16777215, tv_usec = 0}
ts_current = {tv_sec = 1690320, tv_nsec = 555370206}
ts = {tv_sec = 16777215, tv_nsec = 0}
set = {fd = 4, events = 1, revents = 0}
#4 0x7f098fb7d184 in start_thread (arg=0x7f09902dcb00) at
pthread_create.c:312
__res =
pd = 0x7f09902dcb00
now =
unwind_buf = {cancel_jmp_buf = {{jmp_buf = {139679050353408,
3247344970407365903, 1, 1, 139679050354112, 139679050353408,
-3241532557782135537, -3241469800302359281}, mask_was_saved = 0}}, priv = {pad
= {0x0, 0x0, 0x0, 0x0}, data = {prev = 0x0, cleanup = 0x0, canceltype = 0}}}
not_first_call =
pagesize_m1 =
sp =
freesize =
__PRETTY_FUNCTION__ = "start_thread"
#5 0x7f098f8aa37d in clone () at
[tickets] [opensaf:tickets] #2594 AMF: Improve SC status change callback
- Description has changed: Diff: --- old +++ new @@ -1,12 +1,12 @@ The SC status change callback declaration/definition is not consistent with other AMF callbacks. -1. It doesn't have an alias for callback type (defined by typdef) as the others +1) It doesn't have an alias for callback type (defined by typdef) as the others extern SaAisErrorT osafAmfInstallSCStatusChangeCallback( SaAmfHandleT amfHandle, void (*OsafAmfSCStatusChangeCallbackT)(OsafAmfSCStatusT status)); -2. Callback name is not correct. It should not end with T as it's not a type +2) Callback name is not correct. It should not end with T as it's not a type static void (*OsafAmfSCStatusChangeCallbackT)(OsafAmfSCStatusT state); --- ** [tickets:#2594] AMF: Improve SC status change callback** **Status:** accepted **Milestone:** 5.17.10 **Created:** Tue Sep 26, 2017 02:34 AM UTC by Quyen Dao **Last Updated:** Tue Sep 26, 2017 02:36 AM UTC **Owner:** Quyen Dao The SC status change callback declaration/definition is not consistent with other AMF callbacks. 1) It doesn't have an alias for callback type (defined by typdef) as the others extern SaAisErrorT osafAmfInstallSCStatusChangeCallback( SaAmfHandleT amfHandle, void (*OsafAmfSCStatusChangeCallbackT)(OsafAmfSCStatusT status)); 2) Callback name is not correct. It should not end with T as it's not a type static void (*OsafAmfSCStatusChangeCallbackT)(OsafAmfSCStatusT state); Beside that the current declaration/definition of SC status change call may cause issue for the script that automatically generates the python AIS interface in #2471 as it's not consistent with other AMF callbacks --- 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] #2594 AMF: Improve SC status change callback
--- ** [tickets:#2594] AMF: Improve SC status change callback** **Status:** accepted **Milestone:** 5.17.10 **Created:** Tue Sep 26, 2017 02:34 AM UTC by Quyen Dao **Last Updated:** Tue Sep 26, 2017 02:34 AM UTC **Owner:** Quyen Dao The SC status change callback declaration/definition is not consistent with other AMF callbacks. 1. It doesn't have an alias for callback type (defined by typdef) as the others extern SaAisErrorT osafAmfInstallSCStatusChangeCallback( SaAmfHandleT amfHandle, void (*OsafAmfSCStatusChangeCallbackT)(OsafAmfSCStatusT status)); 2. Callback name is not correct. It should not end with T as it's not a type static void (*OsafAmfSCStatusChangeCallbackT)(OsafAmfSCStatusT state); Beside that the current declaration/definition of SC status change call may cause issue for the script that automatically generates the python AIS interface in #2471 as it's not consistent with other AMF callbacks --- 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] #2594 AMF: Improve SC status change callback
- Description has changed: Diff: --- old +++ new @@ -2,12 +2,14 @@ 1) It doesn't have an alias for callback type (defined by typdef) as the others +~~~ extern SaAisErrorT osafAmfInstallSCStatusChangeCallback( SaAmfHandleT amfHandle, void (*OsafAmfSCStatusChangeCallbackT)(OsafAmfSCStatusT status)); +~~~ 2) Callback name is not correct. It should not end with T as it's not a type -static void (*OsafAmfSCStatusChangeCallbackT)(OsafAmfSCStatusT state); +`static void (*OsafAmfSCStatusChangeCallbackT)(OsafAmfSCStatusT state);` Beside that the current declaration/definition of SC status change call may cause issue for the script that automatically generates the python AIS interface in #2471 as it's not consistent with other AMF callbacks --- ** [tickets:#2594] AMF: Improve SC status change callback** **Status:** accepted **Milestone:** 5.17.10 **Created:** Tue Sep 26, 2017 02:34 AM UTC by Quyen Dao **Last Updated:** Tue Sep 26, 2017 02:39 AM UTC **Owner:** Quyen Dao The SC status change callback declaration/definition is not consistent with other AMF callbacks. 1) It doesn't have an alias for callback type (defined by typdef) as the others ~~~ extern SaAisErrorT osafAmfInstallSCStatusChangeCallback( SaAmfHandleT amfHandle, void (*OsafAmfSCStatusChangeCallbackT)(OsafAmfSCStatusT status)); ~~~ 2) Callback name is not correct. It should not end with T as it's not a type `static void (*OsafAmfSCStatusChangeCallbackT)(OsafAmfSCStatusT state);` Beside that the current declaration/definition of SC status change call may cause issue for the script that automatically generates the python AIS interface in #2471 as it's not consistent with other AMF callbacks --- 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] #2594 AMF: Improve SC status change callback
- **status**: accepted --> review --- ** [tickets:#2594] AMF: Improve SC status change callback** **Status:** review **Milestone:** 5.17.10 **Created:** Tue Sep 26, 2017 02:34 AM UTC by Quyen Dao **Last Updated:** Tue Sep 26, 2017 02:39 AM UTC **Owner:** Quyen Dao The SC status change callback declaration/definition is not consistent with other AMF callbacks. 1) It doesn't have an alias for callback type (defined by typdef) as the others ~~~ extern SaAisErrorT osafAmfInstallSCStatusChangeCallback( SaAmfHandleT amfHandle, void (*OsafAmfSCStatusChangeCallbackT)(OsafAmfSCStatusT status)); ~~~ 2) Callback name is not correct. It should not end with T as it's not a type `static void (*OsafAmfSCStatusChangeCallbackT)(OsafAmfSCStatusT state);` Beside that the current declaration/definition of SC status change call may cause issue for the script that automatically generates the python AIS interface in #2471 as it's not consistent with other AMF callbacks --- 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] #2594 AMF: Improve SC status change callback
- Description has changed: Diff: --- old +++ new @@ -1,12 +1,12 @@ The SC status change callback declaration/definition is not consistent with other AMF callbacks. -1. It doesn't have an alias for callback type (defined by typdef) as the others +1. It doesn't have an alias for callback type (defined by typdef) as the others extern SaAisErrorT osafAmfInstallSCStatusChangeCallback( SaAmfHandleT amfHandle, void (*OsafAmfSCStatusChangeCallbackT)(OsafAmfSCStatusT status)); -2. Callback name is not correct. It should not end with T as it's not a type +2. Callback name is not correct. It should not end with T as it's not a type static void (*OsafAmfSCStatusChangeCallbackT)(OsafAmfSCStatusT state); --- ** [tickets:#2594] AMF: Improve SC status change callback** **Status:** accepted **Milestone:** 5.17.10 **Created:** Tue Sep 26, 2017 02:34 AM UTC by Quyen Dao **Last Updated:** Tue Sep 26, 2017 02:34 AM UTC **Owner:** Quyen Dao The SC status change callback declaration/definition is not consistent with other AMF callbacks. 1. It doesn't have an alias for callback type (defined by typdef) as the others extern SaAisErrorT osafAmfInstallSCStatusChangeCallback( SaAmfHandleT amfHandle, void (*OsafAmfSCStatusChangeCallbackT)(OsafAmfSCStatusT status)); 2. Callback name is not correct. It should not end with T as it's not a type static void (*OsafAmfSCStatusChangeCallbackT)(OsafAmfSCStatusT state); Beside that the current declaration/definition of SC status change call may cause issue for the script that automatically generates the python AIS interface in #2471 as it's not consistent with other AMF callbacks --- 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
