[tickets] [opensaf:tickets] #2746 mds: mds test is not thread safe
--- ** [tickets:#2746] mds: mds test is not thread safe** **Status:** unassigned **Milestone:** 5.18.01 **Created:** Thu Dec 21, 2017 07:25 AM UTC by Hans Nordebäck **Last Updated:** Thu Dec 21, 2017 07:25 AM UTC **Owner:** nobody there are several data races related to e.g. svc_to_mds_info structure, one example below: Possible data race during write of size 4 at 0x35F72C by thread #4 ==769== Locks held: none ==769== at 0x129E05: memset (string3.h:84) ==769== by 0x129E05: mds_service_retrieve (mdstipc_conf.c:1619) ==769== by 0x1120C4: tet_vdest_rcvr_thread (mdstipc_api.c:5584) ==769== by 0x4C30FA6: ??? (in /hostfs/rootfs/usr/lib64/valgrind/vgpreload_helgrind-amd64-linux.so) ==769== by 0x50CC183: start_thread (pthread_create.c:312) ==769== by 0x53DFFFC: clone (clone.S:111) ==769== ==769== This conflicts with a previous write of size 4 by thread #1 ==769== Locks held: none ==769== at 0x12A0F3: memset (string3.h:84) ==769== by 0x12A0F3: mds_service_uninstall (mdstipc_conf.c:435) ==769== by 0x116547: tet_cleanup_setup (mdstipc_api.c:2726) ==769== by 0x11BCBF: tet_send_response_ack_tp_5 (mdstipc_api.c:6726) ==769== by 0x12B928: run_test_case (utest.c:178) ==769== by 0x12BD6D: test_run (utest.c:226) ==769== by 0x10DBA8: main (mdstest.c:92) ==769== Address 0x35f72c is 12 bytes inside data symbol "svc_to_mds_info" ==769== ==769== this is likely the cause why some mds tests sometimes fails "randomly". The mds tests has to be thread safe and helgrind can be used to identify these thread synchronization issues. --- 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] #2740 smfd: immCCB action failed to create rollback element due to ERR_EXIST
- **summary**: smfd: immCcb action failed to create rollback element due to ERR_EXIST --> smfd: immCCB action failed to create rollback element due to ERR_EXIST - Description has changed: Diff: --- old +++ new @@ -1,4 +1,4 @@ -While testing the fix of ticket [#2584](https://sourceforge.net/p/opensaf/tickets/2584/), a fault has been found, in which the retried resource-aborted immCcb action (due to IMM sync request) in failed to create the smfRollbackElement object with return code of SA_AIS_ERR_EXIST (because the object had already been created before the CCB got aborted). That error made the campaign fail. +While testing the fix of ticket [#2584](https://sourceforge.net/p/opensaf/tickets/2584/), a fault has been found, in which the retried resource-aborted immCCB action (due to IMM sync request) in failed to create the smfRollbackElement object with return code of SA_AIS_ERR_EXIST (because the object had already been created before the CCB got aborted). That error made the campaign fail. * system log: --- ** [tickets:#2740] smfd: immCCB action failed to create rollback element due to ERR_EXIST** **Status:** unassigned **Milestone:** 5.18.01 **Created:** Tue Dec 19, 2017 09:47 AM UTC by Nguyen TK Luu **Last Updated:** Tue Dec 19, 2017 09:48 AM UTC **Owner:** nobody While testing the fix of ticket [#2584](https://sourceforge.net/p/opensaf/tickets/2584/), a fault has been found, in which the retried resource-aborted immCCB action (due to IMM sync request) in failed to create the smfRollbackElement object with return code of SA_AIS_ERR_EXIST (because the object had already been created before the CCB got aborted). That error made the campaign fail. * system log: 2017-12-19 16:26:37.086 SC-1 osafsmfd[310]: NO CAMP: Start campaign complete actions (1) 2017-12-19 16:26:37.104 SC-1 osafimmnd[207]: NO Create of PERSISTENT runtime object 'smfRollbackElement=CampComplete,safSmfCampaign=campaign_d2584,safApp=safSmfService' (safSmfCampaign). 2017-12-19 16:26:37.116 SC-1 osafimmnd[207]: NO Create of PERSISTENT runtime object 'smfRollbackElement=ccb_0001,smfRollbackElement=CampComplete,safSmfCampaign=campaign_d2584,safApp=safSmfService' (safSmfCampaign). 2017-12-19 16:26:37.250 SC-1 osafimmnd[207]: NO PBE-OI established on this SC. Dumping incrementally to file imm.db 2017-12-19 16:26:37.348 SC-1 osafimmd[196]: NO MDS event from svc_id 25 (change:4, dest:566312912814258) 2017-12-19 16:26:37.353 SC-1 osafimmnd[207]: NO Global discard node received for nodeId:2030f pid:178 2017-12-19 16:26:37.434 SC-1 osafimmd[196]: NO MDS event from svc_id 25 (change:3, dest:566312912814394) 2017-12-19 16:26:37.436 SC-1 osafimmd[196]: NO Extended intro from node 2030f 2017-12-19 16:26:37.642 SC-1 osafimmd[196]: NO Node 2030f request sync sync-pid:314 epoch:0 2017-12-19 16:26:38.255 SC-1 osafimmnd[207]: NO Announce sync, epoch:6 2017-12-19 16:26:38.260 SC-1 osafimmnd[207]: NO SERVER STATE: IMM_SERVER_READY --> IMM_SERVER_SYNC_SERVER 2017-12-19 16:26:38.267 SC-1 osafimmd[196]: NO Successfully announced sync. New ruling epoch:6 2017-12-19 16:26:38.268 SC-1 osafimmnd[207]: NO NODE STATE-> IMM_NODE_R_AVAILABLE 2017-12-19 16:26:40.141 SC-1 osafimmnd[207]: NO Precheck of fevs message of type <33> failed with ERROR:18 2017-12-19 16:26:43.151 SC-1 osafimmnd[207]: message repeated 3 times: [ NO Precheck of fevs message of type <33> failed with ERROR:18] 2017-12-19 16:26:43.308 SC-1 osafimmnd[207]: WA Aborting ccbId 21 to start sync 2017-12-19 16:26:43.317 SC-1 osafimmnd[207]: NO Ccb 21 ABORTED (SMFSERVICE) 2017-12-19 16:26:43.458 SC-1 osafimmloadd: logtrace: trace enabled to file 'osafimmnd', mask=0x0 2017-12-19 16:26:43.459 SC-1 osafimmloadd: NO Sync starting 2017-12-19 16:26:43.894 SC-1 osafimmloadd: IN Synced 362 objects in total 2017-12-19 16:26:43.896 SC-1 osafimmnd[207]: NO NODE STATE-> IMM_NODE_FULLY_AVAILABLE 19132 2017-12-19 16:26:43.901 SC-1 osafimmd[196]: NO ACT: New Epoch for IMMND process at node 2030f old epoch: 0 new epoch:6 2017-12-19 16:26:43.902 SC-1 osafimmd[196]: NO ACT: New Epoch for IMMND process at node 2040f old epoch: 5 new epoch:6 2017-12-19 16:26:43.903 SC-1 osafimmd[196]: NO ACT: New Epoch for IMMND process at node 2020f old epoch: 5 new epoch:6 2017-12-19 16:26:43.904 SC-1 osafimmd[196]: NO ACT: New Epoch for IMMND process at node 2050f old epoch: 5 new epoch:6 2017-12-19 16:26:43.906 SC-1 osafimmloadd: NO Sync ending normally 2017-12-19 16:26:43.906 SC-1 osafimmnd[207]: NO Epoch set to 6 in ImmModel 2017-12-19 16:26:43.907 SC-1 osafimmpbed: NO Update epoch 6 committing with ccbId:10021/4294967329 2017-12-19 16:26:43.908 SC-1 osafimmd[196]: NO ACT: New Epoch for IMMND process at node 2010f old epoch: 5 new epoch:6 2017-12-19 16:26:43.986 SC-1 osafimmnd[207]: NO SERVER STATE: IMM_SERVER_SYNC_SERVER --> IMM_SERVER_READY 2017-12-19 16:26:44.671 SC-1 osafsmfd[310]: ER SmfImmCcbAction::execute failed to create rollback element
[tickets] [opensaf:tickets] #2426 mds: MDS send failure
- **status**: review --> fixed - **Comment**: develop: commit c4a934ba77290efcdcc76700cd024fb3871a3ebf Author: Zoran MilinkovicDate: Wed Dec 20 15:10:04 2017 +0100 imm: change log level for failing to send accept message [#2426] Importance log level is changed from error to warning level due to no reaction from IMMD. --- ** [tickets:#2426] mds: MDS send failure** **Status:** fixed **Milestone:** 5.18.01 **Created:** Thu Apr 13, 2017 11:22 AM UTC by Hung Nguyen **Last Updated:** Wed Dec 20, 2017 02:15 PM UTC **Owner:** Zoran Milinkovic **Attachments:** - [logs.tgz](https://sourceforge.net/p/opensaf/tickets/2426/attachment/logs.tgz) (1.8 MB; application/x-compressed) IMMD@SC-2 recived a message from IMMND@SC-1 but failed to send a message back to IMMND@SC-1. Both IMMD and IMMND use MDS_SENDTYPE_SND. RDE also got that failure. ~~~ 18:33:18 SC-1 osafrded[183]: WA Failed to send RDE_MSG_PEER_INFO_RESP(4) to 2020f9d120640 18:33:18 SC-1 osafrded[183]: message repeated 2 times: [ WA Failed to send RDE_MSG_PEER_INFO_RESP(4) to 2020f9d120640] 18:33:18 SC-2 osafrded[183]: WA Failed to send RDE_MSG_PEER_INFO_RESP(4) to 2010fc4b8a390 18:33:18 SC-2 osafimmd[202]: WA IMMD - MDS Send Failed 18:33:18 SC-2 osafimmd[202]: ER Failed to send accept message to IMMND 2010f ~~~ Attached is the logs. --- 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] #2426 mds: MDS send failure
the immd error message will be changed to a warning message. Sending a reply to immnd may fail for several reasons, e.g. the node goes down after sending "introduce-me" messages or the topology message arrives after the send. The immnd will re-send "introduce-me" messages until accepted, so this immd message send failure is not considered as a fatal error. --- ** [tickets:#2426] mds: MDS send failure** **Status:** review **Milestone:** 5.18.01 **Created:** Thu Apr 13, 2017 11:22 AM UTC by Hung Nguyen **Last Updated:** Wed Dec 20, 2017 02:02 PM UTC **Owner:** Zoran Milinkovic **Attachments:** - [logs.tgz](https://sourceforge.net/p/opensaf/tickets/2426/attachment/logs.tgz) (1.8 MB; application/x-compressed) IMMD@SC-2 recived a message from IMMND@SC-1 but failed to send a message back to IMMND@SC-1. Both IMMD and IMMND use MDS_SENDTYPE_SND. RDE also got that failure. ~~~ 18:33:18 SC-1 osafrded[183]: WA Failed to send RDE_MSG_PEER_INFO_RESP(4) to 2020f9d120640 18:33:18 SC-1 osafrded[183]: message repeated 2 times: [ WA Failed to send RDE_MSG_PEER_INFO_RESP(4) to 2020f9d120640] 18:33:18 SC-2 osafrded[183]: WA Failed to send RDE_MSG_PEER_INFO_RESP(4) to 2010fc4b8a390 18:33:18 SC-2 osafimmd[202]: WA IMMD - MDS Send Failed 18:33:18 SC-2 osafimmd[202]: ER Failed to send accept message to IMMND 2010f ~~~ Attached is the logs. --- 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] #2426 mds: MDS send failure
- **status**: accepted --> review - **assigned_to**: Hans Nordebäck --> Zoran Milinkovic - **Comment**: https://sourceforge.net/p/opensaf/mailman/message/36163959/ --- ** [tickets:#2426] mds: MDS send failure** **Status:** review **Milestone:** 5.18.01 **Created:** Thu Apr 13, 2017 11:22 AM UTC by Hung Nguyen **Last Updated:** Fri Nov 03, 2017 09:50 PM UTC **Owner:** Zoran Milinkovic **Attachments:** - [logs.tgz](https://sourceforge.net/p/opensaf/tickets/2426/attachment/logs.tgz) (1.8 MB; application/x-compressed) IMMD@SC-2 recived a message from IMMND@SC-1 but failed to send a message back to IMMND@SC-1. Both IMMD and IMMND use MDS_SENDTYPE_SND. RDE also got that failure. ~~~ 18:33:18 SC-1 osafrded[183]: WA Failed to send RDE_MSG_PEER_INFO_RESP(4) to 2020f9d120640 18:33:18 SC-1 osafrded[183]: message repeated 2 times: [ WA Failed to send RDE_MSG_PEER_INFO_RESP(4) to 2020f9d120640] 18:33:18 SC-2 osafrded[183]: WA Failed to send RDE_MSG_PEER_INFO_RESP(4) to 2010fc4b8a390 18:33:18 SC-2 osafimmd[202]: WA IMMD - MDS Send Failed 18:33:18 SC-2 osafimmd[202]: ER Failed to send accept message to IMMND 2010f ~~~ Attached is the logs. --- 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] #2745 imm: lower the log message level for failing to send the accept message
- **status**: unassigned --> duplicate - **Component**: unknown --> imm - **Comment**: Duplicate of #2426 --- ** [tickets:#2745] imm: lower the log message level for failing to send the accept message** **Status:** duplicate **Milestone:** 5.18.01 **Created:** Wed Dec 20, 2017 01:40 PM UTC by Zoran Milinkovic **Last Updated:** Wed Dec 20, 2017 01:40 PM UTC **Owner:** nobody When IMMD fails to send the accept message, it's logged with error importance level. The importance level will be changed to warning level due to no reaction from IMMD on error. ~~~ osafimmd[202]: ER Failed to send accept message to IMMND 2010f ~~~ --- 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] #2745 imm: lower the log message level for failing to send the accept message
--- ** [tickets:#2745] imm: lower the log message level for failing to send the accept message** **Status:** unassigned **Milestone:** 5.18.01 **Created:** Wed Dec 20, 2017 01:40 PM UTC by Zoran Milinkovic **Last Updated:** Wed Dec 20, 2017 01:40 PM UTC **Owner:** nobody When IMMD fails to send the accept message, it's logged with error importance level. The importance level will be changed to warning level due to no reaction from IMMD on error. ~~~ osafimmd[202]: ER Failed to send accept message to IMMND 2010f ~~~ --- 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] #2744 build: lib directory may not exist when all-local is built
--- ** [tickets:#2744] build: lib directory may not exist when all-local is built** **Status:** accepted **Milestone:** 5.18.01 **Created:** Wed Dec 20, 2017 01:09 PM UTC by Anders Widell **Last Updated:** Wed Dec 20, 2017 01:09 PM UTC **Owner:** Anders Widell When running a parallel build, $(top_builddir)/lib may not yet exist when the all-local target is built. --- 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] #2743 ais: change default retry in decorator
- **status**: accepted --> review --- ** [tickets:#2743] ais: change default retry in decorator** **Status:** review **Milestone:** 5.18.01 **Created:** Wed Dec 20, 2017 11:58 AM UTC by Vu Minh Nguyen **Last Updated:** Wed Dec 20, 2017 11:58 AM UTC **Owner:** Vu Minh Nguyen Change interval time to 100 miliseconds, and timeout to one minute for the default retry control. --- 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] #2743 ais: change default retry in decorator
--- ** [tickets:#2743] ais: change default retry in decorator** **Status:** accepted **Milestone:** 5.18.01 **Created:** Wed Dec 20, 2017 11:58 AM UTC by Vu Minh Nguyen **Last Updated:** Wed Dec 20, 2017 11:58 AM UTC **Owner:** Vu Minh Nguyen Change interval time to 100 miliseconds, and timeout to one minute for the default retry control. --- 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] #2742 osaf: Use Node ID instead of slot and subslot to identify a node
--- ** [tickets:#2742] osaf: Use Node ID instead of slot and subslot to identify a node** **Status:** accepted **Milestone:** 5.18.01 **Created:** Wed Dec 20, 2017 11:51 AM UTC by Anders Widell **Last Updated:** Wed Dec 20, 2017 11:51 AM UTC **Owner:** Anders Widell Related to ticket [#1755]: remove usage of chassis, slot and subslot to identify a node. Instead, only Node ID will be used to identify a node within the OpenSAF code. --- 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] #2707 pyosaf: Refactor NTF samples to make use of new pyosaf utils
- Description has changed: Diff: --- old +++ new @@ -1,2 +1,2 @@ - Refactor the ntfsend and ntfsubscribe python samples to make use of the new pyosaf utils implementation of enhancement ticket [#2602](https://sourceforge.net/p/opensaf/tickets/2602/). -- Add a new ntfread sample to illustrate usage of the new NtfReader utils. +- Add a new ntfread sample to demonstrate usage of the new NtfReader utils. - **status**: accepted --> review --- ** [tickets:#2707] pyosaf: Refactor NTF samples to make use of new pyosaf utils ** **Status:** review **Milestone:** 5.18.01 **Created:** Mon Nov 27, 2017 07:55 AM UTC by Nguyen TK Luu **Last Updated:** Mon Nov 27, 2017 08:02 AM UTC **Owner:** Nguyen TK Luu - Refactor the ntfsend and ntfsubscribe python samples to make use of the new pyosaf utils implementation of enhancement ticket [#2602](https://sourceforge.net/p/opensaf/tickets/2602/). - Add a new ntfread sample to demonstrate usage of the new NtfReader utils. --- 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] #2685 pyosaf: Fix amf_demo python sample
- **status**: review --> fixed - **assigned_to**: Danh Vo --> nobody - **Comment**: commit 5a520b91f37ef51ddf6fbdd97928a002e2967e0c (HEAD, origin/develop, develop) Author: Danh VoDate: Mon Dec 4 11:21:22 2017 +0700 pyosaf: Fix amf_demo python sample [#2685] - Fix amf_demo to make it work. - Modify README for the latest amf_demo. commit cb0f2869a1b34b4cec5873d5032c708d1b793e19 (HEAD, origin/release, release) Author: Danh Vo Date: Mon Dec 4 11:21:22 2017 +0700 pyosaf: Fix amf_demo python sample [#2685] - Fix amf_demo to make it work. - Modify README for the latest amf_demo. --- ** [tickets:#2685] pyosaf: Fix amf_demo python sample** **Status:** fixed **Milestone:** 5.18.01 **Created:** Fri Nov 17, 2017 02:30 AM UTC by Nguyen TK Luu **Last Updated:** Mon Dec 04, 2017 06:25 AM UTC **Owner:** nobody Fix amf_demo python sample so that it works. It fails because the script returns exit code 1. The root cause maybe come from amf_demo_script could not find the pid file in /tmp directory. 2017-11-17 10:16:18.015 SC-1 osafamfnd[377]: NO 'safSu=SU1,safSg=AmfDemo,safApp=AmfDemo1' Presence State UNINSTANTIATED => INSTANTIATING 2017-11-17 10:16:18.238 SC-1 amf_demo_script: Starting /opt/amf_demo/amf_demo failed 2017-11-17 10:16:18.240 SC-1 osafamfnd[377]: NO Instantiation of 'safComp=AmfDemo,safSu=SU1,safSg=AmfDemo,safApp=AmfDemo1' failed 2017-11-17 10:16:18.241 SC-1 osafamfnd[377]: NO Reason:'Exec of script success, but script exits with non-zero status' 2017-11-17 10:16:18.241 SC-1 osafamfnd[377]: NO Exit code: 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] #2679 pyosaf: Refactor clm-tool sample to make use of new pyosaf utils
- **status**: review --> fixed - **assigned_to**: Danh Vo --> nobody - **Comment**: commit 390b54659b204d4a0d28b2ef24a2fcce28db94fc (HEAD, origin/develop, develop) Author: Danh VoDate: Tue Nov 14 15:36:48 2017 +0700 pyosaf: Refactor clm-tool sample to make use of new pyosaf utils [#2679] - Refactor clm-tool. - Add new function in clm util for sending node get. --- ** [tickets:#2679] pyosaf: Refactor clm-tool sample to make use of new pyosaf utils** **Status:** fixed **Milestone:** 5.18.01 **Created:** Tue Nov 14, 2017 07:53 AM UTC by Nguyen TK Luu **Last Updated:** Tue Nov 14, 2017 09:51 AM UTC **Owner:** nobody Refactor the clm-tool python sample to make use of the new pyosaf utils implementation of enhancement ticket [#2602](https://sourceforge.net/p/opensaf/tickets/2602/). --- 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