[tickets] [opensaf:tickets] #1110 NTF healthcheck callback timedout leading to node reboot

An analysis and some more info: - Current SC-1 is active, SC-2 is standby. - Power off SC-1 so SC-2 is FAILOVER standby -> active. At this time, NTF service on SC-2 try to terminate the child process osafntfimcnd. But the terminating can not successfully. So NTF service on SC-2 was hang. And afte

Re: [tickets] [opensaf:tickets] #1121 imm access control change at build time didnot reflect in attribute change

Well thats why I changed it to doc. I think the only problem was a missunderstanding, hence possibly a need to clarify the documentation. Either that or this ticket should be closed with 'worksforme' /AndersBj From: Hans Feldt [mailto:hansfe...@users.sf.net] Sen

[tickets] [opensaf:tickets] Re: #1121 imm access control change at build time didnot reflect in attribute change

Well thats why I changed it to doc. I think the only problem was a missunderstanding, hence possibly a need to clarify the documentation. Either that or this ticket should be closed with 'worksforme' /AndersBj From: Hans Feldt [mailto:hansfe...@users.sf.net] Sen

[tickets] [opensaf:tickets] #1121 imm access control change at build time didnot reflect in attribute change

- **status**: unassigned --> review - **Part**: nd --> doc --- ** [tickets:#1121] imm access control change at build time didnot reflect in attribute change** **Status:** review **Milestone:** 4.5.0 **Created:** Mon Sep 22, 2014 07:35 AM UTC by surender khetavath **Last Updated:** Tue Sep 23,

[tickets] [opensaf:tickets] #1121 imm access control change at build time didnot reflect in attribute change

- **status**: review --> fixed - **Comment**: Pushing this although it is a minor defect. No risk with that since it just affects a README file. changeset: 5920:6f1e8bedf52c branch: opensaf-4.5.x user:Hans Feldt date:Tue Sep 23 09:51:31 2014 +0200 summary: imm: descri

[tickets] [opensaf:tickets] #1127 IMM: Detached PBE just before a ccb-apply can cause cluster restart.

--- ** [tickets:#1127] IMM: Detached PBE just before a ccb-apply can cause cluster restart.** **Status:** accepted **Milestone:** 4.3.3 **Created:** Tue Sep 23, 2014 07:58 AM UTC by Anders Bjornerstedt **Last Updated:** Tue Sep 23, 2014 07:58 AM UTC **Owner:** Anders Bjornerstedt This ticket

[tickets] [opensaf:tickets] #1089 immtools: buffer overflow in log_stderr_int in immcfg

- **status**: accepted --> review --- ** [tickets:#1089] immtools: buffer overflow in log_stderr_int in immcfg** **Status:** review **Milestone:** 4.3.3 **Created:** Mon Sep 15, 2014 02:46 PM UTC by Zoran Milinkovic **Last Updated:** Mon Sep 22, 2014 09:29 AM UTC **Owner:** Zoran Milinkovic I

[tickets] [opensaf:tickets] #1128 access control feature is valid across nodes?

--- ** [tickets:#1128] access control feature is valid across nodes?** **Status:** unassigned **Milestone:** 4.3.3 **Created:** Tue Sep 23, 2014 09:03 AM UTC by surender khetavath **Last Updated:** Tue Sep 23, 2014 09:03 AM UTC **Owner:** nobody As per README.ACCESS_CONTROL "" - members of th

[tickets] [opensaf:tickets] #1096 imm: immnd may crash in immnd_evt_proc_ccb_compl_rsp if OI handle is detached

- **status**: review --> fixed - **Comment**: changeset: 5925:2095f27c67ab tag: tip parent: 5921:6832cc532594 user:Anders Bjornerstedt date:Mon Sep 22 16:50:07 2014 +0200 summary: imm: In immnd_evt_proc_ccb_compl_rsp skip to end if PBE-OI is detached [#1096] c

[tickets] [opensaf:tickets] Re: #1128 access control feature is valid across nodes?

My 2 cents: Only on the local node :-). Thanks, Ramesh. On 9/23/2014 2:33 PM, surender khetavath wrote: > > > *[tickets:#1128] > access control feature is valid across nodes?*

[tickets] [opensaf:tickets] #1128 access control feature is valid across nodes?

Probably the document should mention this "ACCESS_CONTROL is between immnd and its native client" --- ** [tickets:#1128] access control feature is valid across nodes?** **Status:** unassigned **Milestone:** 4.3.3 **Created:** Tue Sep 23, 2014 09:03 AM UTC by surender khetavath **Last Updated:*

[tickets] [opensaf:tickets] #1128 access control feature is valid across nodes?

IMM only has local clients and the scope of this enhancement is to secure the API usage (which is always node local). I can update the README (again) --- ** [tickets:#1128] access control feature is valid across nodes?** **Status:** unassigned **Milestone:** 4.3.3 **Created:** Tue Sep 23, 2014

[tickets] [opensaf:tickets] #1036 mds: IMMND restarts because of out of order messages

- **status**: unassigned --> assigned - **assigned_to**: A V Mahesh (AVM) --- ** [tickets:#1036] mds: IMMND restarts because of out of order messages** **Status:** assigned **Milestone:** 4.5.0 **Created:** Tue Sep 02, 2014 01:06 PM UTC by Neelakanta Reddy **Last Updated:** Tue Sep 02, 2014 0

[tickets] [opensaf:tickets] #620 Admin operations needs to be allowed when cluster startup timer is running

- **status**: fixed --> accepted - **Milestone**: 4.5.FC --> 4.6.FC --- ** [tickets:#620] Admin operations needs to be allowed when cluster startup timer is running** **Status:** accepted **Milestone:** 4.6.FC **Created:** Tue Nov 12, 2013 06:46 AM UTC by Sirisha Alla **Last Updated:** Fri Se

[tickets] [opensaf:tickets] #620 Admin operations needs to be allowed when cluster startup timer is running

Somehow, the fix was not pushed. I will it in default for 4.6. Thanks -Nagu --- ** [tickets:#620] Admin operations needs to be allowed when cluster startup timer is running** **Status:** accepted **Milestone:** 4.6.FC **Created:** Tue Nov 12, 2013 06:46 AM UTC by Sirisha Alla **Last Updated:*

Re: [tickets] [opensaf:tickets] #1128 access control feature is valid across nodes?

Hans, if you update the README again I suggest you re-use/re-classify this ticket. /AndersBj From: Hans Feldt [mailto:hansfe...@users.sf.net] Sent: den 23 september 2014 11:58 To: opensaf-tickets@lists.sourceforge.net Subject: [tickets] [opensaf:tickets] #1128 ac

[tickets] [opensaf:tickets] Re: #1128 access control feature is valid across nodes?

Hans, if you update the README again I suggest you re-use/re-classify this ticket. /AndersBj From: Hans Feldt [mailto:hansfe...@users.sf.net] Sent: den 23 september 2014 11:58 To: opensaf-tickets@lists.sourceforge.net Subject: [tickets] [opensaf:tickets] #1128 ac

[tickets] [opensaf:tickets] #1129 LOG: Incorrect syslog if fail to close files when closing log stream

--- ** [tickets:#1129] LOG: Incorrect syslog if fail to close files when closing log stream** **Status:** unassigned **Milestone:** 4.6.FC **Created:** Tue Sep 23, 2014 11:02 AM UTC by elunlen **Last Updated:** Tue Sep 23, 2014 11:02 AM UTC **Owner:** nobody In lgs_stream.c:

[tickets] [opensaf:tickets] #1114 NTF: Unadapted LongDns consumer crashes due to read/subsribe long dn notification

- **status**: assigned --> accepted --- ** [tickets:#1114] NTF: Unadapted LongDns consumer crashes due to read/subsribe long dn notification** **Status:** accepted **Milestone:** 4.5.0 **Created:** Fri Sep 19, 2014 05:15 AM UTC by Minh Hon Chau **Last Updated:** Fri Sep 19, 2014 05:16 AM UTC

[tickets] [opensaf:tickets] #1130 immtools: immcfg is truncating the object names with longdns while loading

--- ** [tickets:#1130] immtools: immcfg is truncating the object names with longdns while loading ** **Status:** unassigned **Milestone:** 4.5.0 **Created:** Tue Sep 23, 2014 11:23 AM UTC by Neelakanta Reddy **Last Updated:** Tue Sep 23, 2014 11:23 AM UTC **Owner:** nobody class:

[tickets] [opensaf:tickets] #742 search criteria should be made optional for ReadInitialize()

- **status**: invalid --> accepted - **Part**: - --> doc - **Milestone**: future --> 4.3.3 - **Comment**: NTF PR doc will be updated with the statement: "Current NTF implementation does not consider searchCriteria as optional parameter in saNtfNotificationReadInitialize() API. The API will retur

[tickets] [opensaf:tickets] #1127 IMM: FAilure to send to completed to PBE can cause cluster restart.

- **summary**: IMM: Detached PBE just before a ccb-apply can cause cluster restart. --> IMM: FAilure to send to completed to PBE can cause cluster restart. - Description has changed: Diff: --- old +++ new @@ -3,12 +3,26 @@ http://sourceforge.net/p/opensaf/tickets/1096/ The PBE detache

[tickets] [opensaf:tickets] #1127 IMM: Failure to send completed to PBE can cause cluster restart.

- **summary**: IMM: FAilure to send to completed to PBE can cause cluster restart. --> IMM: Failure to send completed to PBE can cause cluster restart. - Description has changed: Diff: --- old +++ new @@ -22,7 +22,7 @@ node not found should be changed to an assert. So the problem that

[tickets] [opensaf:tickets] #1131 IMM: duplicate immnd process was observed starting opensaf with PBE.

--- ** [tickets:#1131] IMM: duplicate immnd process was observed starting opensaf with PBE.** **Status:** unassigned **Milestone:** 4.3.3 **Created:** Tue Sep 23, 2014 12:24 PM UTC by Hrishikesh **Last Updated:** Tue Sep 23, 2014 12:24 PM UTC **Owner:** nobody changeset : 5697 Setup : 4 node

[tickets] [opensaf:tickets] #1096 imm: immnd may crash in immnd_evt_proc_ccb_compl_rsp if OI handle is detached

- **Comment**: On cluser inspection of the code this case was "mostly" a false alarm. Coverity reported a potential problem if cl_node was NULL in immnd_evt_proc_ccb_compl_rsp(). The coverity issue needed to be plugged. But an assert would have sufficed. The case cl_node being NULL should be im

[tickets] [opensaf:tickets] #1131 IMM: duplicate immnd process was observed starting opensaf with PBE.

1. The write permission is not given for mounted shared filesystem where PBE resides. 2. immnd forked with PBE process Sep 22 19:33:15.014270 osafimmnd [32038:immnd_proc.c:1506] >> immnd_forkPbe Sep 22 19:33:15.014276 osafimmnd [32038:immnd_proc.c:1519] TR exec-pbe-file-path:/usr/lib64/opensaf/

[tickets] [opensaf:tickets] #1131 IMM: duplicate immnd process was observed starting opensaf with PBE.

Duplicate of #1077 Why are you testing such old version as 5697 of opensaf? RC2 was released yesterday and should be the focus in test. --- ** [tickets:#1131] IMM: duplicate immnd process was observed starting opensaf with PBE.** **Status:** unassigned **Milestone:** 4.3.3 **Created:** Tue Sep

[tickets] [opensaf:tickets] #1131 IMM: duplicate immnd process was observed starting opensaf with PBE.

#1077 was not fixed in 4.3 and 4.4 though --- ** [tickets:#1131] IMM: duplicate immnd process was observed starting opensaf with PBE.** **Status:** unassigned **Milestone:** 4.3.3 **Created:** Tue Sep 23, 2014 12:24 PM UTC by Hrishikesh **Last Updated:** Tue Sep 23, 2014 12:41 PM UTC **Owner:*

[tickets] [opensaf:tickets] #1131 IMM: duplicate immnd process was observed starting opensaf with PBE.

Was the problem resolved ? --- ** [tickets:#1131] IMM: duplicate immnd process was observed starting opensaf with PBE.** **Status:** unassigned **Milestone:** 4.3.3 **Created:** Tue Sep 23, 2014 12:24 PM UTC by Hrishikesh **Last Updated:** Tue Sep 23, 2014 12:42 PM UTC **Owner:** nobody chan

[tickets] [opensaf:tickets] #1131 IMM: duplicate immnd process was observed starting opensaf with PBE.

when the cluster stopped and started again the problem is not seen --- ** [tickets:#1131] IMM: duplicate immnd process was observed starting opensaf with PBE.** **Status:** unassigned **Milestone:** 4.3.3 **Created:** Tue Sep 23, 2014 12:24 PM UTC by Hrishikesh **Last Updated:** Tue Sep 23, 20

[tickets] [opensaf:tickets] #1131 IMM: duplicate immnd process was observed starting opensaf with PBE.

So do we close the ticket or was there a problem with insufficiently clear error indication ? --- ** [tickets:#1131] IMM: duplicate immnd process was observed starting opensaf with PBE.** **Status:** unassigned **Milestone:** 4.3.3 **Created:** Tue Sep 23, 2014 12:24 PM UTC by Hrishikesh **La

[tickets] [opensaf:tickets] #1131 IMM: duplicate immnd process was observed starting opensaf with PBE.

- **status**: unassigned --> duplicate - **Comment**: As Hans, pointed it may be duplicate of #1077. After having the changeset of #1077, still the problem is seen, please re-open the ticket. --- ** [tickets:#1131] IMM: duplicate immnd process was observed starting opensaf with PBE.** **

[tickets] [opensaf:tickets] #1128 access control feature is valid across nodes?

- **Component**: imm --> osaf - **Comment**: This issue is not imm specific. --- ** [tickets:#1128] access control feature is valid across nodes?** **Status:** unassigned **Milestone:** 4.3.3 **Created:** Tue Sep 23, 2014 09:03 AM UTC by surender khetavath **Last Updated:** Tue Sep 23, 2014 0

[tickets] [opensaf:tickets] #1132 opensaf shall support temporary unavailbility of both controllers

--- ** [tickets:#1132] opensaf shall support temporary unavailbility of both controllers** **Status:** unassigned **Milestone:** 4.6.FC **Created:** Tue Sep 23, 2014 01:51 PM UTC by Hans Feldt **Last Updated:** Tue Sep 23, 2014 01:51 PM UTC **Owner:** nobody The opensaf cluster shall survive

[tickets] [opensaf:tickets] #1132 opensaf shall support temporary unavailbility of both controllers

Does this mean UNPLANNED down of both SCs or can we expect some form of planned/controlled shutdown of at least a single remaining SC ? --- ** [tickets:#1132] opensaf shall support temporary unavailbility of both controllers** **Status:** unassigned **Milestone:** 4.6.FC **Created:** Tue Sep

[tickets] [opensaf:tickets] #1132 opensaf shall support temporary unavailbility of both controllers

Quesion-2: Is it acceptable that the immsv is not writable (only readable) during the absence of both SCs ? --- ** [tickets:#1132] opensaf shall support temporary unavailbility of both controllers** **Status:** unassigned **Milestone:** 4.6.FC **Created:** Tue Sep 23, 2014 01:51 PM UTC by Hans

[tickets] [opensaf:tickets] Re: #1132 opensaf shall support temporary unavailbility of both controllers

UNPLANNED --- ** [tickets:#1132] opensaf shall support temporary unavailbility of both controllers** **Status:** unassigned **Milestone:** 4.6.FC **Created:** Tue Sep 23, 2014 01:51 PM UTC by Hans Feldt **Last Updated:** Tue Sep 23, 2014 03:03 PM UTC **Owner:** nobody The opensaf cluster shal

[tickets] [opensaf:tickets] Re: #1132 opensaf shall support temporary unavailbility of both controllers

Most likely that is acceptable. IMM is already not writeable in certain situations today. This would not be different from a usage perspective. I guess what could be different is what happens when the service recovers. But that we need to look at per service. --- ** [tickets:#1132] opensaf sh

[tickets] [opensaf:tickets] #1114 NTF: Unadapted LongDns consumer crashes due to read/subsribe long dn notification

The following NTF APIs need to add the protection for unadapted producer/consumer against the notification containing any extended SaNameT, which hereby is known as long DN notification: 1 - saNtfNotificationSend returns SA_AIS_ERR_INVALID_PARAM if one of the following statements is true: .

[tickets] [opensaf:tickets] #1069 NTF: Incorrect or no validation of ntfsend option attributes

- **status**: review --> fixed - **Comment**: changeset: 5926:72def88cf2f8 branch: opensaf-4.3.x parent: 5922:2354e041b9c9 user:praveen.malv...@oracle.com date:Wed Sep 24 09:39:43 2014 +0530 summary: tools/safntf : validate ntfsend options V3 [#1069] changeset: 5

[tickets] [opensaf:tickets] #1114 NTF: Unadapted LongDns consumer crashes due to read/subsribe long dn notification

thresholdInformation has thresholdValue, thresholdHysteresis, observedValue as SaNtfValueT According to https://www.itu.int/rec/T-REC-X.733/en, it's not the case that thresholdInformation will use SA_NTF_VALUE_LDAP_NAME. --- ** [tickets:#1114] NTF: Unadapted LongDns consumer crashes due to r

[tickets] [opensaf:tickets] #1112 mds: immnd crashes and massive fevs duplicate messages seen

- **status**: unassigned --> fixed - **assigned_to**: A V Mahesh (AVM) - **Comment**: 1) I am not able to Reproduce the problem with TIPC 2.0 Suse 2) The fevs duplicates symptom is appears to be due to a bug in TIPC. Fixed by this TIPC patch: https://git.kernel.org/cgit/linux/kernel/git/davem/

[tickets] [opensaf:tickets] #742 search criteria should be made optional for ReadInitialize()

- **status**: accepted --> review --- ** [tickets:#742] search criteria should be made optional for ReadInitialize()** **Status:** review **Milestone:** 4.3.3 **Created:** Thu Jan 23, 2014 10:39 AM UTC by Sirisha Alla **Last Updated:** Tue Sep 23, 2014 11:37 AM UTC **Owner:** Praveen Since se

[tickets] [opensaf:tickets] #742 search criteria should be made optional for ReadInitialize()

In NTFsv PR doc, section 2.2.3 "Implementation Notes" will be updated with the statement: "Current NTF implementation does not consider searchCriteria as optional parameter in saNtfNotificationReadInitialize() API. The API will return SA_AIS_ERR_INVALID_PARAM if searchCriteria is passed incorre

[tickets] [opensaf:tickets] #863 payload middleware su is not instantiated as part of unlock-in/unlock

- **status**: fixed --> unassigned - **Comment**: Followed the above reproducible steps. After doing stop and start on PL-4 and unlock-in and UNlock on PL-4 Su, still pl-4 Su is in DISABLED and UNINSTANTIATED state. safSu=PL-4,safSg=NoRed,safApp=OpenSAF saAmfSUAdminState=UNLOCKED(1)