[tickets] [opensaf:tickets] #1190 AMF: saAmfSIPrefActiveAssignments has wrong default, stopping scaling nway active SGs

2014-10-23 Thread Hans Feldt
--- ** [tickets:#1190] AMF: saAmfSIPrefActiveAssignments has wrong default, stopping scaling nway active SGs** **Status:** unassigned **Milestone:** 4.4.2 **Created:** Thu Oct 23, 2014 01:10 PM UTC by Hans Feldt **Last Updated:** Thu Oct 23, 2014 01:10 PM UTC **Owner:** nobody Problem: In

[tickets] [opensaf:tickets] #1190 AMF: saAmfSIPrefActiveAssignments has wrong default, stopping scaling nway active SGs

2014-10-23 Thread Hans Feldt
the schema seems to be wrong since has a default value of 1, should have no default --- ** [tickets:#1190] AMF: saAmfSIPrefActiveAssignments has wrong default, stopping scaling nway active SGs** **Status:** unassigned **Milestone:** 4.4.2 **Created:** Thu Oct 23, 2014 01:10 PM UTC by Hans

[tickets] [opensaf:tickets] #1075 2PBE: pbed aborts at sqlite_prepare_ccb

2014-10-23 Thread Anders Bjornerstedt
- **status**: accepted -- duplicate - **Comment**: This ticket is a duplicate of ticket #1057 already fixed. The problem is that on timeout waiting for This error message: Sep 12 18:01:49 SLES-64BIT-SLOT1 osafimmpbed: ER sqlite_prepare_ccb invoked when no sqlite transaction has been

[tickets] [opensaf:tickets] #1189 imm: admin operation returns ERR_NAME_TOO_LONG for a valid extended name in return parameters

2014-10-23 Thread Zoran Milinkovic
- **status**: accepted -- review - **Comment**: https://sourceforge.net/p/opensaf/mailman/message/32962560/ --- ** [tickets:#1189] imm: admin operation returns ERR_NAME_TOO_LONG for a valid extended name in return parameters** **Status:** review **Milestone:** 4.5.1 **Created:** Thu Oct 23,

[tickets] [opensaf:tickets] #1188 IMM: Sync-retry wait time causes problems

2014-10-23 Thread A V Mahesh (AVM)
To address following the sysnc wait time was changed from 'usleep(15)' to a 'sleep(2)' ( above TIPC link tolerance of 1.5 sec ) while testing TIPC Multicast. When A node sync is in-progress , the sync message are being send in very high number/frequency when Large IMM DB, at that