[tickets] [opensaf:tickets] #1510 CKPT: cpnd crashes during checkpoint open timeout with large sections

[A V Mahesh (AVM)]

- **Milestone**: 4.7.2 --> future
- **Comment**:

As I understood When a collocated checkpoint replica is opened, and the 
active replica has large numbers of sections (~200k) and each sections
size is approximately 2k , you are seeing the issue .


So for debugging/assing the issue  just tune these below cpasv sync 
timeout variables fist , if increasing these values resolves the issue, then we 
can think of 
alternates  solution ,some thing  like dynamically calculating the sync time 
out time value 
for the NON active collocated checkpoint replica opened


osaf/libs/common/cpsv/include/cpa_def.h:#define CPSV_WAIT_TIME 1400
/* MDS wait time in case of syncronous call */
osaf/libs/common/cpsv/include/cpnd_cb.h:#define CPSV_WAIT_TIME  1000
osaf/libs/common/cpsv/include/cpd_cb.h:#define CPSV_WAIT_TIME  1000




---

** [tickets:#1510] CKPT: cpnd crashes during checkpoint open timeout with large 
sections**

**Status:** review
**Milestone:** future
**Created:** Thu Oct 01, 2015 04:14 PM UTC by Alex Jones
**Last Updated:** Wed May 04, 2016 07:08 PM UTC
**Owner:** Alex Jones


When opening a collocated checkpoint replica where the active has large numbers 
of sections (~200k), the sync from the active can timeout with errorcode 
SA_AIS_ERR_TRY_AGAIN. In this case the code deletes the memory for the node, 
but does not delete the node from the db. When the checkpoint access is tried 
again, the freed memory for the node is still in the db, and ckptnd crashes.

Valgrind analysis shows the following:

==53610== Thread 1:
==53610== Invalid read of size 4
==53610==at 0x4E4D7C4: ncs_patricia_tree_get (patricia.c:93)
==53610==by 0x40400D: cpnd_ckpt_node_get (cpnd_db.c:42)
==53610==by 0x40D1A2: cpnd_process_evt (cpnd_evt.c:1957)
==53610==by 0x40E9D6: cpnd_main_process (cpnd_init.c:568)
==53610==by 0x403882: main (cpnd_main.c:72)
==53610==  Address 0x687de60 is 0 bytes inside a block of size 1,072 free'd
==53610==at 0x4C29D4E: free (in 
/usr/lib64/valgrind/vgpreload_memcheck-amd64-linux.so)
==53610==by 0x40A827: cpnd_evt_proc_ckpt_open (cpnd_evt.c:983)
==53610==by 0x40D426: cpnd_process_evt (cpnd_evt.c:202)
==53610==by 0x40E9D6: cpnd_main_process (cpnd_init.c:568)
==53610==by 0x403882: main (cpnd_main.c:72)
==53610== 
==53610== Invalid read of size 8
==53610==at 0x4E4D7C0: ncs_patricia_tree_get (patricia.c:90)
==53610==by 0x40400D: cpnd_ckpt_node_get (cpnd_db.c:42)
==53610==by 0x40D1A2: cpnd_process_evt (cpnd_evt.c:1957)
==53610==by 0x40E9D6: cpnd_main_process (cpnd_init.c:568)
==53610==by 0x403882: main (cpnd_main.c:72)
==53610==  Address 0x687de70 is 16 bytes inside a block of size 1,072 free'd
==53610==at 0x4C29D4E: free (in 
/usr/lib64/valgrind/vgpreload_memcheck-amd64-linux.so)
==53610==by 0x40A827: cpnd_evt_proc_ckpt_open (cpnd_evt.c:983)
==53610==by 0x40D426: cpnd_process_evt (cpnd_evt.c:202)
==53610==by 0x40E9D6: cpnd_main_process (cpnd_init.c:568)
==53610==by 0x403882: main (cpnd_main.c:72)
==53610== 
==53610== Invalid read of size 8
==53610==at 0x4E4D7FB: ncs_patricia_tree_get (patricia.c:435)
==53610==by 0x40400D: cpnd_ckpt_node_get (cpnd_db.c:42)
==53610==by 0x40D1A2: cpnd_process_evt (cpnd_evt.c:1957)
==53610==by 0x40E9D6: cpnd_main_process (cpnd_init.c:568)
==53610==by 0x403882: main (cpnd_main.c:72)
==53610==  Address 0x687de78 is 24 bytes inside a block of size 1,072 free'd
==53610==at 0x4C29D4E: free (in 
/usr/lib64/valgrind/vgpreload_memcheck-amd64-linux.so)
==53610==by 0x40A827: cpnd_evt_proc_ckpt_open (cpnd_evt.c:983)
==53610==by 0x40D426: cpnd_process_evt (cpnd_evt.c:202)
==53610==by 0x40E9D6: cpnd_main_process (cpnd_init.c:568)
==53610==by 0x403882: main (cpnd_main.c:72)
==53610== 
==53610== Invalid read of size 1
==53610==at 0x4C2D0B9: bcmp (in 
/usr/lib64/valgrind/vgpreload_memcheck-amd64-linux.so)
==53610==by 0x4E4D803: ncs_patricia_tree_get (patricia.c:435)
==53610==by 0x40400D: cpnd_ckpt_node_get (cpnd_db.c:42)
==53610==by 0x40D1A2: cpnd_process_evt (cpnd_evt.c:1957)
==53610==by 0x40E9D6: cpnd_main_process (cpnd_init.c:568)
==53610==by 0x403882: main (cpnd_main.c:72)
==53610==  Address 0x687de80 is 32 bytes inside a block of size 1,072 free'd
==53610==at 0x4C29D4E: free (in 
/usr/lib64/valgrind/vgpreload_memcheck-amd64-linux.so)
==53610==by 0x40A827: cpnd_evt_proc_ckpt_open (cpnd_evt.c:983)
==53610==by 0x40D426: cpnd_process_evt (cpnd_evt.c:202)
==53610==by 0x40E9D6: cpnd_main_process (cpnd_init.c:568)
==53610==by 0x403882: main (cpnd_main.c:72)
==53610== 
==53610== Invalid read of size 1
==53610==at 0x4C2D0D0: bcmp (in 
/usr/lib64/valgrind/vgpreload_memcheck-amd64-linux.so)
==53610==by 0x4E4D803: ncs_patricia_tree_get (patricia.c:435)
==53610==by 0x40400D: cpnd_ckpt_node_get (cpnd_db.c:42)
==53610==by 0x40D1A2: cpnd_process_evt (cpnd_evt.c:1957)
==53610==by 0x40E9D6: cpnd_main_process (cpnd_init.c:568)

[tickets] [opensaf:tickets] #1553 AMF: Send CsiSetCallback immediately when CSI attributes are modified (loadbalancing, VM migration usecases)

[Praveen]

Updated PR doc  in :
changeset:   190:c4d93e4c37f7
tag: tip
user:praveen.malv...@oracle.com
date:Tue Sep 20 11:10:08 2016 +0530
summary: amf: update PR doc for enhancements [#1608], [#1454] and [#1553]



---

** [tickets:#1553] AMF: Send CsiSetCallback immediately when CSI attributes are 
modified (loadbalancing, VM migration usecases)**

**Status:** fixed
**Milestone:** 5.1.FC
**Labels:** VM migration loadbalancer-synchronization 
**Created:** Wed Oct 21, 2015 10:03 AM UTC by Mathi Naickan
**Last Updated:** Mon Aug 29, 2016 12:35 PM UTC
**Owner:** Praveen


AMF is the 'workload' manager in OpenSAF. There are also loadbalancers external 
to OpenSAF that can choose to modify some attributes of an application 
component's workload which is currently assigned ACTIVE (without loss of 
service). In such scenarios it is possible (and necessary) for both AMF and the 
external load balancers to throttle each other. The reverse throttling(from AMF 
to the external load balancer) is possible based on any changes to the 
NodeCapacity limitations set in AMF, but that is for later/future 
considerations.

For eg:- Suppose an application component (say modelled in n-way active) is 
currently serving traffic originating from a source/target X, based on some 
network criteria the load balancer can choose to re-configure/modify that 
application to serve traffic from a different source/target Y. Such change in 
information related to that workload could be communicated to that application 
component at runtime without loss of service.

The above scenario is achieved if the admin (or a loadbalancer) modifies the 
attributes of a workload i.e. csiattribute name-value pair, and then the 
altered name-value information is communicated to that application or 
associated application components 'immediately' instead of waiting for the next 
admin operation!

Today AMF supports modifying csi attribute name-value without requiring that SI 
to be locked. But the modified attributes are sent only after a subsequent 
admin operation. This ticket is intended to evaluate and support sending 
CSIsetcallback (with the same CSI state information but modified csi 
attributes) immediately.

Implementation scope:
 Introduction of new resources: 
-saAmfInitialize_5() API,
-callback structure SaAmfCallbacksT_5 and
-CSI Attribute Change callback OsafCsiAttributeChangeCallbackT.
-new attribute osafAmfCSICommunicateCsiAttributeChange in class SaAmfCSI.
As a part of \#1553, minor version (SAF) of AMF will be updated to 02 because 
of introduction of  aobve mentioned resources in agent. So highest supported 
version now becomes B.04.02.

Description of new resources at agent:
A)OsafCsiAttributeChangeCallbackT
AMF will use this callback to communicate to a running component
any runtime change in the assigned CSI Attribute value.
A component can register this callback using new API 
saAmfInitialize_5().
Callback Characteristics:
-Arguments:
 typedef void (*OsafCsiAttributeChangeCalbackT)( SaInvocationT 
invocation,
const SaNameT *csiName, SaAmfCSIAttributeListT 
csiAttr);
-After receving this callback, a component will have to respond 
to AMFND
  using saAmfResponse_4() API with the same invocation number.
-Callback will be invoked in the context of registered process.
-Callback is meant for SA-Aware component, PROXIED PI component 
and
 PROXIED NPI component. In cases of proxied it will be given to 
proxy.
-Callback timeout will be same as 
saAmfCompCSISetCallbackTimeout or
 saAmfCtDefCallbackTimeout.
B)SaAmfCallbacksT_5 (new callback structure)
typedef struct {
SaAmfHealthcheckCallbackT   
saAmfHealthcheckCallback;
SaAmfComponentTerminateCallbackT
saAmfComponentTerminateCallback;
SaAmfCSISetCallbackTsaAmfCSISetCallback;
SaAmfCSIRemoveCallbackT 
saAmfCSIRemoveCallback;
SaAmfProtectionGroupTrackCallbackT_4
saAmfProtectionGroupTrackCallback;
SaAmfProxiedComponentInstantiateCallbackT   
saAmfProxiedComponentInstantiateCallback;
SaAmfProxiedComponentCleanupCallbackT   
saAmfProxiedComponentCleanupCallback;
SaAmfContainedComponentInstantiateCallbackT 
saAmfContainedComponentInstantiateCallback;
SaAmfContainedComponentCleanupCallbackT 
saAmfContainedComponentCleanupCallback;
OsafCsiAttributeChangeCallbackT 
osafCsiAttributeChangeCallback;
} SaAmfCallbacksT_5;
This is new callback structure consisting of all B.04.01 callbacks and 
newly
introduced OsafCsiAttributeChangeCallbackT. A component can register all
callbacks including 

[tickets] [opensaf:tickets] #2029 imm: fevs message lost during failover

[Hung Nguyen]

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



---

** [tickets:#2029] imm: fevs message lost during failover**

**Status:** review
**Milestone:** 4.7.2
**Created:** Tue Sep 13, 2016 11:05 AM UTC by Hung Nguyen
**Last Updated:** Thu Sep 15, 2016 10:11 AM UTC
**Owner:** Hung Nguyen
**Attachments:**

- [logs.7z](https://sourceforge.net/p/opensaf/tickets/2029/attachment/logs.7z) 
(250.9 kB; application/octet-stream)


There's fevs message loss when failing over between 2 SCs.


~~~
Sep  8 11:50:00 SC-2-1 osafimmnd[4241]: NO Implementer locally disconnected. 
Marking it as doomed 232 <754, 2010f> (@OpenSafImmPBE)
Sep  8 11:50:00 SC-2-1 osafimmnd[4241]: NO Implementer locally disconnected. 
Marking it as doomed 233 <755, 2010f> (OsafImmPbeRt_B)
...
Sep  8 11:50:00 SC-2-1 osafimmnd[4241]: NO Implementer disconnected 233 <755, 
2010f> (OsafImmPbeRt_B)
~~~


The IMMNDs never receive the D2ND_DISCARD_IMPL for @OpenSafImmPBE, so that 
applier keeps being mark as dying


~~~
Sep  8 11:50:02 SC-2-1 osafimmnd[4241]: NO ImmModel::getPbeBSlave reports 
missing PbeBSlave locally => unsafe
Sep  8 11:50:03 SC-2-1 osafimmnd[4241]: NO ImmModel::getPbeBSlave reports 
missing PbeBSlave locally => unsafe
Sep  8 11:50:04 SC-2-1 osafimmnd[4241]: NO ImmModel::getPbeBSlave reports 
missing PbeBSlave locally => unsafe
...
Sep  8 11:59:08 SC-2-1 osafimmnd[4241]: NO ImmModel::getPbeBSlave reports 
missing PbeBSlave locally => unsafe
Sep  8 11:59:09 SC-2-1 osafimmnd[4241]: NO ImmModel::getPbeBSlave reports 
missing PbeBSlave locally => unsafe
Sep  8 11:59:10 SC-2-1 osafimmnd[4241]: NO ImmModel::getPbeBSlave reports 
missing PbeBSlave locally => unsafe
...
~~~

The main problem is the standby IMMD also broadcast D2ND_DISCARD_NODE message 
when it receives an NCSMDS_DOWN from IMMND. See immd_process_immnd_down().

If the NCSMDS_DOWN event comes to the 2 IMMDs at the same time, the 2 
D2ND_DISCARD_NODE messages will be stamped with the same number. One of the 2 
will be discarded by IMMNDs, no problem here.
But if there's a latency of NCSMDS_DOWN event, an other fevs message (in this 
case it's D2ND_DISCARD_IMPL for @OpenSafImmPBE) will be discarded by IMMNDs, 
that will cause fevs message loss.

Details of the problem is explained here


http://sequencediagram.org/index.html?initialData=A4QwTgLglgxloDsIAICSBZdARAjACgGUAVAIQEoAoUSWeEJNTLAJjwEEBhIy66ORFBnQA5LAGcKFMACMA9gA9ksgG4BTMI2z5i5ADRCW7LmQBcMAK5gwqhgDNVysQRsATDrPNITyHAAYALADMAGySMgpKahpComImMVhKCMgEHMzIUGLILrIA7ghhcooq6pq4hKSmwhwE2AQA+lgA8gDqwsgONhCSkgbalQC0AMTWLgB8CXEsoo2oqWwASlj1wk1YAKLIYhAgALbAqi7IuVAQABY+AYEA7L1MrJzcADxD0gA25qoDkyaizMtYOYcRbLDAABQAMshbLINAABJoHBAEEC2VC7XZgkjrQoRErRe5GbgmeyOZwINweBiZZAIWQoczAFwgCCHZAQWQAc1U51KJ3OZRwAB0ECKxLIMihtntgFlechdqoxGIQNzjqcLn4grcKAYHsZhqMJphYiZpgCgSD6uCodL9mz+Zqrjq+hVyC9OdYbN9CY9TOgSBwxMoFUqVWqYRotTdccUooK3aYwWAoAwPCh5blwAhU5yRSKWmxkOgw6rVMgYFSICZo9dkABqHzIACEAF5LtqeuE46UfkQzuXJtlMjBwEdzbN5ktrehIaHlWX8whpKpR+YxOXZLZsoy3rAWWzSVkEOZdiuwEv+yyAORZXJnACeyARSJRaIxWM2NLpKFs5jebxPi4I5jocsaRL2vrGL8NR1I0rTtJ0SCXmcNJISglaKnKEp6sgbwHho5z0IKQA


~~~
Sep  8 11:50:00 SC-2-1 osafimmd[4226]: WA IMMND DOWN on active controller 2 
detected at standby immd!! 1. Possible failover
...
Sep  8 11:50:00 SC-2-1 osafimmd[4226]: WA Message count:10437 + 1 != 10437
Sep  8 11:50:00 SC-2-1 osafimmnd[4241]: WA DISCARD DUPLICATE FEVS message:10437
Sep  8 11:50:00 SC-2-1 osafimmnd[4241]: WA Error code 2 returned for message 
type 82 - ignoring
~~~


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.--
___
Opensaf-tickets mailing list
Opensaf-tickets@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets

[tickets] [opensaf:tickets] #2041 Msg: saMsgInitialize is returning continuous TRY_AGAINS after mqsv ndrestarts in backward compatability.

[Ramesh]

- **Component**: msg --> imm
- **Comment**:

Seems this failure need to be investigate from IMM context as 
"immutil_saImmOiInitialize_2()" is returning SA_AIS_ERR_TIMEOUT error code.



---

** [tickets:#2041] Msg: saMsgInitialize is returning continuous TRY_AGAINS 
after mqsv ndrestarts in backward compatability.**

**Status:** unassigned
**Milestone:** 4.7.2
**Created:** Fri Sep 16, 2016 12:13 PM UTC by Madhurika Koppula
**Last Updated:** Fri Sep 16, 2016 12:13 PM UTC
**Owner:** nobody
**Attachments:**

- 
[messages-20160921.bz2](https://sourceforge.net/p/opensaf/tickets/2041/attachment/messages-20160921.bz2)
 (240.9 kB; application/octet-stream)


**Environment Details:**
OS : Suse 64bit
Setup : 4 nodes ( 2 controllers and 2 payloads with headless feature disabled & 
1PBE enabled ).

Backward Compatability:
Opensaf versions on nodes:
SC-1 (5.0), SC-2 (5.1 FC), PL-3 (5.0), PL-4(5.1FC).

**Summary:**  saMsgInitialize is returning continuous TRY_AGAINS after 
mqnd_imm_initialize failed with ERR_TIMEOUT.

**Steps followed & Observed behaviour:**

Mqsv test application is being ran by continuously killing mqnd.

Observations:

saMsgInitialize failed with continuous TRY_AGAIN. Below is the snapshot. 

100|0| Version : B.3.1
100|0| RETRY   : saMsgInitialize with all valid parameters
100|0| Return Value: SA_AIS_ERR_TRY_AGAIN
100|0|
100|0|
100|0| Version : B.3.1
100|0| Version : B.3.1
100|0| Version : B.3.1
100|0| Version : B.3.1
100|0| Version : B.3.1
100|0| Version : B.3.1
100|0| Version : B.3.1
100|0| Version : B.3.1
100|0| Version : B.3.1 Retry Count : 10
100|0|
100|0| Version : B.3.1
100|0| Version : B.3.1
100|0| Version : B.3.1
100|0| Version : B.3.1
100|0| Version : B.3.1
100|0| Version : B.3.1
100|0| Version : B.3.1
100|0| Version : B.3.1
100|0| Version : B.3.1
100|0| Version : B.3.1 Retry Count : 20
100|0|
100|0| Version : B.3.1
100|0| Version  Sun Sep 18 11:51:19 IST 2016
100|0|Sun Sep 18 11:51:19 IST 2016
100|0|Sun Sep 18 11:51:59 IST 2016
100|0|Sun Sep 18 11:51:59 IST 2016
100|0|Sun Sep 18 11:52:39 IST 2016
100|0|Sun Sep 18 11:52:39 IST 2016

100|0| Version : B.3.1
100|0| Version : B.3.1
100|0| Version : B.3.1
100|0| Version : B.3.1
100|0| Version : B.3.1
100|0| Version : B.3.1
100|0| Version : B.3.1
100|0| Version : B.3.1 Retry Count : 30
100|0|
100|0| Version : B.3.1
100|0| Version : B.3.1
100|0| Version : B.3.1
100|0| Version : B.3.1
100|0| Version : B.3.1
100|0| Version : B.3.1
100|0| Version : B.3.1
100|0| Version : B.3.1
100|0| Version : B.3.1
100|0| Version : B.3.1 Retry Count : 40
100|0| Try again count exceeded* TEST CASE FAILED 

Below is the snippet of syslog of SC-1:


Sep 18 11:48:32 SCALE_SLOT-41 osafimmnd[19813]: NO Implementer (applier) 
connected: 2462 (@OpenSafImmReplicatorA) <20504, 2010f>
Sep 18 11:48:32 SCALE_SLOT-41 osafntfimcnd[19819]: NO Started
Sep 18 11:48:39 SCALE_SLOT-41 osafamfd[1816]: NO Re-initializing with IMM
Sep 18 11:48:39 SCALE_SLOT-41 osafimmnd[19813]: NO Implementer connected: 2463 
(safAmfService) <20506, 2010f>
Sep 18 11:48:39 SCALE_SLOT-41 osafamfd[1816]: NO Finished re-initializing with 
IMM

**Sep 18 11:48:39 SCALE_SLOT-41 osafmsgnd[19792]: ER mqnd_imm_initialize 
Failed: 5**

Sep 18 11:48:39 SCALE_SLOT-41 osafamfnd[1826]: 
'safComp=MQND,safSu=SC-1,safSg=NoRed,safApp=OpenSAF'unregistered
Sep 18 11:48:39 SCALE_SLOT-41 osafmsgnd[19792]: CR Destroying the shared memory 
segment failed
Sep 18 11:48:39 SCALE_SLOT-41 osafmsgnd[19792]: ER saAmfComponentUnregister 
Failed with error 9
Sep 18 11:48:39 SCALE_SLOT-41 osafmsgnd[19792]: ER Cb is NULL
Sep 18 11:48:49 SCALE_SLOT-41 osafimmnd[19813]: NO Implementer connected: 2464 
(MsgQueueService131343) <20507, 2010f>
Sep 18 11:48:49 SCALE_SLOT-41 osafimmnd[19813]: NO Implementer locally 
disconnected. Marking it as doomed 2464 <20507, 2010f> (MsgQueueService131343)

Attachments:
1)Syslog of 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] #2038 NTF: Using sizeof(string) for lengthAdditionalText results in SA_AIS_ERR_INVALID_PARAM

[Minh Hon Chau]

- **status**: review --> fixed
- **assigned_to**: Minh Hon Chau -->  nobody 
- **Comment**:

changeset:   8101:9ffc9d219684
tag: tip
parent:  8099:26140709359f
user:minh-chau 
date:Tue Sep 20 14:54:39 2016 +1000
summary: NTF: Replace sizeof by strlen in ntftest [#2038]

changeset:   8100:9f1767961132
branch:  opensaf-5.1.x
parent:  8098:5a4d66f467f3
user:minh-chau
date:Tue Sep 20 14:52:07 2016 +1000
summary: NTF: Replace sizeof by strlen in ntftest [#2038]




---

** [tickets:#2038] NTF: Using sizeof(string) for lengthAdditionalText results 
in SA_AIS_ERR_INVALID_PARAM**

**Status:** fixed
**Milestone:** 5.1.RC2
**Created:** Thu Sep 15, 2016 08:47 AM UTC by Minh Hon Chau
**Last Updated:** Thu Sep 15, 2016 11:15 PM UTC
**Owner:** nobody


After patch of #2006, now if ntf client uses sizeof(string) + 1 to specify the 
string length for lengthAdditionalText, that will result in 
SA_AIS_ERR_INVALID_PARAM when sending notification.

Some existing ntftests have failed because those tests are still using sizeof, 
which could be fixed in ntftests. However, that could be a *complaint* from 
real applications which have been running without problem (application's code 
are using sizeof())


---

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] #1986 log: logtest fails when run after immomtest

[Vu Minh Nguyen]

- **status**: review --> fixed
- **assigned_to**: Vu Minh Nguyen -->  nobody 
- **Comment**:

changeset:   8099:26140709359f
tag: tip
parent:  8097:b6faa36cf2ce
user:Vu Minh Nguyen 
date:Tue Sep 20 11:24:27 2016 +0700
summary: log: fix logtest fails when run after immomtest [#1986]

changeset:   8098:5a4d66f467f3
branch:  opensaf-5.1.x
parent:  8096:f6760a2e9c76
user:Vu Minh Nguyen 
date:Tue Sep 20 11:24:27 2016 +0700
summary: log: fix logtest fails when run after immomtest [#1986]



---

** [tickets:#1986] log: logtest fails when run after immomtest**

**Status:** fixed
**Milestone:** 5.1.RC2
**Created:** Tue Aug 30, 2016 09:03 AM UTC by Anders Widell
**Last Updated:** Tue Sep 13, 2016 11:22 AM UTC
**Owner:** nobody


If I first run immomtest and then logtest, I get the following result:

~~~

Suite 1: Library Life Cycle
1  PASSED   saLogInitialize() OK;
2  PASSED   saLogInitialize() with NULL pointer to handle;
3  PASSED   saLogInitialize() with NULL pointer to callbacks;
4  PASSED   saLogInitialize() with NULL callbacks AND version;
5  PASSED   saLogInitialize() with uninitialized handle;
6  PASSED   saLogInitialize() with uninitialized version;
7  PASSED   saLogInitialize() with too high release level;
8  PASSED   saLogInitialize() with minor version set to 1;
9  PASSED   saLogInitialize() with major version set to 3;
   10  PASSED   saLogSelectionObjectGet() OK;
   11  PASSED   saLogSelectionObjectGet() with NULL log handle;
   12  PASSED   saLogDispatch() OK;
   13  PASSED   saLogFinalize() OK;
   14  PASSED   saLogFinalize() with NULL log handle;

Suite 2: Log Service Operations
1  PASSED   saLogStreamOpen_2() system stream OK;
2  PASSED   saLogStreamOpen_2() notification stream OK;
3  PASSED   saLogStreamOpen_2() alarm stream OK;
4  PASSED   Create app stream OK;
5  PASSED   Create and open app stream;
6  PASSED   saLogStreamOpen_2() - NULL ptr to handle;
7  PASSED   saLogStreamOpen_2() - NULL logStreamName;
8  PASSED   Open app stream second time with altered logFileName;
9  PASSED   Open app stream second time with altered logFilePathName;
   10  PASSED   Open app stream second time with altered logFileFmt;
   11  PASSED   Open app stream second time with altered maxLogFileSize;
   12  PASSED   Open app stream second time with altered maxLogRecordSize;
   13  PASSED   Open app stream second time with altered maxFilesRotated;
   14  PASSED   Open app stream second time with altered haProperty;
   15  PASSED   Open app with logFileFmt == NULL;
   16  PASSED   Open app stream second time with logFileFmt == NULL;
   17  PASSED   Open app stream with NULL logFilePathName;
   18  PASSED   Open app stream with '.' logFilePathName;
   19  PASSED   Open app stream with invalid logFileFmt;
   20  PASSED   Open app stream with unsupported logFullAction;
   21  PASSED   Open non exist app stream with NULL create attrs;
   22  PASSED   saLogStreamOpenAsync_2(), Not supported;
   23  PASSED   saLogStreamOpenCallbackT() OK;
   24  PASSED   saLogWriteLog(), Not supported;
   25  PASSED   saLogWriteAsyncLog() system OK;
   26  PASSED   saLogWriteAsyncLog() alarm OK;
   27  PASSED   saLogWriteAsyncLog() notification OK;
   28  PASSED   saLogWriteAsyncLog() with NULL logStreamHandle;
   29  PASSED   saLogWriteAsyncLog() with invalid logStreamHandle;
   30  PASSED   saLogWriteAsyncLog() with invalid ackFlags;
   31  PASSED   saLogWriteAsyncLog() with NULL logRecord ptr;
   32  PASSED   saLogWriteAsyncLog() logSvcUsrName == NULL;
   33  PASSED   saLogWriteAsyncLog() logSvcUsrName == NULL and envset;
   34  PASSED   saLogWriteAsyncLog() with logTimeStamp set;
   35  PASSED   saLogWriteAsyncLog() without logTimeStamp set;
   36  PASSED   saLogWriteAsyncLog() 1800 bytes logrecord (ticket #203);
   37  PASSED   saLogWriteAsyncLog() invalid severity;
   38  PASSED   saLogWriteLogAsync() logBufSize > strlen(logBuf) + 1;
   39  PASSED   saLogWriteLogAsync() logBufSize > SA_LOG_MAX_RECORD_SIZE;
   40  PASSED   saLogWriteLogCallbackT() SA_DISPATCH_ONE;
   41  PASSED   saLogWriteLogCallbackT() SA_DISPATCH_ALL;
   42  PASSED   saLogFilterSetCallbackT OK;
   43  PASSED   saLogStreamClose OK;
   44  PASSED   saLogStreamOpen_2 with maxFilesRotated = 0, ERR;
   45  PASSED   saLogStreamOpen_2 with maxFilesRotated = 128, ERR;
   46  PASSED   saLogStreamOpen_2 with logFileName > 218 characters, ERR;
   47  PASSED   saLogStreamOpen_2 with invalid filename;
   48  PASSED   saLogStreamOpen_2 with maxLogRecordSize > MAX_RECSIZE, ERR;
   49  PASSED   saLogStreamOpen_2 with maxLogRecordSize < 150, ERR;
   

[tickets] [opensaf:tickets] #1913 log: improve test cases for log service

[Vu Minh Nguyen]

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

Change status to `accept`. Need to figure out the better way to refactor the 
test code.



---

** [tickets:#1913] log: improve test cases for log service**

**Status:** accepted
**Milestone:** 5.2.FC
**Created:** Thu Jul 14, 2016 03:30 AM UTC by Vu Minh Nguyen
**Last Updated:** Tue Aug 30, 2016 01:29 AM UTC
**Owner:** Canh Truong


Most test cases for the log service are made in a simplified way compared to 
how the log service should be handled when used by an application. Because of 
such simplifications test cases may report FAIL or even abort also if the log 
service not actually has failed. To get rid of this problem there are two 
things that should be improved:

1) Many (all) of the APIs may return SA_AIS_ERR_TRY_AGAIN this is not a fault 
and should normally not fail a test case instead proper TRY AGAIN handling 
should be used with all API function calls. 
2) Several test cases have dependency on other test cases. Will make them 
independence on others. 
3) Many test cases do change settings such as IMM attribute values before 
running tests, but not restore them back to previous values. 


---

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] #2032 ckpt: ckpttest for long dn (5 55, 5 57, 7 12) is failing

[Vo Minh Hoang]

- **status**: unassigned --> accepted
- **assigned_to**: Vo Minh Hoang



---

** [tickets:#2032] ckpt: ckpttest for long dn (5 55, 5 57, 7 12) is failing**

**Status:** accepted
**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:** Vo Minh Hoang


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] #1991 AMF: Existing PG tracking should not be stopped for CURRENT flag

[Minh Hon Chau]

- **status**: review --> fixed
- **assigned_to**: Long HB Nguyen -->  nobody 
- **Comment**:

changeset:   8097:b6faa36cf2ce
tag: tip
parent:  8095:06794cdbd3ee
user:Long Nguyen 
date:Tue Sep 20 11:54:58 2016 +1000
summary: amfa: fix saAmfProtectionGroupTrackStop [#1991]

changeset:   8096:f6760a2e9c76
branch:  opensaf-5.1.x
parent:  8094:6e6980f88b50
user:Long Nguyen 
date:Tue Sep 20 11:53:55 2016 +1000
summary: amfa: fix saAmfProtectionGroupTrackStop [#1991]





---

** [tickets:#1991] AMF: Existing PG tracking should not be stopped  for CURRENT 
flag**

**Status:** fixed
**Milestone:** 5.1.RC2
**Created:** Wed Aug 31, 2016 09:44 AM UTC by Srikanth R
**Last Updated:** Fri Sep 16, 2016 02:14 AM UTC
**Owner:** nobody


5.1.FC : changeset - 6997

Issue : Existing PG tracking should not be stopped  for CURRENT call


Steps performed :

-> Call saAmfInitialize_4()
-> Call saAmfProtectionGroupTrack_4() with SA_TRACK_CURRENT flag.
-> Call saAmfProtectionGroupTrack_4() with SA_TRACK_CHANGES flag.
-> Call saAmfProtectionGroupTrack_4() with SA_TRACK_CURRENT flag.
-> Call saAmfProtectionGroupTrackStop()


Observed output :

TrackStop returns ERR_NOT_EXIST, indicating that tracking is not started 
earlier. 


Expected output:

   TrackStop() api should  return SA_AIS_OK and in the earlier release, api is 
returning SA_AIS_OK.
 
 According to the B04.01 spec 7.11.1 page 318 ,  Tracking should not be stopped 
untill TrackStop() is called explicitly.

Once saAmfProtectionGroupTrack_4() has been called with trackFlags
containing either SA_TRACK_CHANGES or SA_TRACK_CHANGES_ONLY, notification
callbacks can only be stopped by an invocation of
saAmfProtectionGroupTrackStop().



---

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] #2023 AMF : Long DN RT objects creation failed with ERR_TOO_LONG (13)

[Minh Hon Chau]

- **status**: unassigned --> accepted
- **assigned_to**: Minh Hon Chau
- **Milestone**: 4.7.2 --> 5.2.FC



---

** [tickets:#2023] AMF : Long DN RT objects creation failed with ERR_TOO_LONG 
(13)**

**Status:** accepted
**Milestone:** 5.2.FC
**Created:** Sat Sep 10, 2016 10:57 AM UTC by Srikanth R
**Last Updated:** Thu Sep 15, 2016 05:34 AM UTC
**Owner:** Minh Hon Chau
**Attachments:**

- 
[2023.tgz](https://sourceforge.net/p/opensaf/tickets/2023/attachment/2023.tgz) 
(159.7 kB; application/x-compressed-tar)


Environment details
--
OS : Suse 64bit 
Changeset : 7997  ( 5.1.FC)
Setup : 5 nodes ( 2 controllers and 3 payloads with headless feature disabled & 
no PBE  & longDn feature enabled )
AMF Application : 2N model with SUs mapped on PL-3,PL-4


Summary :
--
 Long DN RT objects creation failed with ERR_TOO_LONG during unlock operation 
of SU.


Steps followed & Observed behaviour
--

-> Initially enabled the longDn feature.

-> Later imported the attached AMF configuration successfully.

-> Now performed unlock-in and unlock operation of SU, for which following 
error is observed in syslog.

Sep 10 16:11:43 CONTROLLER-2 osafamfnd[4279]: NO Assigned 
'safSi=AmfDemoabcdefghijklmnopqrstuvwxyzabcdefghijklmnopqrstuvwxyzabcdefghijklmnopqrstuvwxyzabcdefghijklmnopqrstuvwxyzabcdefghijklmnopqrstuvwxyzabcdefghijklmnopqrstuvwxyzabcdefghijklmnopqrstuvwxyzabcdefghijklmnopqrstuvwxyzabcdefghijklmnopqrstuvwxyzabcdefghijklmnopqrstuvwxyzabcdefghijklmnopqrstuvwxyzabcdefghijklmnopqrstuvwxyzabcdefghijklmnopqrstuvwxyzabcdefghijklmnopqrstuvwxyzabcdefghijklmnopqrstuvwxyzabcdefghijklmnopqrstuvwxyz,safApp=AmfDemoabcdefghijklmnopqrstuvwxyzabcdefghijklmnopqrstuvwxyzabcdefghijklmnopqrstuvwxyzabcdefghijklmnopqrstuvwxyzabcdefghijklmnopqrstuvwxyzabcdefghijklmnopqrstuvwxyzabcdefghijklmnopqrstuvwxyzabcdefghijklmnopqrstuvwxyzabcdefghijklmnopqrstuvwxyzabcdefghijklmnopqrstuvwxyzabcdefghijklmnopqrstuvwxyzabcdefghijklmnopqrstuvwxyzabcdefghijklmnopqrstuvwxyzabcdefghijklmnopqrstuvwxyzabcdefghijklmnopqrstuvwxyzabcdefghijklmnopqrstuvwxyz'
 ACTIVE to 'safSu=SU1,safSg=AmfDemoabcdefghijklmnopqrstuvwxyzabcdefghijklmnopq
 
rstuvwxyzabcdefghijklmnopqrstuvwxyzabcdefghijklmnopqrstuvwxyzabcdefghijklmnopqrstuvwxyzabcdefghijklmnopqrstuvwxyzabcdefghijklmnopqrstuvwxyzabcdefghijklmnopqrstuvwxyzabcdefghijklmnopqrstuvwxyzabcdefghijklmnopqrstuvwxyzabcdefghijklmnopqrstuvwxyzabcdefghijklmnopqrstuvwxyzabcdefghijklmnopqrstuvwxyzabcdefghijklmnopqrstuvwxyzabcdefghijklmnopqrstuvwxyzabcdefghijklmnopqrstuvwxyz,safApp=AmfDemoabcdefghijklmnopqrstuvwxyzabcdefghijklmnopqrstuvwxyzabcdefghijklmnopqrstuvwxyzabcdefghijklmnopqrstuvwxyzabcdefghijklmnopqrstuvwxyzabcdefghijklmnopqrstuvwxyzabcdefghijklmnopqrstuvwxyzabcdefghijklmnopqrstuvwxyzabcdefghijklmnopqrstuvwxyzabcdefghijklmnopqrstuvwxyzabcdefghijklmnopqrstuvwxyzabcdefghijklmnopqrstuvwxyzabcdefghijklmnopqrstuvwxyzabcdefghijklmnopqrstuvwxyzabcdefghijklmnopqrstuvwxyzabcdefghijklmnopqrstuvwxyz'
Sep 10 16:11:43 CONTROLLER-2 osafamfd[4265]: ER exec: create FAILED 13
Sep 10 16:11:46 CONTROLLER-2 osafamfd[4265]:** ER exec: create FAILED 13**


Below is the corresponding trace in osafamfd :


Sep 10 16:11:46.647681 osafamfd [4265:imm.cc:0396] >> execute
Sep 10 16:11:46.647730 osafamfd [4265:imm.cc:0142] >> exec: Create 
safCsi=AmfDemoabcdefghijklmnopqrstuvwxyzabcdefghijklmnopqrstuvwxyzabcdefghijklmnopqrstuvwxyzabcdefghijklmnopqrstuvwxyzabcdefghijklmnopqrstuvwxyzabcdefghijklmnopqrstuvwxyzabcdefghijklmnopqrstuvwxyzabcdefghijklmnopqrstuvwxyzabcdefghijklmnopqrstuvwxyzabcdefghijklmnopqrstuvwxyzabcdefghijklmnopqrstuvwxyzabcdefghijklmnopqrstuvwxyzabcdefghijklmnopqrstuvwxyzabcdefghijklmnopqrstuvwxyzabcdefghijklmnopqrstuvwxyzabcdefghijklmnopqrstuvwxyz_CSIA,safSi=AmfDemoabcdefghijklmnopqrstuvwxyzabcdefghijklmnopqrstuvwxyzabcdefghijklmnopqrstuvwxyzabcdefghijklmnopqrstuvwxyzabcdefghijklmnopqrstuvwxyzabcdefghijklmnopqrstuvwxyzabcdefghijklmnopqrstuvwxyzabcdefghijklmnopqrstuvwxyzabcdefghijklmnopqrstuvwxyzabcdefghijklmnopqrstuvwxyzabcdefghijklmnopqrstuvwxyzabcdefghijklmnopqrstuvwxyzabcdefghijklmnopqrstuvwxyzabcdefghijklmnopqrstuvwxyzabcdefghijklmnopqrstuvwxyzabcdefghijklmnopqrstuvwxyz,safApp=AmfDemoabcdefghijklmnopqrstuvwxyzabcdefghijklmnopqrstuvwxy
 zabcdefghijklmnopqrstuvT
Sep 10 16:11:46.647783 osafamfd [4265:imma_oi_api.c:2786] >> 
rt_object_create_common
Sep 10 16:11:46.647879 osafamfd [4265:imma_oi_api.c:2892] TR attr:safCSIComp
Sep 10 16:11:46.647908 osafamfd [4265:imma_oi_api.c:2892] TR 
attr:saAmfCSICompHAState
Sep 10 16:11:46.647927 osafamfd [4265:imma_oi_api.c:2892] TR 
attr:saAmfCSICompHAReadinessState
Sep 10 16:11:46.649108 osafamfd [4265:imma_oi_api.c:3063] << 
rt_object_create_common
Sep 10 16:11:46.649157 osafamfd [4265:imm.cc:0163] ER exec: create FAILED 13




---

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 

[tickets] [opensaf:tickets] #2048 opensaf/doc: no separate branches for 4.7 and 5.0.

[Anders Widell]

It is rare that we need to update the documentation for old releases. If you 
need to do this, you can create the branch when needed. E.g. if you wish to 
update the PR documentation for the OpenSAF 4.7.x track, you create an 
opensaf-4.7.x branch from by branching out from the 4.7.0 tag.


---

** [tickets:#2048] opensaf/doc: no separate branches for 4.7 and 5.0.**

**Status:** unassigned
**Milestone:** 4.7.2
**Created:** Mon Sep 19, 2016 11:43 AM UTC by Praveen
**Last Updated:** Mon Sep 19, 2016 11:43 AM UTC
**Owner:** nobody


It seems there are no separate branches for 4.7 and 5.0 for documentation.
Even they are not listed in closed brnaches.
Here is output of hg commands:
\# hg branch
default
\# hg branches
default  189:e4d420f962d3
\# hg branches -c
default  189:e4d420f962d3
opensaf-4.6.x181:0a4b9b47c55c (closed)
opensaf-4.5.x167:650e49539772 (closed)
opensaf-4.4.x155:81bbe5de2f18 (closed)
opensaf-4.3.x134:ff16f59fe449 (closed)
opensaf-4.2.x 98:b97c89fb2890 (closed)



---

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] #2050 PLM: update PR doc to address new virtualization configuration

[Alex Jones]

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



---

** [tickets:#2050] PLM: update PR doc to address new virtualization 
configuration**

**Status:** review
**Milestone:** 5.1.RC2
**Created:** Mon Sep 19, 2016 01:58 PM UTC by Alex Jones
**Last Updated:** Mon Sep 19, 2016 01:58 PM UTC
**Owner:** Alex Jones


This ticket is for updating the PLM PR doc to reflect virtualization 
enhancement in 5.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] #2050 PLM: update PR doc to address new virtualization configuration

[Alex Jones]

---

** [tickets:#2050] PLM: update PR doc to address new virtualization 
configuration**

**Status:** accepted
**Milestone:** 5.1.RC2
**Created:** Mon Sep 19, 2016 01:58 PM UTC by Alex Jones
**Last Updated:** Mon Sep 19, 2016 01:58 PM UTC
**Owner:** Alex Jones


This ticket is for updating the PLM PR doc to reflect virtualization 
enhancement in 5.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] #1988 AMF: Admin operation continuation does not work with short cluster init timeout

[Praveen]

Hi Minh,

Ack code review only.

Thanks,
Praveen


---

** [tickets:#1988] AMF: Admin operation continuation does not work with short 
cluster init timeout**

**Status:** review
**Milestone:** 5.1.RC2
**Created:** Wed Aug 31, 2016 12:04 AM UTC by Minh Hon Chau
**Last Updated:** Wed Sep 14, 2016 02:34 AM UTC
**Owner:** Minh Hon Chau


In scenario of admin continuation after headless, if saAmfClusterStartupTimeout 
configures short value, then the admin continuation will initiate when 
saAmfClusterStartupTimeout expires but the SU is still in OUT OF SERVICE. The 
eventual result is failure of admin operation after headless.


---

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] #2049 smf: Delete node group if already exist when creating

[elunlen]

---

** [tickets:#2049] smf: Delete node group if already exist when creating**

**Status:** accepted
**Milestone:** 5.1.RC2
**Created:** Mon Sep 19, 2016 12:52 PM UTC by elunlen
**Last Updated:** Mon Sep 19, 2016 12:52 PM UTC
**Owner:** elunlen


If for some reason a node a node group for admin operation already exist when 
trying to create one the existing node group shall be deleted and a new attempt 
to create the node group shall be done


---

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] #2048 opensaf/doc: no separate branches for 4.7 and 5.0.

[Praveen]

---

** [tickets:#2048] opensaf/doc: no separate branches for 4.7 and 5.0.**

**Status:** unassigned
**Milestone:** 4.7.2
**Created:** Mon Sep 19, 2016 11:43 AM UTC by Praveen
**Last Updated:** Mon Sep 19, 2016 11:43 AM UTC
**Owner:** nobody


It seems there are no separate branches for 4.7 and 5.0 for documentation.
Even they are not listed in closed brnaches.
Here is output of hg commands:
\# hg branch
default
\# hg branches
default  189:e4d420f962d3
\# hg branches -c
default  189:e4d420f962d3
opensaf-4.6.x181:0a4b9b47c55c (closed)
opensaf-4.5.x167:650e49539772 (closed)
opensaf-4.4.x155:81bbe5de2f18 (closed)
opensaf-4.3.x134:ff16f59fe449 (closed)
opensaf-4.2.x 98:b97c89fb2890 (closed)



---

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] #2047 amf: SG unstable when NPI comp in PI SU moves to TERM_FAILED state during fresh assignments.

[Praveen]

- **status**: unassigned --> assigned
- **assigned_to**: Praveen



---

** [tickets:#2047] amf: SG unstable when NPI comp in PI SU moves to TERM_FAILED 
state during fresh assignments.**

**Status:** assigned
**Milestone:** 4.7.2
**Created:** Mon Sep 19, 2016 11:31 AM UTC by Praveen
**Last Updated:** Mon Sep 19, 2016 11:31 AM UTC
**Owner:** Praveen
**Attachments:**

- 
[pinpi_issue.tgz](https://sourceforge.net/p/opensaf/tickets/2047/attachment/pinpi_issue.tgz)
 (21.9 kB; application/x-compressed)


Conf: 2N model, one NPI and one PI comp in SU.
Steps to reproduce:
1)Add application using immcfg command.
2)Lock SG.
3)Unlock-in and unlock SUs.
4)Make provisions so that instantiation and clean up scripts of NPI comp 
returns with non-zero status.
5)Unlock SG.
When SG is unlocked, AMFND initiates active assignments by issuing callback to 
PI comp and by instantiating NPI component. After instantiation failure of NPI 
comp, AMFND tries to clean up it. Cleanup fails. AMFND marks comp and SU in 
TERM_FAILED state and terminates PI comp also, but AMFND neither responds to 
AMFD for the completion of assignment nor it sends any recovery request. 
Because of this SG remains unstable in REALIGN state.In this state, no admin 
operation is allowed.
Attached are traces and configuration.
Even though issue seems to be similar to #538, it is different in one aspect. 
In #538, SU moves to TERM_FAILED state and there is possibiltiy of 
failover/switchover as standby assignments are present.
In the present case, it happened during initial assignments and thus there is 
no standby to switchover/failover to.


---

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] #2047 amf: SG unstable when NPI comp in PI SU moves to TERM_FAILED state during fresh assignments.

[Praveen]

---

** [tickets:#2047] amf: SG unstable when NPI comp in PI SU moves to TERM_FAILED 
state during fresh assignments.**

**Status:** unassigned
**Milestone:** 4.7.2
**Created:** Mon Sep 19, 2016 11:31 AM UTC by Praveen
**Last Updated:** Mon Sep 19, 2016 11:31 AM UTC
**Owner:** nobody
**Attachments:**

- 
[pinpi_issue.tgz](https://sourceforge.net/p/opensaf/tickets/2047/attachment/pinpi_issue.tgz)
 (21.9 kB; application/x-compressed)


Conf: 2N model, one NPI and one PI comp in SU.
Steps to reproduce:
1)Add application using immcfg command.
2)Lock SG.
3)Unlock-in and unlock SUs.
4)Make provisions so that instantiation and clean up scripts of NPI comp 
returns with non-zero status.
5)Unlock SG.
When SG is unlocked, AMFND initiates active assignments by issuing callback to 
PI comp and by instantiating NPI component. After instantiation failure of NPI 
comp, AMFND tries to clean up it. Cleanup fails. AMFND marks comp and SU in 
TERM_FAILED state and terminates PI comp also, but AMFND neither responds to 
AMFD for the completion of assignment nor it sends any recovery request. 
Because of this SG remains unstable in REALIGN state.In this state, no admin 
operation is allowed.
Attached are traces and configuration.
Even though issue seems to be similar to #538, it is different in one aspect. 
In #538, SU moves to TERM_FAILED state and there is possibiltiy of 
failover/switchover as standby assignments are present.
In the present case, it happened during initial assignments and thus there is 
no standby to switchover/failover to.


---

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] #2046 smf: Recreate IMM handles if bad handle when deleting node group

[elunlen]

---

** [tickets:#2046] smf: Recreate IMM handles if bad handle when deleting node 
group**

**Status:** accepted
**Milestone:** 5.1.RC2
**Created:** Mon Sep 19, 2016 11:23 AM UTC by elunlen
**Last Updated:** Mon Sep 19, 2016 11:23 AM UTC
**Owner:** elunlen


When doing an admin operation on AMF a fail may cause the handles that was 
created when the admin operation C++ object was created to be invalid. If that 
happen a node group that was created before the admin operation cannot be 
deleted, will fail with bad handle.
The node group must always be deleted.
The deleteNodeGroup() method must be fixed so that if the delete operation 
fails with bad handles new handles has to be created so that the node group can 
be deleted


---

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] #2044 cpa: saCkptCheckpointSynchronize api is not supporting full range of timeout values

[A V Mahesh (AVM)]

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

changeset:   8092:ff7e1a5a8c1b
branch:  opensaf-4.7.x
parent:  8084:a32ab58f9ade
user:A V Mahesh 
date:Mon Sep 19 14:35:29 2016 +0530
summary: cpa: provide support for full range of timeout for CkptSynchronize 
API [#2044]
 
changeset:   8093:bcd8675c17b3
branch:  opensaf-5.0.x
parent:  8085:47cb9594242b
user:A V Mahesh 
date:Mon Sep 19 14:35:41 2016 +0530
summary: cpa: provide support for full range of timeout for CkptSynchronize 
API [#2044]
 
changeset:   8094:6e6980f88b50
branch:  opensaf-5.1.x
parent:  8090:628fcbb0c110
user:A V Mahesh 
date:Mon Sep 19 14:36:02 2016 +0530
summary: cpa: provide support for full range of timeout for CkptSynchronize 
API [#2044]
 
changeset:   8095:06794cdbd3ee
tag: tip
parent:  8091:95d8784d1d0c
user:A V Mahesh 
date:Mon Sep 19 14:36:42 2016 +0530
summary: cpa: provide support for full range of timeout for CkptSynchronize 
API [#2044]



---

** [tickets:#2044] cpa: saCkptCheckpointSynchronize api is not supporting full 
range of timeout values**

**Status:** fixed
**Milestone:** 4.7.2
**Created:** Mon Sep 19, 2016 05:40 AM UTC by A V Mahesh (AVM)
**Last Updated:** Mon Sep 19, 2016 06:22 AM UTC
**Owner:** A V Mahesh (AVM)


If timeout is provided less than 14 seconds  saCkptCheckpointSynchronize() 
TIMEOUT immediately.

Fix :  remove chek for if (timeout < CPSV_WAIT_TIME) 


---

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] #1997 IMM: immnd fails to update si while bringing up opensaf with 2PBE

[Long HB Nguyen]

- **status**: unassigned --> assigned
- **assigned_to**: Long HB Nguyen



---

** [tickets:#1997] IMM: immnd fails to update si while bringing up opensaf with 
2PBE**

**Status:** assigned
**Milestone:** 5.1.RC2
**Created:** Fri Sep 02, 2016 11:46 AM UTC by Chani Srivastava
**Last Updated:** Wed Sep 14, 2016 02:09 AM UTC
**Owner:** Long HB Nguyen
**Attachments:**

- 
[LogAMF.zip](https://sourceforge.net/p/opensaf/tickets/1997/attachment/LogAMF.zip)
 (432.4 kB; application/zip)


setup:
Version - OpenSAF 5.1.FC : changeset - 7997
4-Node cluster
2PBE enabled

Bring up opensaf on a controller with 2PBE enable. IMMND throwing error
Attachments: syslog, amfd and immnd traces

Sep  2 16:54:13 SLOT1 osafimmpbed: WA Start prepare for ccb: 
10004/4294967300 towards slave PBE returned: '12' from Immsv
Sep  2 16:54:13 SLOT1 osafimmpbed: WA PBE-A failed to prepare PRTA update 
Ccb:10004/4294967300 towards PBE-B
Sep  2 16:54:13 SLOT1 osafimmpbed: NO 2PBE Error (18) in PRTA update 
(ccbId:10004)
**Sep  2 16:54:13 SLOT1 osafimmnd[3632]: WA update of PERSISTENT runtime 
attributes in object 'safSi=NoRed3,safApp=OpenSAF' REVERTED. PBE rc:18
Sep  2 16:54:13 SLOT1 osafamfd[3698]: ER exec: update FAILED 18**
Sep  2 16:54:14 SLOT1 osafimmnd[3632]: NO PBE-OI established on this SC. 
Dumping incrementally to file imm.db

Note- 1. OpenSAF is successfully started
 2. Issue not seen with 1PBE

Once controller is up, amf-state si gives

safSi=SC-2N,safApp=OpenSAF
saAmfSIAdminState=UNLOCKED(1)
saAmfSIAssignmentState=PARTIALLY_ASSIGNED(3)
safSi=NoRed4,safApp=OpenSAF
saAmfSIAdminState=UNLOCKED(1)
saAmfSIAssignmentState=UNASSIGNED(1)
safSi=NoRed1,safApp=OpenSAF
saAmfSIAdminState=UNLOCKED(1)
saAmfSIAssignmentState=FULLY_ASSIGNED(2)
safSi=NoRed2,safApp=OpenSAF
saAmfSIAdminState=UNLOCKED(1)
saAmfSIAssignmentState=UNASSIGNED(1)
safSi=NoRed3,safApp=OpenSAF
saAmfSIAdminState=UNLOCKED(1)
saAmfSIAssignmentState=UNASSIGNED(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] #2022 AMF : amfd asserted for NG lock operation ( quiesced timeout - Nway model))

[Praveen]

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

This fix may be applicable to other branches also, I will check if there are 
some tickets in N-WAY model with same assertion,



---

** [tickets:#2022] AMF : amfd asserted for NG lock operation ( quiesced timeout 
- Nway model))**

**Status:** review
**Milestone:** 5.1.RC2
**Created:** Sat Sep 10, 2016 09:58 AM UTC by Srikanth R
**Last Updated:** Thu Sep 15, 2016 12:33 PM UTC
**Owner:** Praveen
**Attachments:**

- 
[createAppTestApp.sh](https://sourceforge.net/p/opensaf/tickets/2022/attachment/createAppTestApp.sh)
 (15.8 kB; text/x-shellscript)
- 
[messages](https://sourceforge.net/p/opensaf/tickets/2022/attachment/messages) 
(11.2 kB; application/octet-stream)
- 
[osafamfd](https://sourceforge.net/p/opensaf/tickets/2022/attachment/osafamfd) 
(452.8 kB; application/octet-stream)


Environment details
--
OS : Suse 64bit 
Changeset : 7997  ( 5.1.FC)
Setup : 5 nodes ( 2 controllers and 3 payloads with headless feature enabled & 
no PBE )
AMF Application : NPM model with SUs mapped on SC-2,PL-3,PL-4


Summary :
--
AMFD on both controllers asserted, if Nway application failed in CSI SET 
QUIESCED callback in lock operation of node group 


Steps followed & Observed behaviour
--

-> Hosted nway application on PL-3,PL-4 and SC-2 and brought up the 
application. Configuration is attached to the ticket.
-> Created a node group with all the three nodes.
-> Ensured that one of component will not respond to quiesced callback
-> Now performed the lock operation on the node group
-> amfd on both controllers asserted with the following back trace.


0  0x7f66fbc6fb55 in raise () from /lib64/libc.so.6
1  0x7f66fbc71131 in abort () from /lib64/libc.so.6
2  0x7f66fda6816a in __osafassert_fail (__file=0x51214d "su.cc", 
__line=2022, __func=0x513aa0 "dec_curr_stdby_si", __assertion=0x51355f 
"saAmfSUNumCurrStandbySIs > 0") at sysf_def.c:281

3  0x004d68cd in AVD_SU::dec_curr_stdby_si (this=0x7ccf40) at su.cc:2022
4  0x004be804 in avd_susi_update_assignment_counters (susi=0x78c670, 
action=AVSV_SUSI_ACT_DEL, current_ha_state=0, new_ha_state=0) at siass.cc:783
5  0x004be59b in avd_susi_del_send (susi=0x78c670) at siass.cc:714
6  0x004af12e in avd_sg_nway_node_fail_stable (cb=0x751b80, 
su=0x800470, susi=0x0) at sg_nway_fsm.cc:3022
7  0x004b025d in avd_sg_nway_node_fail_sg_realign (cb=0x751b80, 
su=0x800470) at sg_nway_fsm.cc:3493
8  0x004a8042 in SG_NWAY::node_fail (this=0x797c50, cb=0x751b80, 
su=0x800470) at sg_nway_fsm.cc:497
9  0x004b209e in sg_su_failover_func (su=0x800470) at sgproc.cc:525
10 0x004b2d16 in avd_su_oper_state_evh (cb=0x751b80, 
evt=0x7f66f4002940) at sgproc.cc:838
11 0x00450ba9 in process_event (cb_now=0x751b80, evt=0x7f66f4002940) at 
main.cc:768
12 0x004508cd in main_loop () at main.cc:689
13 0x00450e43 in main (argc=2, argv=0x7fff0f81ab18) at main.cc:841







---

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] #2024 Imm doc: updattion of IMMsv PR document for 5.1

[Neelakanta Reddy]

- **status**: accepted --> fixed
- **Comment**:

changeset:   189:e4d420f962d3
tag: tip
user:Neelakanta Reddy
date:Mon Sep 19 12:12:48 2016 +0530
summary: imm: updated IMMsv PR for 5.1 Release[#2024]




---

** [tickets:#2024] Imm doc: updattion of IMMsv PR document for 5.1**

**Status:** fixed
**Milestone:** 5.1.RC2
**Created:** Mon Sep 12, 2016 06:17 AM UTC by Neelakanta Reddy
**Last Updated:** Tue Sep 13, 2016 10:05 AM UTC
**Owner:** Neelakanta Reddy


This defect is to update, IMMsv PR document


---

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] #2045 logd faulted due to 'csiSetcallbackFailed' on STANDBY during role_change in Headless scenario

[Ritu Raj]

---

** [tickets:#2045] logd faulted due to 'csiSetcallbackFailed' on STANDBY during 
role_change in Headless scenario**

**Status:** unassigned
**Milestone:** 4.7.2
**Created:** Mon Sep 19, 2016 06:42 AM UTC by Ritu Raj
**Last Updated:** Mon Sep 19, 2016 06:42 AM UTC
**Owner:** nobody
**Attachments:**

- 
[SC-2.tar.bz2](https://sourceforge.net/p/opensaf/tickets/2045/attachment/SC-2.tar.bz2)
 (14.9 MB; application/x-bzip)
- 
[syslogSC-1](https://sourceforge.net/p/opensaf/tickets/2045/attachment/syslogSC-1)
 (3.8 MB; application/octet-stream)
- 
[syslogSC-2](https://sourceforge.net/p/opensaf/tickets/2045/attachment/syslogSC-2)
 (2.9 MB; application/octet-stream)


# Environment details

OS : Suse 64bit
Changeset : 7997 ( 5.1.FC)
Setup : 6 nodes ( 3 controllers and 3 payloads with headless feature enabled & 
1PBE with 10K objects)

# Summary
NCS_MBCSV_OP_CHG_ROLE FAILED on STANBY controller and logd faulted due to 
'csiSetcallbackFailed'

# Steps followed & Observed behaviour
1. Invoked headless by killing Active followed by Standby and Spare Controller,
maintaining gap of 11 sec between controller reboot
2. After 81 successful failover, during role change from STNADBY to ACTIVE, on  
STANDBY(SC-2) logd faulted due to 'csiSetcallbackFailed' 
[also .. NCS_MBCSV_OP_CHG_ROLE FAILED] 

*Syslog:
Sep 16 22:26:39 SCALE_SLOT-72 osaflogd[1770]: ER ncs_mbcsv_svc 
NCS_MBCSV_OP_CHG_ROLE FAILED
Sep 16 22:26:39 SCALE_SLOT-72 osafamfnd[1810]: NO 
'safComp=LOG,safSu=SC-2,safSg=2N,safApp=OpenSAF' faulted due to 
'csiSetcallbackFailed' : Recovery is 'nodeFailfast'
Sep 16 22:26:39 SCALE_SLOT-72 osafamfnd[1810]: ER 
safComp=LOG,safSu=SC-2,safSg=2N,safApp=OpenSAF Faulted due 
to:csiSetcallbackFailed Recovery is:nodeFailfast
Sep 16 22:26:39 SCALE_SLOT-72 osafamfnd[1810]: Rebooting OpenSAF NodeId = 
131599 EE Name = , Reason: Component faulted: recovery is node failfast, 
OwnNodeId = 131599, SupervisionTime = 60
Sep 16 22:26:39 SCALE_SLOT-72 opensaf_reboot: Rebooting local node; timeout=60
 

*Notes:
1. There is time gap between systems [node's are not sync]
With respect to SC-1 and SC-2, SC-3  is >> +6:24:07
2. Syslog of controller's and  amfd and clmd trace's of SC-2 is attached
3. logd traces are not enabled



---

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] #2043 log: ER no stream exists

[Vu Minh Nguyen]

- Description has changed:

Diff:



--- old
+++ new
@@ -15,7 +15,7 @@
 
 1) Create streamA
 2) Create streamB
-3) Delete streamB
+3) Delete streamA
 4) Reboot active node
 
 We will get following in syslog:






---

** [tickets:#2043] log: ER no stream exists**

**Status:** accepted
**Milestone:** 5.1.RC2
**Created:** Mon Sep 19, 2016 05:20 AM UTC by Vu Minh Nguyen
**Last Updated:** Mon Sep 19, 2016 05:20 AM UTC
**Owner:** Vu Minh Nguyen


Logsv used following code to iterate all existing log streams:

```C
  /* check existing streams */
  num = get_number_of_streams();
  stream = log_stream_get_by_id(--num);
  if (!stream)
LOG_ER("No streams exist!");
  while (stream != NULL) {
stream = log_stream_get_by_id(--num);
  }
```

If we create 02 log streams, then delete them in the following order, above 
code will run incorrectly.

1) Create streamA
2) Create streamB
3) Delete streamA
4) Reboot active node

We will get following in syslog:

> Sep 19 12:08:22 SC-2 local0.err osaflogd[453]: ER No streams exist!



---

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] #2044 cpa: saCkptCheckpointSynchronize api is not supporting full range of timeout values

[A V Mahesh (AVM)]

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



---

** [tickets:#2044] cpa: saCkptCheckpointSynchronize api is not supporting full 
range of timeout values**

**Status:** review
**Milestone:** 4.7.2
**Created:** Mon Sep 19, 2016 05:40 AM UTC by A V Mahesh (AVM)
**Last Updated:** Mon Sep 19, 2016 05:40 AM UTC
**Owner:** A V Mahesh (AVM)


If timeout is provided less than 14 seconds  saCkptCheckpointSynchronize() 
TIMEOUT immediately.

Fix :  remove chek for if (timeout < CPSV_WAIT_TIME) 


---

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