date:20170720

[tickets] [opensaf:tickets] #2531 clm: saClmClusterTrack tests intermittently failing

2017-07-20 Thread Gary Lee via Opensaf-tickets

- **status**: accepted --> review



---

** [tickets:#2531] clm: saClmClusterTrack tests intermittently failing**

**Status:** review
**Milestone:** 5.17.08
**Created:** Thu Jul 20, 2017 10:12 AM UTC by Gary Lee
**Last Updated:** Thu Jul 20, 2017 10:12 AM UTC
**Owner:** Gary Lee


saClmClusterTrack tests are intermittently failing since #2520 was pushed. It 
appears some of the extra test pre and post-conditions are adding extra load to 
the cluster and now callbacks sometimes arrive after poll timeout.

~~~
#0 0x7f0baf31f428 in __GI_raise (sig=sig@entry=6) at 
../sysdeps/unix/sysv/linux/raise.c:54
resultvar = 0
pid = 279
selftid = 279
#1 0x7f0baf32102a in __GI_abort () at abort.c:89
save_stage = 2
act = {__sigaction_handler = {sa_handler = 0x4, sa_sigaction = 0x4}, sa_mask = 
{__val = {0, 0, 140722867603632, 47244640256, 139688173297664, 93937335533192, 
721, 93937335537008, 0, 0, 139688160975244, 139688162072152, 139688162085808, 
0, 139688162072152, 93937335533192}}, sa_flags = -1343037440, sa_restorer = 
0x556f7d83fe88}
sigs = {__val = {32, 0 }}
#2 0x7f0baf317bd7 in __assert_fail_base (fmt=, 
assertion=assertion@entry=0x556f7d83fe88 "ret == 1", 
file=file@entry=0x556f7d840378 "src/clm/apitest/tet_saClmClusterTrack.c", 
line=line@entry=721, function=function@entry=0x556f7d840d70 
<__PRETTY_FUNCTION__.7228> "saClmClusterTrack_25") at assert.c:92
str = 0x556f7f7f4220 ""
total = 4096
#3 0x7f0baf317c82 in __GI___assert_fail 
(assertion=assertion@entry=0x556f7d83fe88 "ret == 1", 
file=file@entry=0x556f7d840378 "src/clm/apitest/tet_saClmClusterTrack.c", 
line=line@entry=721, function=function@entry=0x556f7d840d70 
<__PRETTY_FUNCTION__.7228> "saClmClusterTrack_25") at assert.c:101
No locals.
#4 0x556f7d83b007 in saClmClusterTrack_25 () at 
src/clm/apitest/tet_saClmClusterTrack.c:721
fds = {{fd = 10, events = 1, revents = 0}}
thread4 = 139688031545088
__PRETTY_FUNCTION__ = "saClmClusterTrack_25"
#5 0x556f7d83f3e5 in run_test_case (suite=, tcase=) at src/osaf/apitest/utest.c:163
No locals.
#6 0x556f7d83f894 in test_run (suite=, tcase=) at src/osaf/apitest/utest.c:187
i = 7
j = 25
#7 0x7f0baf30a830 in __libc_start_main (main=0x556f7d837a10 , argc=1, 
argv=0x7ffc98890b48, init=, fini=, 
rtld_fini=, stack_end=0x7ffc98890b38) at ../csu/libc-start.c:291
result = 
unwind_buf = {cancel_jmp_buf = {{jmp_buf = {0, 4769676410766378679, 
93937335502288, 140722867604288, 0, 0, 1663659470616151735, 
1655334589884417719}, mask_was_saved = 0}}, priv = {pad = {0x0, 0x0, 
0x7ffc98890b58, 0x7f0baff33168}, data = {prev = 0x0, cleanup = 0x0, canceltype 
= -1735849128}}}
not_first_call = 
#8 0x556f7d8385f9 in _start ()
No symbol table info available.
~~~


---

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] #2522 dtm: if TCP_USER_TIMEOUT closes socket, no attempt is make to reconnect

2017-07-20 Thread A V Mahesh (AVM) via Opensaf-tickets

I don't think   Alex is taking about initial discovery issue/ processes ( 
topology node discovery) ,
but any how we can configure very big value of `DTM_INI_DIS_TIMEOUT_SECS` in 
dtm.conf to verify


---

** [tickets:#2522] dtm: if TCP_USER_TIMEOUT closes socket, no attempt is make 
to reconnect**

**Status:** unassigned
**Milestone:** 5.17.10
**Created:** Thu Jul 06, 2017 01:28 PM UTC by Alex Jones
**Last Updated:** Thu Jul 20, 2017 01:54 PM UTC
**Owner:** nobody


If TCP is used for transport, and TCP_USER_TIMEOUT is used also, if a node 
leaves the cluster due to some quick network outage, the nodes do not come back 
into the cluster automatically.

If TCP_USER_TIMEOUT is set to 1500 ms, and the network outage on the link is 
for 2000 ms, the node never comes back into the cluster.


---

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] #2522 dtm: if TCP_USER_TIMEOUT closes socket, no attempt is make to reconnect

2017-07-20 Thread Anders Widell via Opensaf-tickets

I believe DTM sends broadcast (or multicast) messages on the network for a 
while after it has started, to discover other nodes on the network. But it 
stops doing this after a while and that is the reason why it fails to reconnect 
after a network disturbance.

A solution could be:
* The node with the lowest node_id will never stop broadcasting the discovery 
messages
* A node which is connected with another node with a lower node_id will never 
broadcast discovery messages
* The node with the lowest node_id will inform all the other connected nodes 
about the topology of the cluster - in particular, if a new node has appeared.


---

** [tickets:#2522] dtm: if TCP_USER_TIMEOUT closes socket, no attempt is make 
to reconnect**

**Status:** unassigned
**Milestone:** 5.17.10
**Created:** Thu Jul 06, 2017 01:28 PM UTC by Alex Jones
**Last Updated:** Thu Jul 06, 2017 01:28 PM UTC
**Owner:** nobody


If TCP is used for transport, and TCP_USER_TIMEOUT is used also, if a node 
leaves the cluster due to some quick network outage, the nodes do not come back 
into the cluster automatically.

If TCP_USER_TIMEOUT is set to 1500 ms, and the network outage on the link is 
for 2000 ms, the node never comes back into the cluster.


---

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] #2528 clm: CLM does not handle ERR_BAD_HANDLE from saImmOmSearchInitialize

2017-07-20 Thread Hung Nguyen via Opensaf-tickets

- **status**: review --> fixed
- **Comment**:

develop (5.17.08) [code:74c67f]
~~~
commit 74c67fe68fc08c75e834fe2cc2153c604c9b014d
Author: Zoran Milinkovic 
Date:   Thu Jul 20 17:14:51 2017 +0700

clm: handle ERR_BAD_HANDLE for saImmOmSearchInitialize [#2528]

CLM handles ERR_BAD_HANDLE for saImmOmSearchInitialize in 
clms_cluster_config_get.
As part of this patch, handling of IMM version is improved in the same 
function.
~~~


release [code:4afc6d]
~~~
commit 4afc6dc5c1ee9c3b27e03155aa952c6466217468
Author: Zoran Milinkovic 
Date:   Thu Jul 20 17:14:51 2017 +0700

clm: handle ERR_BAD_HANDLE for saImmOmSearchInitialize [#2528]

CLM handles ERR_BAD_HANDLE for saImmOmSearchInitialize in 
clms_cluster_config_get.
As part of this patch, handling of IMM version is improved in the same 
function.

~~~




---

** [tickets:#2528] clm: CLM does not handle ERR_BAD_HANDLE from 
saImmOmSearchInitialize**

**Status:** fixed
**Milestone:** 5.17.08
**Created:** Fri Jul 14, 2017 12:18 PM UTC by Zoran Milinkovic
**Last Updated:** Fri Jul 14, 2017 01:18 PM UTC
**Owner:** Zoran Milinkovic


CLM fails with ERR_BAD_HANDLE in saImmOmSearchInitialize call.
CLM should reinitialize OM handle and repeat search at least once.

Jul 11 21:00:40 SC-1 osafrded[5886]: NO Got peer info response from node 
0x2020f with role ACTIVE
Jul 11 21:00:40 SC-1 osafclmd[5976]: WA OpenSAF imm lib: Message loss detected 
for dest 564115135000812 service id:25
Jul 11 21:00:40 SC-1 osafimmnd[5931]: WA IMMND - Client Node Get Failed for 
client handle: 1357209796879
Jul 11 21:00:40 SC-1 osafclmd[5976]: WA OpenSAF imm lib: Message loss detected 
for dest 564115135000812 service id:25
Jul 11 21:00:40 SC-1 osafclmd[5976]: WA marking handle as exposed
Jul 11 21:00:40 SC-1 osafclmd[5976]: ER No Object of SaClmNode Class was found
Jul 11 21:00:40 SC-1 osafclmd[5976]: ER clms_node_create_config failed rc:9
Jul 11 21:00:40 SC-1 osafclmd[5976]: ER clms_imm_activate FAILED
Jul 11 21:00:40 SC-1 osafclmd[5976]: ER initialize_for_assignment FAILED 9


---

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] #2531 clm: saClmClusterTrack tests intermittently failing

2017-07-20 Thread Gary Lee via Opensaf-tickets

- Description has changed:

Diff:



--- old
+++ new
@@ -1,4 +1,4 @@
-saClmClusterTrack tests are intermittently failing since #2520 was push. It 
appears some of the extra test pre and post-conditions are adding extra load to 
the cluster and now callbacks sometimes arrive after poll timeout.
+saClmClusterTrack tests are intermittently failing since #2520 was pushed. It 
appears some of the extra test pre and post-conditions are adding extra load to 
the cluster and now callbacks sometimes arrive after poll timeout.
 
 ~~~
 #0 0x7f0baf31f428 in __GI_raise (sig=sig@entry=6) at 
../sysdeps/unix/sysv/linux/raise.c:54






---

** [tickets:#2531] clm: saClmClusterTrack tests intermittently failing**

**Status:** accepted
**Milestone:** 5.17.08
**Created:** Thu Jul 20, 2017 10:12 AM UTC by Gary Lee
**Last Updated:** Thu Jul 20, 2017 10:12 AM UTC
**Owner:** Gary Lee


saClmClusterTrack tests are intermittently failing since #2520 was pushed. It 
appears some of the extra test pre and post-conditions are adding extra load to 
the cluster and now callbacks sometimes arrive after poll timeout.

~~~
#0 0x7f0baf31f428 in __GI_raise (sig=sig@entry=6) at 
../sysdeps/unix/sysv/linux/raise.c:54
resultvar = 0
pid = 279
selftid = 279
#1 0x7f0baf32102a in __GI_abort () at abort.c:89
save_stage = 2
act = {__sigaction_handler = {sa_handler = 0x4, sa_sigaction = 0x4}, sa_mask = 
{__val = {0, 0, 140722867603632, 47244640256, 139688173297664, 93937335533192, 
721, 93937335537008, 0, 0, 139688160975244, 139688162072152, 139688162085808, 
0, 139688162072152, 93937335533192}}, sa_flags = -1343037440, sa_restorer = 
0x556f7d83fe88}
sigs = {__val = {32, 0 }}
#2 0x7f0baf317bd7 in __assert_fail_base (fmt=, 
assertion=assertion@entry=0x556f7d83fe88 "ret == 1", 
file=file@entry=0x556f7d840378 "src/clm/apitest/tet_saClmClusterTrack.c", 
line=line@entry=721, function=function@entry=0x556f7d840d70 
<__PRETTY_FUNCTION__.7228> "saClmClusterTrack_25") at assert.c:92
str = 0x556f7f7f4220 ""
total = 4096
#3 0x7f0baf317c82 in __GI___assert_fail 
(assertion=assertion@entry=0x556f7d83fe88 "ret == 1", 
file=file@entry=0x556f7d840378 "src/clm/apitest/tet_saClmClusterTrack.c", 
line=line@entry=721, function=function@entry=0x556f7d840d70 
<__PRETTY_FUNCTION__.7228> "saClmClusterTrack_25") at assert.c:101
No locals.
#4 0x556f7d83b007 in saClmClusterTrack_25 () at 
src/clm/apitest/tet_saClmClusterTrack.c:721
fds = {{fd = 10, events = 1, revents = 0}}
thread4 = 139688031545088
__PRETTY_FUNCTION__ = "saClmClusterTrack_25"
#5 0x556f7d83f3e5 in run_test_case (suite=, tcase=) at src/osaf/apitest/utest.c:163
No locals.
#6 0x556f7d83f894 in test_run (suite=, tcase=) at src/osaf/apitest/utest.c:187
i = 7
j = 25
#7 0x7f0baf30a830 in __libc_start_main (main=0x556f7d837a10 , argc=1, 
argv=0x7ffc98890b48, init=, fini=, 
rtld_fini=, stack_end=0x7ffc98890b38) at ../csu/libc-start.c:291
result = 
unwind_buf = {cancel_jmp_buf = {{jmp_buf = {0, 4769676410766378679, 
93937335502288, 140722867604288, 0, 0, 1663659470616151735, 
1655334589884417719}, mask_was_saved = 0}}, priv = {pad = {0x0, 0x0, 
0x7ffc98890b58, 0x7f0baff33168}, data = {prev = 0x0, cleanup = 0x0, canceltype 
= -1735849128}}}
not_first_call = 
#8 0x556f7d8385f9 in _start ()
No symbol table info available.
~~~


---

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] #2531 clm: saClmClusterTrack tests intermittently failing

2017-07-20 Thread Gary Lee via Opensaf-tickets




---

** [tickets:#2531] clm: saClmClusterTrack tests intermittently failing**

**Status:** accepted
**Milestone:** 5.17.08
**Created:** Thu Jul 20, 2017 10:12 AM UTC by Gary Lee
**Last Updated:** Thu Jul 20, 2017 10:12 AM UTC
**Owner:** Gary Lee


saClmClusterTrack tests are intermittently failing since #2520 was push. It 
appears some of the extra test pre and post-conditions are adding extra load to 
the cluster and now callbacks sometimes arrive after poll timeout.

~~~
#0 0x7f0baf31f428 in __GI_raise (sig=sig@entry=6) at 
../sysdeps/unix/sysv/linux/raise.c:54
resultvar = 0
pid = 279
selftid = 279
#1 0x7f0baf32102a in __GI_abort () at abort.c:89
save_stage = 2
act = {__sigaction_handler = {sa_handler = 0x4, sa_sigaction = 0x4}, sa_mask = 
{__val = {0, 0, 140722867603632, 47244640256, 139688173297664, 93937335533192, 
721, 93937335537008, 0, 0, 139688160975244, 139688162072152, 139688162085808, 
0, 139688162072152, 93937335533192}}, sa_flags = -1343037440, sa_restorer = 
0x556f7d83fe88}
sigs = {__val = {32, 0 }}
#2 0x7f0baf317bd7 in __assert_fail_base (fmt=, 
assertion=assertion@entry=0x556f7d83fe88 "ret == 1", 
file=file@entry=0x556f7d840378 "src/clm/apitest/tet_saClmClusterTrack.c", 
line=line@entry=721, function=function@entry=0x556f7d840d70 
<__PRETTY_FUNCTION__.7228> "saClmClusterTrack_25") at assert.c:92
str = 0x556f7f7f4220 ""
total = 4096
#3 0x7f0baf317c82 in __GI___assert_fail 
(assertion=assertion@entry=0x556f7d83fe88 "ret == 1", 
file=file@entry=0x556f7d840378 "src/clm/apitest/tet_saClmClusterTrack.c", 
line=line@entry=721, function=function@entry=0x556f7d840d70 
<__PRETTY_FUNCTION__.7228> "saClmClusterTrack_25") at assert.c:101
No locals.
#4 0x556f7d83b007 in saClmClusterTrack_25 () at 
src/clm/apitest/tet_saClmClusterTrack.c:721
fds = {{fd = 10, events = 1, revents = 0}}
thread4 = 139688031545088
__PRETTY_FUNCTION__ = "saClmClusterTrack_25"
#5 0x556f7d83f3e5 in run_test_case (suite=, tcase=) at src/osaf/apitest/utest.c:163
No locals.
#6 0x556f7d83f894 in test_run (suite=, tcase=) at src/osaf/apitest/utest.c:187
i = 7
j = 25
#7 0x7f0baf30a830 in __libc_start_main (main=0x556f7d837a10 , argc=1, 
argv=0x7ffc98890b48, init=, fini=, 
rtld_fini=, stack_end=0x7ffc98890b38) at ../csu/libc-start.c:291
result = 
unwind_buf = {cancel_jmp_buf = {{jmp_buf = {0, 4769676410766378679, 
93937335502288, 140722867604288, 0, 0, 1663659470616151735, 
1655334589884417719}, mask_was_saved = 0}}, priv = {pad = {0x0, 0x0, 
0x7ffc98890b58, 0x7f0baff33168}, data = {prev = 0x0, cleanup = 0x0, canceltype 
= -1735849128}}}
not_first_call = 
#8 0x556f7d8385f9 in _start ()
No symbol table info available.
~~~


---

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] #248 "amf: Incorrect return code from saAmfComponentErrorReport_4 () and saAmfComponentErrorClear_4()".

2017-07-20 Thread Nagendra Kumar via Opensaf-tickets

The basic reason for returning SA_AIS_ERR_VERSION(3) from non-registered after 
finalise is that in Finalize(), pend_dis is zero  and ncs_ava_shutdown() is 
called, which in turn call ncs_ava_shutdown()->ava_destroy(). ava_destroy() 
deletes cb and makes gl_ava_hdl zero.
So, when ComponentErrorReport_4() is called ava_B4_ver_used(0) returns zero 
because neither cb nor gl_ava_hdl exists and then the following code returns 
SA_AIS_ERR_VERSION:
  /* Version is previously set in in initialize function */
  if (!ava_B4_ver_used(0)) {
TRACE_2(
"Invalid AMF version, set correct AMF version using saAmfInitialize_4. "
"Required version is: ReleaseCode = 'B', majorVersion = 0x04");
rc = SA_AIS_ERR_VERSION;
goto done;
  }

WHen called from registered process in Dispatch context, pend_dis is not zero 
and ncs_ava_shutdown() is not called and hence ava_B4_ver_used(0) returns true 
and code proceeds and returns BAD_HANDLE from later point of call.


---

** [tickets:#248] "amf: Incorrect return code from saAmfComponentErrorReport_4 
() and saAmfComponentErrorClear_4()". **

**Status:** assigned
**Milestone:** 5.2.FC
**Created:** Thu May 16, 2013 06:41 AM UTC by Praveen
**Last Updated:** Wed Jul 19, 2017 06:41 AM UTC
**Owner:** Nagendra Kumar


Migrated from http://devel.opensaf.org/ticket/2817.

Changeset:3728
 When saAmfComponentErrorReport_4() and saAmfComponentErrorClear_4() are called 
after finalizing the amfHandle(calling saAmfFinalize()), both of them returns 
SA_AIS_ERR_VERSION instead of SA_AIS_ERR_BAD_HANDLE.



---

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] #333 amf: saAmfHealthcheckStart returns SA_AIS_ERR_NOT_EXIST when SA_AMF_COMPONENT_NAME is not exported.

2017-07-20 Thread Nagendra Kumar via Opensaf-tickets

- **status**: unassigned --> assigned
- **assigned_to**: Nagendra Kumar
- **Part**: - --> nd
- **Blocker**:  --> False
- **Milestone**: future --> 5.17.10



---

** [tickets:#333] amf: saAmfHealthcheckStart returns SA_AIS_ERR_NOT_EXIST when 
SA_AMF_COMPONENT_NAME is not exported.**

**Status:** assigned
**Milestone:** 5.17.10
**Created:** Mon May 27, 2013 04:48 AM UTC by Praveen
**Last Updated:** Mon Apr 03, 2017 06:47 PM UTC
**Owner:** Nagendra Kumar


Migrated from http://devel.opensaf.org/ticket/2113.





Unless SA_AMF_COMPONENT_NAME is not exported, health check is not started for 
unregistered process.
 

As APPENDIX B on page 442 specifies that saAmfHealthcheckStart can be called in 
the context of any process , whether it is not registered or not



---

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] #248 "amf: Incorrect return code from saAmfComponentErrorReport_4 () and saAmfComponentErrorClear_4()".

2017-07-20 Thread Nagendra Kumar via Opensaf-tickets

The patch is tested on CS #8791


---

** [tickets:#248] "amf: Incorrect return code from saAmfComponentErrorReport_4 
() and saAmfComponentErrorClear_4()". **

**Status:** review
**Milestone:** 5.17.10
**Created:** Thu May 16, 2013 06:41 AM UTC by Praveen
**Last Updated:** Thu Jul 20, 2017 07:56 AM UTC
**Owner:** Nagendra Kumar


Migrated from http://devel.opensaf.org/ticket/2817.

Changeset:3728
 When saAmfComponentErrorReport_4() and saAmfComponentErrorClear_4() are called 
after finalizing the amfHandle(calling saAmfFinalize()), both of them returns 
SA_AIS_ERR_VERSION instead of SA_AIS_ERR_BAD_HANDLE.



---

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] #248 "amf: Incorrect return code from saAmfComponentErrorReport_4 () and saAmfComponentErrorClear_4()".

2017-07-20 Thread Nagendra Kumar via Opensaf-tickets

Attched the patch


Attachments:

- 
[248_1.patch](https://sourceforge.net/p/opensaf/tickets/_discuss/thread/e78dae72/2a55/attachment/248_1.patch)
 (1.1 kB; application/octet-stream)


---

** [tickets:#248] "amf: Incorrect return code from saAmfComponentErrorReport_4 
() and saAmfComponentErrorClear_4()". **

**Status:** assigned
**Milestone:** 5.2.FC
**Created:** Thu May 16, 2013 06:41 AM UTC by Praveen
**Last Updated:** Thu Jul 20, 2017 07:55 AM UTC
**Owner:** Nagendra Kumar


Migrated from http://devel.opensaf.org/ticket/2817.

Changeset:3728
 When saAmfComponentErrorReport_4() and saAmfComponentErrorClear_4() are called 
after finalizing the amfHandle(calling saAmfFinalize()), both of them returns 
SA_AIS_ERR_VERSION instead of SA_AIS_ERR_BAD_HANDLE.



---

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] #2104 nid: Use the tipc command instead of tipc-config

2017-07-20 Thread Anders Widell via Opensaf-tickets

Yes, the tipc command is included in the iproute2 package.

The scripts could be rewritten to use the new tipc command instead of the old 
tipc-config command. For backwards compatibility with systems that don't have 
the tipc command, we could provide a shell script: /usr/local/lib/opensaf/tipc, 
which emulates the needed functionality of the tipc command, by calling the 
tipc-config command.


---

** [tickets:#2104] nid: Use the tipc command instead of tipc-config**

**Status:** unassigned
**Milestone:** future
**Created:** Fri Oct 07, 2016 04:58 PM UTC by Anders Widell
**Last Updated:** Wed Feb 01, 2017 10:05 AM UTC
**Owner:** nobody


The tipc-config command is obsolete and no longer being maintained. We should 
switch to using the "tipc" command instead.


---

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] #248 "amf: Incorrect return code from saAmfComponentErrorReport_4 () and saAmfComponentErrorClear_4()".

2017-07-20 Thread Nagendra Kumar via Opensaf-tickets

- **status**: assigned --> review
- **Milestone**: 5.2.FC --> 5.17.10



---

** [tickets:#248] "amf: Incorrect return code from saAmfComponentErrorReport_4 
() and saAmfComponentErrorClear_4()". **

**Status:** review
**Milestone:** 5.17.10
**Created:** Thu May 16, 2013 06:41 AM UTC by Praveen
**Last Updated:** Thu Jul 20, 2017 07:55 AM UTC
**Owner:** Nagendra Kumar


Migrated from http://devel.opensaf.org/ticket/2817.

Changeset:3728
 When saAmfComponentErrorReport_4() and saAmfComponentErrorClear_4() are called 
after finalizing the amfHandle(calling saAmfFinalize()), both of them returns 
SA_AIS_ERR_VERSION instead of SA_AIS_ERR_BAD_HANDLE.



---

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] #2445 log: reorganize headers and implementation

2017-07-20 Thread Canh Truong via Opensaf-tickets

- **status**: accepted --> review
- **Comment**:



  Part1 -  Fix cppcheck, cpplint, replace nullptr for following files:
- lgs_amf.*, lgs_config.*, lgs_dest.*, lgs_evt.*, lgs_file.*,
  lgs_filehdl.*, lgs_nildest.*, lgs_unixsock_dest.*
  lgs_util.*, lgs_dest_test.*



---

** [tickets:#2445] log: reorganize headers and implementation**

**Status:** review
**Milestone:** 5.17.10
**Created:** Fri Apr 28, 2017 08:28 AM UTC by Vu Minh Nguyen
**Last Updated:** Sat Jul 01, 2017 04:15 PM UTC
**Owner:** Canh Truong


This ticket intends to do some enhancements:
1) Put public interfaces and its implementations in proper places (e.g: 
lgs_amf_init() interface could be put into lgs_amf.h file)
2) Fix all cppcheck messages
3) Fix all cpplint messages
4) Replace NULL by nullptr

Will divide the fix to several increaments. The purpose is to make the review 
patch small and avoid code rebasing. The work could be fixing all above items 
for few files, then send it out for review. 


---

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] #2531 clm: saClmClusterTrack tests intermittently failing

[tickets] [opensaf:tickets] #2522 dtm: if TCP_USER_TIMEOUT closes socket, no attempt is make to reconnect

[tickets] [opensaf:tickets] #2522 dtm: if TCP_USER_TIMEOUT closes socket, no attempt is make to reconnect

[tickets] [opensaf:tickets] #2528 clm: CLM does not handle ERR_BAD_HANDLE from saImmOmSearchInitialize

[tickets] [opensaf:tickets] #2531 clm: saClmClusterTrack tests intermittently failing

[tickets] [opensaf:tickets] #2531 clm: saClmClusterTrack tests intermittently failing

[tickets] [opensaf:tickets] #248 "amf: Incorrect return code from saAmfComponentErrorReport_4 () and saAmfComponentErrorClear_4()".

[tickets] [opensaf:tickets] #333 amf: saAmfHealthcheckStart returns SA_AIS_ERR_NOT_EXIST when SA_AMF_COMPONENT_NAME is not exported.

[tickets] [opensaf:tickets] #248 "amf: Incorrect return code from saAmfComponentErrorReport_4 () and saAmfComponentErrorClear_4()".

[tickets] [opensaf:tickets] #248 "amf: Incorrect return code from saAmfComponentErrorReport_4 () and saAmfComponentErrorClear_4()".

[tickets] [opensaf:tickets] #2104 nid: Use the tipc command instead of tipc-config

[tickets] [opensaf:tickets] #248 "amf: Incorrect return code from saAmfComponentErrorReport_4 () and saAmfComponentErrorClear_4()".

[tickets] [opensaf:tickets] #2445 log: reorganize headers and implementation

13 matches

Site Navigation

Mail list logo

Footer information