[tickets] [opensaf:tickets] #2466 AMF: NodeGroup Admin UNLOCK timeout during cluster start up

2017-05-22 Thread Gary Lee
Hi Praveen I guess something like this should work, based on Minh and your comments? amfd: only increment su_cnt_admin_oper for non-opensaf SUs [#2466] diff --git a/src/amf/amfd/sgproc.cc b/src/amf/amfd/sgproc.cc index cd95fe82c..20549808b 100644 --- a/src/amf/amfd/sgproc.cc +++ b/src/amf/amfd/s

[tickets] [opensaf:tickets] #2466 AMF: NodeGroup Admin UNLOCK timeout during cluster start up

2017-05-22 Thread Praveen
Hi Minh, Earlier we used to reject admin operation on AMF entities if cluster is not in AVD_APP_STATE (cluster startup timer not expired). Such a check is not present in check_ng_stability() and thus above admin operation was allowed. Later we enhanced AMF to allow admin operation before cluste

[tickets] [opensaf:tickets] #2466 AMF: NodeGroup Admin UNLOCK timeout during cluster start up

2017-05-22 Thread Praveen
Hi Minh, I will go thorugh it today. Thanks Praveen --- ** [tickets:#2466] AMF: NodeGroup Admin UNLOCK timeout during cluster start up** **Status:** unassigned **Milestone:** 5.17.06 **Created:** Tue May 23, 2017 01:19 AM UTC by Minh Hon Chau **Last Updated:** Tue May 23, 2017 05:13 AM UTC **

[tickets] [opensaf:tickets] #2466 AMF: NodeGroup Admin UNLOCK timeout during cluster start up

2017-05-22 Thread Minh Hon Chau
- Description has changed: Diff: --- old +++ new @@ -89,6 +89,4 @@ } ... - Please NOTE that this problem starts to happen since #2416, in which tries to update IMM sync call. This could be the reason that make NoRed Opensaf SU of PL-3 get assigned late so that nodegroup admi

[tickets] [opensaf:tickets] #2466 AMF: NodeGroup Admin UNLOCK timeout during cluster start up

2017-05-22 Thread Minh Hon Chau
Hi Praveen, Any comments? At second thought, I think it does not relate to #2416 The IMM sync call did time out but took just milisec, it mostly did not cause much latency of Opensaf Saf NoRED of PL3 getting assignment after ng command was issued. PL-3 came late due to timing in starting up node

[tickets] [opensaf:tickets] #2466 AMF: NodeGroup Admin UNLOCK timeout during cluster start up

2017-05-22 Thread Minh Hon Chau
- Description has changed: Diff: --- old +++ new @@ -18,10 +18,10 @@ admin unlock nodegroup issues ~~~ - May 22 14:34:02.989761 osafamfd [11068:11068:../../opensaf/src/amf/amfd/nodegroup.cc:1100] su_cnt_admin_oper >> ng_admin_op_cb: 'safAmfNodeGroup=smfLockAdmNg2,safAmfCluster=myAm

[tickets] [opensaf:tickets] #2466 AMF: NodeGroup Admin UNLOCK timeout during cluster start up

2017-05-22 Thread Minh Hon Chau
Is there something we can do in avd_new_assgn_susi(), that makes AMFD doesn't increase the counter for Opensaf SU, because AMFD doesn't decrease it when Opensaf SU gets assigned ? --- ** [tickets:#2466] AMF: NodeGroup Admin UNLOCK timeout during cluster start up** **Status:** unassigned **Mil

[tickets] [opensaf:tickets] #2466 AMF: NodeGroup Admin UNLOCK timeout during cluster start up

2017-05-22 Thread Minh Hon Chau
--- ** [tickets:#2466] AMF: NodeGroup Admin UNLOCK timeout during cluster start up** **Status:** unassigned **Milestone:** 5.17.06 **Created:** Tue May 23, 2017 01:19 AM UTC by Minh Hon Chau **Last Updated:** Tue May 23, 2017 01:19 AM UTC **Owner:** nobody When cluster is coming up, if a nod

[tickets] [opensaf:tickets] #1286 LOG: String copy without length check or check if string

2017-05-22 Thread Vu Minh Nguyen
- **status**: unassigned --> fixed - **Blocker**: --> False - **Milestone**: future --> 5.1.FC - **Comment**: Fixed in enhacement ticket [#1315] since OpenSAF 5.1 release. --- ** [tickets:#1286] LOG: String copy without length check or check if string** **Status:** fixed **Milestone:** 5.1.F

[tickets] [opensaf:tickets] #1482 log: size of destination buffer is smaller than the size of the source buffer

2017-05-22 Thread Vu Minh Nguyen
- **status**: unassigned --> fixed - **Blocker**: --> False - **Milestone**: future --> 5.1.FC - **Comment**: Fixed in enhacement ticket [#1315] since OpenSAF 5.1 release. --- ** [tickets:#1482] log: size of destination buffer is smaller than the size of the source buffer** **Status:** fixe

[tickets] [opensaf:tickets] #2425 lck: implement saLckLimitGet

2017-05-22 Thread Alex Jones
- **status**: review --> fixed - **Comment**: commit 7277188767bb0fd14fb2c3083f7c3d814280b829 Author: Alex Jones Date: Mon May 22 09:52:26 2017 -0400 --- ** [tickets:#2425] lck: implement saLckLimitGet** **Status:** fixed **Milestone:** 5.17.08 **Created:** Wed Apr 12, 2017 05:04 PM UTC b

[tickets] [opensaf:tickets] #2453 log: process TRY AGAIN in logtest 2 40 and logtest 2 41

2017-05-22 Thread Vu Minh Nguyen
- **status**: review --> fixed - **assigned_to**: Canh Truong --> nobody - **Comment**: [Develop] commit d1a62870d898d12ab1bbda8a459db28eda3d09ea Author: Canh Van Truong Date: Wed May 3 13:50:07 2017 +0200 log: process TRY AGAIN in logtest 2 40 and logtest 2 41 [#2453] [Release] commit