[tickets] [opensaf:tickets] #2648 smf: smfd crashes after cluster reboot when campaign is in ExecutionCompleted

2017-10-19 Thread Alex Jones via Opensaf-tickets
I completely agree with using rollback and a backup. We do this. And we have 
the system setup such that if a cluster reboot takes place before commit, the 
old version of software is used.

This ticket really addresses a corner case. We have a customer that did an 
upgrade, forgot to commit, and then the chassis rebooted. This caused an 
infinite reboot cycle. The only way we can get out of it, is to remove the 
imm.db files.


---

** [tickets:#2648] smf: smfd crashes after cluster reboot when campaign is in 
ExecutionCompleted**

**Status:** review
**Milestone:** 5.17.10
**Created:** Thu Oct 19, 2017 06:45 PM UTC by Alex Jones
**Last Updated:** Thu Oct 19, 2017 07:21 PM UTC
**Owner:** Alex Jones


smfd crashes in updateImmAttr because it returns NO_RESOURCES. Here is how to 
reproduce:

1. enable PBE, and make sure the "disable" flag is set in OpenSafSmfConfig
2. execute an upgrade campaign, and let it go to "execution completed", but 
don't commit it
3. reboot the entire cluster
4. only allow 1 system controller to come up
5. smfd will attempt to re-execute the campaign
6. any writes to IMM (like setting an error because the campaign file can't be 
found) will fail with NO_RESOURCES and smfd will assert and crash

The reason for the assert and crash is because PBE has not been turned off by 
smfd before the campaign has been inititialized.


---

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] #2631 amfd: Handle unavailability of CLM API

2017-10-19 Thread Minh Hon Chau via Opensaf-tickets
- **status**: assigned --> review



---

** [tickets:#2631] amfd: Handle unavailability of CLM API**

**Status:** review
**Milestone:** 5.17.10
**Created:** Tue Oct 17, 2017 03:35 AM UTC by Minh Hon Chau
**Last Updated:** Tue Oct 17, 2017 03:35 AM UTC
**Owner:** Minh Hon Chau


CLM start/stop tracking APIs may return TIMEOUT or TRYAGAIN, AMFD shall have a 
mechanism to retry the calls. This ticket makes CLM APIs calls encapsulated in 
a job which is similar to NTF/IMM calls


---

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] #2648 smf: smfd crashes after cluster reboot when campaign is in ExecutionCompleted

2017-10-19 Thread Alex Jones via Opensaf-tickets
- **status**: accepted --> review



---

** [tickets:#2648] smf: smfd crashes after cluster reboot when campaign is in 
ExecutionCompleted**

**Status:** review
**Milestone:** 5.17.10
**Created:** Thu Oct 19, 2017 06:45 PM UTC by Alex Jones
**Last Updated:** Thu Oct 19, 2017 07:01 PM UTC
**Owner:** Alex Jones


smfd crashes in updateImmAttr because it returns NO_RESOURCES. Here is how to 
reproduce:

1. enable PBE, and make sure the "disable" flag is set in OpenSafSmfConfig
2. execute an upgrade campaign, and let it go to "execution completed", but 
don't commit it
3. reboot the entire cluster
4. only allow 1 system controller to come up
5. smfd will attempt to re-execute the campaign
6. any writes to IMM (like setting an error because the campaign file can't be 
found) will fail with NO_RESOURCES and smfd will assert and crash

The reason for the assert and crash is because PBE has not been turned off by 
smfd before the campaign has been inititialized.


---

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] #2648 smf: smfd crashes after cluster reboot when campaign is in ExecutionCompleted

2017-10-19 Thread Alex Jones via Opensaf-tickets
I think moving restorePbe from executeWrapup to commit is the right thing to do 
to solve this issue. That way when the cluster is rebooted, and smfd starts up 
again after the reboot, the campaign will be in init state, and nothing will be 
executed.

I think, conceptually, it also makes sense to not write everything to PBE until 
commit time. Then you can use a cluster reboot like a fallback.


---

** [tickets:#2648] smf: smfd crashes after cluster reboot when campaign is in 
ExecutionCompleted**

**Status:** accepted
**Milestone:** 5.17.10
**Created:** Thu Oct 19, 2017 06:45 PM UTC by Alex Jones
**Last Updated:** Thu Oct 19, 2017 06:45 PM UTC
**Owner:** Alex Jones


smfd crashes in updateImmAttr because it returns NO_RESOURCES. Here is how to 
reproduce:

1. enable PBE, and make sure the "disable" flag is set in OpenSafSmfConfig
2. execute an upgrade campaign, and let it go to "execution completed", but 
don't commit it
3. reboot the entire cluster
4. only allow 1 system controller to come up
5. smfd will attempt to re-execute the campaign
6. any writes to IMM (like setting an error because the campaign file can't be 
found) will fail with NO_RESOURCES and smfd will assert and crash

The reason for the assert and crash is because PBE has not been turned off by 
smfd before the campaign has been inititialized.


---

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] #2647 ntfd: ntfimcnd crashed on handling for Object creation callback

2017-10-19 Thread Srinivas Siva Mangipudy via Opensaf-tickets
- Description has changed:

Diff:



--- old
+++ new
@@ -3,7 +3,7 @@
 2. Analysis 
= =
 A huge number of objects, about 200k objects, were created in IMM with PBE 
disabled. Then these objects were deleted in one CCB (by deleting the root 
object). After deleting the objects, the classes were also removed. Then the 
crash happened.
 
-Oct 19 19:45:04 SC-2-1 osafimmnd[22799]: NO Number of objects in IMM is:10 
Oct 19 19:47:00 SC-2-1 osafimmnd[22799]: NO Number of objects in IMM is:20 
Oct 19 19:47:00 SC-2-1 osafimmnd[22799]: NO Ccb 217 COMMITTED (immcfg_SC-2- 
1_27933) Oct 19 19:47:01 SC-2-1 osafimmnd[22799]: WA Busy in HUGE admin owner 
release 5 Oct 19 19:47:01 SC-2-1 osafimmnd[22799]: WA Busy in HUGE admin 
owner release 10 Oct 19 19:47:01 SC-2-1 osafimmnd[22799]: WA Busy in HUGE 
admin owner release 15 Oct 19 19:47:01 SC-2-1 osafimmnd[22799]: WA Busy in 
HUGE admin owner release 20 Oct 19 19:47:25 SC-2-1 osafimmnd[22799]: NO Ccb 
218 COMMITTED (immcfg_SC-2- 1_28075) Oct 19 19:47:25 SC-2-1 
osafntfimcnd[27468]: ER saImmOmClassDescriptionGet_2 failed  
SA_AIS_ERR_NOT_EXIST (12) Oct 19 19:47:25 SC-2-1 osafntfimcnd[27468]:  
../../../../../../../opensaf/osaf/services/saf/ntfsv/ntfimcnd/ntfimcn_imm.c:167:
 get_rdn_attr_name:  Assertion '0' failed. 
+ 
../../../../../../../opensaf/osaf/services/saf/ntfsv/ntfimcnd/ntfimcn_imm.c:167:
 get_rdn_attr_name:  Assertion '0' failed. 
 
 When NTFimcnd created notifications, some information had to be looked up in 
IMM.  
 NTFimcnd only asked for class information in case of object creation: 
@@ -13,9 +13,6 @@
 
 In this case, NTF was still handling notifications for a big number of created 
objects.  Usually,  NTFimcnd cached the class information.  But because these 
objects belong to many classes, it had to ask IMM for class information. But  
the class was already removed in IMM.  IMM was much faster to create and delete 
the objects and class (with PBE disabled), while NTF  was still processing the 
objects, so the information was not there in IMM anymore, and the  crashed 
happened.
 
-Oct 19 19:47:25.344370 osafntfimcnd  
[27468:../../../../../../../opensaf/osaf/libs/agents/saf/imma/imma_proc.c:2333] 
TR Ccb-object- create callback Oct 19 19:47:25.344381 osafntfimcnd  
[27468:../../../../../../../opensaf/osaf/libs/agents/saf/imma/imma_proc.c:2436] 
TR ccb-object-create  make the callback Oct 19 19:47:25.344385 osafntfimcnd  
[27468:../../../../../../../opensaf/osaf/services/saf/ntfsv/ntfimcnd/ntfimcn_imm.c:0426]
 >>  saImmOiCcbObjectCreateCallback Oct 19 19:47:25.344389 osafntfimcnd  
[27468:../../../../../../../opensaf/osaf/services/saf/ntfsv/ntfimcnd/ntfimcn_imm.c:0194]
 >>  get_created_dn Oct 19 19:47:25.344392 osafntfimcnd  
[27468:../../../../../../../opensaf/osaf/services/saf/ntfsv/ntfimcnd/ntfimcn_imm.c:0105]
 >>  get_rdn_attr_name Oct 19 19:47:25.344398 osafntfimcnd  
[27468:../../../../../../../opensaf/osaf/libs/agents/saf/imma/imma_om_api.c:4987]
 >>  saImmOmClassDescriptionGet_2 Oct 19 19:47:25.344402 osafntfimcnd  
[27468:../../../../../../../opensaf/osaf/libs/agents/saf/imma/imma_om_api.c:4996]
 >>  saImmOmClassDescriptionGet_2 Oct 19 19:47:25.344407 osafntfimcnd  
[27468:../../../../../../../opensaf/osaf/libs/agents/saf/imma/imma_om_api.c:5066]
 TR ClassName:  TestCCB1 Oct 19 19:47:25.344411 osafntfimcnd  
[27468:../../../../../../../opensaf/osaf/libs/agents/saf/imma/imma_om_api.c:5083]
 TR  ClassDescrGet 3 Oct 19 19:47:25.344578 osafntfimcnd  
[27468:../../../../../../../opensaf/osaf/libs/agents/saf/imma/imma_om_api.c:5121]
 TR Alloc attrdefs  array:0x1933650 Oct 19 19:47:25.344594 osafntfimcnd  
[27468:../../../../../../../opensaf/osaf/libs/agents/saf/imma/imma_om_api.c:5327]
 <<  saImmOmClassDescriptionGet_2 Oct 19 19:47:25.344619 osafntfimcnd  
[27468:../../../../../../../opensaf/osaf/libs/agents/saf/imma/imma_om_api.c:5335]
 >>  saImmOmClassDescriptionMemoryFree_2 
-Oct 19 19:47:25.344625 osafntfimcnd  
[27468:../../../../../../../opensaf/osaf/libs/agents/saf/imma/imma_om_api.c:5379]
 <<  saImmOmClassDescriptionMemoryFree_2 Oct 19 19:47:25.344628 osafntfimcnd  
[27468:../../../../../../../opensaf/osaf/services/saf/ntfsv/ntfimcnd/ntfimcn_imm.c:0164]
 <<  get_rdn_attr_name Oct 19 19:47:25.344633 osafntfimcnd  
[27468:../../../../../../../opensaf/osaf/services/saf/ntfsv/ntfimcnd/ntfimcn_imm.c:0228]
 <<  get_created_dn Oct 19 19:47:25.344639 osafntfimcnd  
[27468:../../../../../../../opensaf/osaf/services/saf/ntfsv/ntfimcnd/ntfimcn_imm.c:0473]
 <<  saImmOiCcbObjectCreateCallback Oct 19 19:47:25.344643 osafntfimcnd  
[27468:../../../../../../../opensaf/osaf/libs/agents/saf/imma/imma_proc.c:2496] 
TR ccb-object-create  callback returned RC:1 Oct 19 19:47:25.344648 
osafntfimcnd  
[27468:../../../../../../../opensaf/osaf/libs/agents/saf/imma/imma_proc.c:3171] 
<<  imma_process_callback_info Oct 19 19:47:25.344653 osafntfimcnd  

[tickets] [opensaf:tickets] #2648 smf: smfd crashes after cluster reboot when campaign is in ExecutionCompleted

2017-10-19 Thread Alex Jones via Opensaf-tickets



---

** [tickets:#2648] smf: smfd crashes after cluster reboot when campaign is in 
ExecutionCompleted**

**Status:** accepted
**Milestone:** 5.17.10
**Created:** Thu Oct 19, 2017 06:45 PM UTC by Alex Jones
**Last Updated:** Thu Oct 19, 2017 06:45 PM UTC
**Owner:** Alex Jones


smfd crashes in updateImmAttr because it returns NO_RESOURCES. Here is how to 
reproduce:

1. enable PBE, and make sure the "disable" flag is set in OpenSafSmfConfig
2. execute an upgrade campaign, and let it go to "execution completed", but 
don't commit it
3. reboot the entire cluster
4. only allow 1 system controller to come up
5. smfd will attempt to re-execute the campaign
6. any writes to IMM (like setting an error because the campaign file can't be 
found) will fail with NO_RESOURCES and smfd will assert and crash

The reason for the assert and crash is because PBE has not been turned off by 
smfd before the campaign has been inititialized.


---

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] #2441 smf: coredump and syslog flood after immnd crash

2017-10-19 Thread elunlen via Opensaf-tickets
- **status**: review --> fixed
- **assigned_to**: elunlen -->  nobody 
- **Comment**:

commit 1c58a2106a55ad212a8e296424b1f20508eeb9cd
Author: Lennart Lund 
Date:   Thu Oct 19 15:17:27 2017 +0200

smf: coredump and syslog flood after immnd crash [#2441]

When reinitializing the OI handle, done in a separate thread, then keep the
new handle in a local variable until the whole OI including OI set is done
When finished the new handle can be published in the global cb structure.
Also protect global variable change with imm lock mutex




---

** [tickets:#2441] smf: coredump and syslog flood after immnd crash**

**Status:** fixed
**Milestone:** 5.17.10
**Created:** Thu Apr 27, 2017 09:05 AM UTC by Rafael Odzakow
**Last Updated:** Wed Oct 18, 2017 01:41 PM UTC
**Owner:** nobody


Seen in opensaf version: 183d7c379a8f
short ID: 8190

SMF shall handle the return code ERR_BAD_HANDLE in a better way probably by 
reinitializing and creating a new handle. ERR_BAD_HANDLE can happen when IMMND 
crashes and is still reinitializing.


These lines are flooding the system and trace log:
~~~
5:09:43.862034 osafsmfd 
[27207:../../../../../../../opensaf/osaf/services/saf/smfsv/smfd/smfd_main.c:0107]
 WA Lock failed eith EBUSY pthread_mutex_trylock for imm 16
5:09:43.862042 osafsmfd 
[27207:../../../../../../../opensaf/osaf/services/saf/smfsv/smfd/smfd_main.c:0101]
 >> smfd_imm_trylock
~~~


SMF backtrace

~~~
### BT FULL ###
#0 0x7f04a27e50c7 in raise () from /lib64/libc.so.6
No symbol table info available.
#1 0x7f04a27e6478 in abort () from /lib64/libc.so.6
No symbol table info available.
#2 0x7f04a4d1afee in __osafassert_fail (__file=, 
__line=, __func=, __assertion=) at 
../../../../../../opensaf/osaf/libs/core/leap/sysf_def.c:281
No locals.
#3 0x00411f8f in updateImmAttr (dn=, 
attributeName=0x47db5b "saSmfCmpgElapsedTime", 
attrValueType=SA_IMM_ATTR_SATIMET, value=0x1d89cb8) at 
../../../../../../../opensaf/osaf/services/saf/smfsv/smfd/smfd_campaign_oi.cc:773
rc = SA_AIS_ERR_BAD_OPERATION
__FUNCTION__ = "updateImmAttr"
#4 0x0040f129 in SmfCampaign::updateElapsedTime 
(this=this@entry=0x1d89c90) at 
../../../../../../../opensaf/osaf/services/saf/smfsv/smfd/SmfCampaign.cc:930
updateTime = 
diffTime = 
timeStamp = {
tv_sec = 1490843664,
tv_usec = 109102
}
#5 0x0040f169 in SmfCampaign::stopElapsedTime (this=0x1d89c90) at 
../../../../../../../opensaf/osaf/services/saf/smfsv/smfd/SmfCampaign.cc:958
No locals.
#6 0x00440bee in SmfCampState::changeState 
(this=this@entry=0x7f048c014b70, i_camp=i_camp@entry=0x7f048c001220, 
i_state=0x7f048c00d3d0) at 
../../../../../../../opensaf/osaf/services/saf/smfsv/smfd/SmfCampState.cc:224
__FUNCTION__ = "changeState"
newState = {
static npos = ,
_M_dataplus = {
 = {
<__gnu_cxx::new_allocator> = {}, },
members of std::basic_string::_Alloc_hider:
_M_p = 0x7f048c12ae48 "SmfCampStateExecFailed"
}
}
oldState = {
static npos = ,
_M_dataplus = {
 = {
<__gnu_cxx::new_allocator> = {}, },
members of std::basic_string::_Alloc_hider:
_M_p = 0x7f048c02f108 "SmfCampStateExecuting"
}
}
#7 0x00443faa in SmfCampStateExecuting::procResult 
(this=0x7f048c014b70, i_camp=0x7f048c001220, i_procedure=, 
i_result=) at 
../../../../../../../opensaf/osaf/services/saf/smfsv/smfd/SmfCampState.cc:947
error = {
static npos = ,
_M_dataplus = {
 = {
<__gnu_cxx::new_allocator> = {}, },
members of std::basic_string::_Alloc_hider:
_M_p = 0x7f048c010f48 "Procedure safSmfProc=SingleStep_upgrade_SCs failed"
}
}
__FUNCTION__ = "procResult"
result = 
#8 0x0042500a in SmfUpgradeCampaign::procResult (this=0x7f048c001220, 
i_procedure=0x7f048c10afe0, i_result=SMF_PROC_FAILED) at 
../../../../../../../opensaf/osaf/services/saf/smfsv/smfd/SmfUpgradeCampaign.cc:955
__FUNCTION__ = "procResult"
campResult = 
#9 0x0040cdb1 in SmfCampaignThread::processEvt (this=0x1d8d310) at 
../../../../../../../opensaf/osaf/services/saf/smfsv/smfd/SmfCampaignThread.cc:653
evt = 0x7f0490001b40
#10 0x0040cf48 in SmfCampaignThread::handleEvents 
(this=this@entry=0x1d8d310) at 
../../../../../../../opensaf/osaf/services/saf/smfsv/smfd/SmfCampaignThread.cc:699
ret = 
__FUNCTION__ = "handleEvents"
fds = {{
fd = 25,
events = 1,
revents = 1
}}
#11 0x00408253 in SmfCampaignThread::main (this=this@entry=0x1d8d310) 
at 
../../../../../../../opensaf/osaf/services/saf/smfsv/smfd/SmfCampaignThread.cc:760
__FUNCTION__ = "main"
#12 0x00408352 in SmfCampaignThread::main (info=0x1d8d310) at 
../../../../../../../opensaf/osaf/services/saf/smfsv/smfd/SmfCampaignThread.cc:109
__FUNCTION__ = "main"
self = 0x1d8d310
#13 0x7f04a3a110a4 in start_thread () from /lib64/libpthread.so.0
No symbol table info available.
#14 0x7f04a289502d in clone () from 

[tickets] [opensaf:tickets] #2647 ntfd: ntfimcnd crashed on handling for Object creation callback

2017-10-19 Thread Srinivas Siva Mangipudy via Opensaf-tickets
- Description has changed:

Diff:



--- old
+++ new
@@ -1,4 +1,21 @@
-1. Problem 
= = 
NTFimcnd crashed while 200k objects was created and the deleted in IMM, the 
classes  associated with these objects were also removed. 2. Analysis 
= = A 
huge number of objects, about 200k objects, were created in IMM with PBE 
disabled. Then these objects were deleted in one CCB (by deleting the root 
object). After deleting the objects, the classes were also removed. Then the 
crash happened. Oct 19 19:45:04 SC-2-1 osafimmnd[22799]: NO Number of objects 
in IMM is:10 Oct 19 19:47:00 SC-2-1 osafimmnd[22799]: NO Number of objects 
in IMM is:20 Oct 19 19:47:00 SC-2-1 osafimmnd[22799]: NO Ccb 217 COMMITTED 
(immcfg_SC-2- 1_27933) Oct 19 19:47:01 SC-2-1 osafimmnd[22799]: WA Busy in HUGE 
admin owner release 5 Oct 19 19:47:01 SC-2-1 osafimmnd[22799]: WA Busy in 
HUGE admin owner release 10 Oct 19 19:47:01 SC-2-1 osafimmnd[22799]: WA 
Busy in HUGE admin owner release 15 Oct 19 19:47:01 SC-2-1 
osafimmnd[22799]: WA Busy in HUGE admin owner release 20 Oct 19 19:47:25 
SC-2-1 osafimmnd[22799]: NO Ccb 218 COMMITTED (immcfg_SC-2- 1_28075) Oct 19 
19:47:25 SC-2-1 osafntfimcnd[27468]: ER saImmOmClassDescriptionGet_2 failed  
SA_AIS_ERR_NOT_EXIST (12) Oct 19 19:47:25 SC-2-1 osafntfimcnd[27468]:  
../../../../../../../opensaf/osaf/services/saf/ntfsv/ntfimcnd/ntfimcn_imm.c:167:
 get_rdn_attr_name:  Assertion '0' failed. When NTFimcnd created notifications, 
some information had to be looked up in IMM.  NTFimcnd only asked for class 
information in case of object creation: static SaAisErrorT 
saImmOiCcbObjectCreateCallback(SaImmOiHandleT immOiHandle,  
  SaImmOiCcbIdT ccbId,  
  const SaImmClassNameT className,  
  const SaNameT *parentName, const SaImmAttrValuesT_2 **attr) { … 
dn_ptr = get_created_dn(className, parentName, attr); … } static void 
saImmOiCcbApplyCallback(SaImmOiHandleT immOiHandle, SaImmOiCcbIdT ccbId) {  
   … switch 
(ccbUtilOperationData->operationType) { case CCBUTIL_CREATE:
 rdn_attr_name = get_rdn_attr_name( 
ccbUtilOperationData- >param.create.className); 
-internal_rc = ntfimcn_send_object_create_notification( 
ccbUtilOperationData, rdn_attr_name,
 ccbLast); … } In this case, NTF was still 
handling notifications for a big number of created objects.  Usually,  NTFimcnd 
cached the class information.  But because these objects belong to many 
classes, it had to ask IMM for class information. But  the class was already 
removed in IMM.  IMM was much faster to create and delete the objects and class 
(with PBE disabled), while NTF  was still processing the objects, so the 
information was not there in IMM anymore, and the  crashed happened. Oct 19 
19:47:25.344370 osafntfimcnd  
[27468:../../../../../../../opensaf/osaf/libs/agents/saf/imma/imma_proc.c:2333] 
TR Ccb-object- create callback Oct 19 19:47:25.344381 osafntfimcnd  
[27468:../../../../../../../opensaf/osaf/libs/agents/saf/imma/imma_proc.c:2436] 
TR ccb-object-create  make the callback Oct 19 19:47:25.344385 osafntfimcnd  
[27468:../../../../../../../opensaf/osaf/services/saf/ntfsv/ntfimcnd/ntfimcn_imm.c:0426]
 >>  saImmOiCcbObjectCreateCallback Oct 19 19:47:25.344389 osafntfimcnd  
[27468:../../../../../../../opensaf/osaf/services/saf/ntfsv/ntfimcnd/ntfimcn_imm.c:0194]
 >>  get_created_dn Oct 19 19:47:25.344392 osafntfimcnd  
[27468:../../../../../../../opensaf/osaf/services/saf/ntfsv/ntfimcnd/ntfimcn_imm.c:0105]
 >>  get_rdn_attr_name Oct 19 19:47:25.344398 osafntfimcnd  
[27468:../../../../../../../opensaf/osaf/libs/agents/saf/imma/imma_om_api.c:4987]
 >>  saImmOmClassDescriptionGet_2 Oct 19 19:47:25.344402 osafntfimcnd  
[27468:../../../../../../../opensaf/osaf/libs/agents/saf/imma/imma_om_api.c:4996]
 >>  saImmOmClassDescriptionGet_2 Oct 19 19:47:25.344407 osafntfimcnd  
[27468:../../../../../../../opensaf/osaf/libs/agents/saf/imma/imma_om_api.c:5066]
 TR ClassName:  TestCCB1 Oct 19 19:47:25.344411 osafntfimcnd  
[27468:../../../../../../../opensaf/osaf/libs/agents/saf/imma/imma_om_api.c:5083]
 TR  ClassDescrGet 3 Oct 19 19:47:25.344578 osafntfimcnd  
[27468:../../../../../../../opensaf/osaf/libs/agents/saf/imma/imma_om_api.c:5121]
 TR Alloc attrdefs  array:0x1933650 Oct 19 19:47:25.344594 osafntfimcnd  
[27468:../../../../../../../opensaf/osaf/libs/agents/saf/imma/imma_om_api.c:5327]
 <<  saImmOmClassDescriptionGet_2 Oct 19 19:47:25.344619 osafntfimcnd  

[tickets] [opensaf:tickets] #2647 ntfd: ntfimcnd crashed on handling for Object creation callback

2017-10-19 Thread Srinivas Siva Mangipudy via Opensaf-tickets



---

** [tickets:#2647] ntfd: ntfimcnd crashed on handling for Object creation 
callback**

**Status:** unassigned
**Milestone:** 5.17.10
**Created:** Thu Oct 19, 2017 12:45 PM UTC by Srinivas Siva Mangipudy
**Last Updated:** Thu Oct 19, 2017 12:45 PM UTC
**Owner:** nobody


1. Problem 
= = 
NTFimcnd crashed while 200k objects was created and the deleted in IMM, the 
classes  associated with these objects were also removed. 2. Analysis 
= = A 
huge number of objects, about 200k objects, were created in IMM with PBE 
disabled. Then these objects were deleted in one CCB (by deleting the root 
object). After deleting the objects, the classes were also removed. Then the 
crash happened. Oct 19 19:45:04 SC-2-1 osafimmnd[22799]: NO Number of objects 
in IMM is:10 Oct 19 19:47:00 SC-2-1 osafimmnd[22799]: NO Number of objects 
in IMM is:20 Oct 19 19:47:00 SC-2-1 osafimmnd[22799]: NO Ccb 217 COMMITTED 
(immcfg_SC-2- 1_27933) Oct 19 19:47:01 SC-2-1 osafimmnd[22799]: WA Busy in HUGE 
admin owner release 5 Oct 19 19:47:01 SC-2-1 osafimmnd[22799]: WA Busy in 
HUGE admin owner release 10 Oct 19 19:47:01 SC-2-1 osafimmnd[22799]: WA 
Busy in HUGE admin owner release 15 Oct 19 19:47:01 SC-2-1 
osafimmnd[22799]: WA Busy in HUGE admin owner release 20 Oct 19 19:47:25 
SC-2-1 osafimmnd[22799]: NO Ccb 218 COMMITTED (immcfg_SC-2- 1_28075) Oct 19 
19:47:25 SC-2-1 osafntfimcnd[27468]: ER saImmOmClassDescriptionGet_2 failed  
SA_AIS_ERR_NOT_EXIST (12) Oct 19 19:47:25 SC-2-1 osafntfimcnd[27468]:  
../../../../../../../opensaf/osaf/services/saf/ntfsv/ntfimcnd/ntfimcn_imm.c:167:
 get_rdn_attr_name:  Assertion '0' failed. When NTFimcnd created notifications, 
some information had to be looked up in IMM.  NTFimcnd only asked for class 
information in case of object creation: static SaAisErrorT 
saImmOiCcbObjectCreateCallback(SaImmOiHandleT immOiHandle,  
  SaImmOiCcbIdT ccbId,  
  const SaImmClassNameT className,  
  const SaNameT *parentName, const SaImmAttrValuesT_2 **attr) { … 
dn_ptr = get_created_dn(className, parentName, attr); … } static void 
saImmOiCcbApplyCallback(SaImmOiHandleT immOiHandle, SaImmOiCcbIdT ccbId) {  
   … switch 
(ccbUtilOperationData->operationType) { case CCBUTIL_CREATE:
 rdn_attr_name = get_rdn_attr_name( 
ccbUtilOperationData- >param.create.className); 
internal_rc = ntfimcn_send_object_create_notification(  
   ccbUtilOperationData, rdn_attr_name, 
ccbLast); … } In this case, NTF was still 
handling notifications for a big number of created objects.  Usually,  NTFimcnd 
cached the class information.  But because these objects belong to many 
classes, it had to ask IMM for class information. But  the class was already 
removed in IMM.  IMM was much faster to create and delete the objects and class 
(with PBE disabled), while NTF  was still processing the objects, so the 
information was not there in IMM anymore, and the  crashed happened. Oct 19 
19:47:25.344370 osafntfimcnd  
[27468:../../../../../../../opensaf/osaf/libs/agents/saf/imma/imma_proc.c:2333] 
TR Ccb-object- create callback Oct 19 19:47:25.344381 osafntfimcnd  
[27468:../../../../../../../opensaf/osaf/libs/agents/saf/imma/imma_proc.c:2436] 
TR ccb-object-create  make the callback Oct 19 19:47:25.344385 osafntfimcnd  
[27468:../../../../../../../opensaf/osaf/services/saf/ntfsv/ntfimcnd/ntfimcn_imm.c:0426]
 >>  saImmOiCcbObjectCreateCallback Oct 19 19:47:25.344389 osafntfimcnd  
[27468:../../../../../../../opensaf/osaf/services/saf/ntfsv/ntfimcnd/ntfimcn_imm.c:0194]
 >>  get_created_dn Oct 19 19:47:25.344392 osafntfimcnd  
[27468:../../../../../../../opensaf/osaf/services/saf/ntfsv/ntfimcnd/ntfimcn_imm.c:0105]
 >>  get_rdn_attr_name Oct 19 19:47:25.344398 osafntfimcnd  
[27468:../../../../../../../opensaf/osaf/libs/agents/saf/imma/imma_om_api.c:4987]
 >>  saImmOmClassDescriptionGet_2 Oct 19 19:47:25.344402 osafntfimcnd  
[27468:../../../../../../../opensaf/osaf/libs/agents/saf/imma/imma_om_api.c:4996]
 >>  saImmOmClassDescriptionGet_2 Oct 19 19:47:25.344407 osafntfimcnd  
[27468:../../../../../../../opensaf/osaf/libs/agents/saf/imma/imma_om_api.c:5066]
 TR ClassName:  TestCCB1 Oct 19 19:47:25.344411 osafntfimcnd  
[27468:../../../../../../../opensaf/osaf/libs/agents/saf/imma/imma_om_api.c:5083]
 TR  ClassDescrGet 3 Oct 19 19:47:25.344578 osafntfimcnd  
[27468:../../../../../../../opensaf/osaf/libs/agents/saf/imma/imma_om_api.c:5121]
 TR Alloc attrdefs  array:0x1933650 Oct 19 19:47:25.344594 osafntfimcnd  

[tickets] [opensaf:tickets] #2646 dtm: Add a tool for syncing log messages to disk

2017-10-19 Thread Anders Widell via Opensaf-tickets
- **Type**: defect --> enhancement
- **Component**: unknown --> dtm
- **Priority**: major --> minor



---

** [tickets:#2646] dtm: Add a tool for syncing log messages to disk**

**Status:** unassigned
**Milestone:** 5.17.10
**Created:** Thu Oct 19, 2017 11:20 AM UTC by Anders Widell
**Last Updated:** Thu Oct 19, 2017 11:20 AM UTC
**Owner:** nobody


Add a command-line tool that can flush and sync all log streams to disk. Use 
this tool in the opensaf_reboot script before rebooting.


---

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] #2646 dtm: Add a tool for syncing log messages to disk

2017-10-19 Thread Anders Widell via Opensaf-tickets



---

** [tickets:#2646] dtm: Add a tool for syncing log messages to disk**

**Status:** unassigned
**Milestone:** 5.17.10
**Created:** Thu Oct 19, 2017 11:20 AM UTC by Anders Widell
**Last Updated:** Thu Oct 19, 2017 11:20 AM UTC
**Owner:** nobody


Add a command-line tool that can flush and sync all log streams to disk. Use 
this tool in the opensaf_reboot script before rebooting.


---

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] #2645 dtm: Use validation functions from base::LogMessage to valida log stream MSGID

2017-10-19 Thread Anders Widell via Opensaf-tickets



---

** [tickets:#2645] dtm: Use validation functions from base::LogMessage to 
valida log stream MSGID**

**Status:** unassigned
**Milestone:** 5.17.10
**Created:** Thu Oct 19, 2017 11:16 AM UTC by Anders Widell
**Last Updated:** Thu Oct 19, 2017 11:16 AM UTC
**Owner:** nobody


the base::LogMessage class already has functions for validating the MSGID field 
of log messages. This could be re-used, with the addition that we should reject 
slashes as well to prevent directory traversal (for security reasons).


---

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] #2644 base: Inconsistent LogMessage::String constructors

2017-10-19 Thread Anders Widell via Opensaf-tickets



---

** [tickets:#2644] base: Inconsistent LogMessage::String constructors**

**Status:** unassigned
**Milestone:** 5.17.10
**Created:** Thu Oct 19, 2017 11:14 AM UTC by Anders Widell
**Last Updated:** Thu Oct 19, 2017 11:14 AM UTC
**Owner:** nobody


The base::LogMessage::String class has two constructors, one taking a "size" 
parameter and a another taking a "max_size" parameter. For former constructor 
seems to be unused, and can be removed.


---

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] #2643 base: Validate the name of the trace log stream

2017-10-19 Thread Anders Widell via Opensaf-tickets



---

** [tickets:#2643] base: Validate the name of the trace log stream**

**Status:** unassigned
**Milestone:** 5.17.10
**Created:** Thu Oct 19, 2017 11:06 AM UTC by Anders Widell
**Last Updated:** Thu Oct 19, 2017 11:06 AM UTC
**Owner:** nobody


Validate the name of the trace log file (sent in the MSGID field of the log 
record). If the name is invalid or too long, use the OpenSAF has function to 
generate a substitute MSGID.


---

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] #2642 dtm: Close unused log streams

2017-10-19 Thread Anders Widell via Opensaf-tickets



---

** [tickets:#2642] dtm: Close unused log streams**

**Status:** unassigned
**Milestone:** 5.17.10
**Created:** Thu Oct 19, 2017 10:46 AM UTC by Anders Widell
**Last Updated:** Thu Oct 19, 2017 10:46 AM UTC
**Owner:** nobody


Consider closing and freeing resources for log streams (except mds.log) that 
have not been used for a while (probably because trace was disabled using 
SIGUSR2).


---

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] #2641 base: Deallocate TraceLog instance when trace is turned off

2017-10-19 Thread Anders Widell via Opensaf-tickets



---

** [tickets:#2641] base: Deallocate TraceLog instance when trace is turned off**

**Status:** unassigned
**Milestone:** 5.17.10
**Created:** Thu Oct 19, 2017 10:45 AM UTC by Anders Widell
**Last Updated:** Thu Oct 19, 2017 10:45 AM UTC
**Owner:** nobody


Consider deallocating the TraceLog instance when trace is turned off (using 
SIGUSR2), to save resources and return the service to the same state as before 
trace was 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.--
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] #2640 base: Use large unix socket send and receive buffers when tracing

2017-10-19 Thread Anders Widell via Opensaf-tickets



---

** [tickets:#2640] base: Use large unix socket send and receive buffers when 
tracing**

**Status:** unassigned
**Milestone:** 5.17.10
**Created:** Thu Oct 19, 2017 10:43 AM UTC by Anders Widell
**Last Updated:** Thu Oct 19, 2017 10:43 AM UTC
**Owner:** nobody


When tracing is enabled, consider increasing the size of the unix socket send 
buffer in tracelog, and the size of the receive buffer in the internal log 
server. This would allow tracelog to handle larger bursts of trace messages 
without blocking or dropping trace messages.


---

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] #2639 base: Use common code for MDS log and tracelog

2017-10-19 Thread Anders Widell via Opensaf-tickets



---

** [tickets:#2639] base: Use common code for MDS log and tracelog**

**Status:** unassigned
**Milestone:** 5.17.10
**Created:** Thu Oct 19, 2017 10:40 AM UTC by Anders Widell
**Last Updated:** Thu Oct 19, 2017 10:40 AM UTC
**Owner:** nobody


The MDS log and the tracelog should be consolidated to use common code, since 
much of the code is the same in both implementations.


---

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] #2638 dtm: Use multiple backup files when rotating log files

2017-10-19 Thread Anders Widell via Opensaf-tickets



---

** [tickets:#2638] dtm: Use multiple backup files when rotating log files**

**Status:** assigned
**Milestone:** 5.17.10
**Created:** Thu Oct 19, 2017 10:15 AM UTC by Anders Widell
**Last Updated:** Thu Oct 19, 2017 10:15 AM UTC
**Owner:** Anders Widell


Currently, only one backup file is used when rotating log files. This may be 
insufficient when the internal log server is used for trace, and the suggestion 
is to use multiple backup files (.1, .2, .3 ... .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] #2637 base: Trace messages can be dropped

2017-10-19 Thread Anders Widell via Opensaf-tickets



---

** [tickets:#2637] base: Trace messages can be dropped**

**Status:** accepted
**Milestone:** 5.17.10
**Created:** Thu Oct 19, 2017 10:13 AM UTC by Anders Widell
**Last Updated:** Thu Oct 19, 2017 10:13 AM UTC
**Owner:** Anders Widell


Since the new logtrace implementation uses non-blocking send, trace messages 
may be dropped in case a large amount of trace messages are generated in a 
burst. The suggestion is to use blocking send instead, to avoid loss of trace 
messages.


---

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] #2635 log: logtest failed after introducing the ticket 2165

2017-10-19 Thread Vu Minh Nguyen via Opensaf-tickets
- **status**: review --> fixed
- **assigned_to**: Vu Minh Nguyen -->  nobody 
- **Comment**:

commit 58a5b360e3c4460c6802b9870814833dcce67d1e (HEAD, origin/develop, 
ticket-2635, develop)
Author: Vu Minh Nguyen 
Date:   Thu Oct 19 16:21:18 2017 +0700

log: update target log file location [#2635]

After introducing the ticket [#2165], writing log to log server
will have its own log file name based on msg_id field.
This change causes logtest failed.(Previously, log was stored in mds.log)

logtest code needs to be updated accordingly .




---

** [tickets:#2635] log: logtest failed after introducing the ticket 2165**

**Status:** fixed
**Milestone:** 5.17.10
**Created:** Thu Oct 19, 2017 07:14 AM UTC by Vu Minh Nguyen
**Last Updated:** Thu Oct 19, 2017 07:28 AM UTC
**Owner:** nobody


After introducing the ticket [#2165], writing log to log server will have its 
own log file name based on msg_id field. This change causes `logtest` failed. 
Previously, log was stored in `mds.log`.

> Suite 18: LOG OI tests, configure alternative destinations
> Failed to perform cmd grep "writing a record to destination_311281152" 
> /var/log/opensaf/mds.log 1> /dev/null
>13  FAILED   (expected EXIT_SUCCESS, got EXIT_FAILURE (1))   Write a log 
> record to destination, OK

`logtest` code needs to be updated accordingly .


---

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] #2632 amf: immxml-configure utility (tool) is failing with "UTF-8" encoding

2017-10-19 Thread Vijay Roy via Opensaf-tickets
Hi Thuan,

Thanks for pointing out. I have corrected the statement. 

commit ca4796d27ceb5810ff2a489c4528a8b24618be48
Author: Vijay Roy 
Date:   Thu Oct 19 13:40:57 2017 +0530

imm: immxml-configure utility (tool) is failing with UTF-8 encoding [#2632]

The fix is to support UTF-8 unicode validatoin for both
UPPER_CASE (UTF-8) and lower_case (utf-8)




---

** [tickets:#2632] amf: immxml-configure utility (tool) is failing with "UTF-8" 
encoding**

**Status:** fixed
**Milestone:** 5.17.10
**Created:** Tue Oct 17, 2017 07:28 AM UTC by Vijay Roy
**Last Updated:** Thu Oct 19, 2017 09:01 AM UTC
**Owner:** Vijay Roy


**Issue:** immxml-configure utility (tool) is failing when upper case "UTF-8" 
is supplied by user. 

Code changes goes at - /src/imm/tools/immxml-merge while validating. 


---

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] #2632 amf: immxml-configure utility (tool) is failing with "UTF-8" encoding

2017-10-19 Thread Thuan via Opensaf-tickets
Hi,

commit mesage should be "imm", not "amf", isn't it?

/Thuan


---

** [tickets:#2632] amf: immxml-configure utility (tool) is failing with "UTF-8" 
encoding**

**Status:** fixed
**Milestone:** 5.17.10
**Created:** Tue Oct 17, 2017 07:28 AM UTC by Vijay Roy
**Last Updated:** Thu Oct 19, 2017 08:15 AM UTC
**Owner:** Vijay Roy


**Issue:** immxml-configure utility (tool) is failing when upper case "UTF-8" 
is supplied by user. 

Code changes goes at - /src/imm/tools/immxml-merge while validating. 


---

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] #2632 amf: immxml-configure utility (tool) is failing with "UTF-8" encoding

2017-10-19 Thread Vijay Roy via Opensaf-tickets
- **status**: review --> fixed



---

** [tickets:#2632] amf: immxml-configure utility (tool) is failing with "UTF-8" 
encoding**

**Status:** fixed
**Milestone:** 5.17.10
**Created:** Tue Oct 17, 2017 07:28 AM UTC by Vijay Roy
**Last Updated:** Thu Oct 19, 2017 08:15 AM UTC
**Owner:** Vijay Roy


**Issue:** immxml-configure utility (tool) is failing when upper case "UTF-8" 
is supplied by user. 

Code changes goes at - /src/imm/tools/immxml-merge while validating. 


---

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] #2632 amf: immxml-configure utility (tool) is failing with "UTF-8" encoding

2017-10-19 Thread Vijay Roy via Opensaf-tickets
Issue fixed with following commit. 

commit 80dbc58573cb9bcced22d9c087954290dcb03ad4
Author: Vijay Roy 
Date:   Thu Oct 19 13:40:57 2017 +0530

amf: immxml-configure utility (tool) is failing with UTF-8 encoding [#2632]

The fix is to support UTF-8 unicode validatoin for both
UPPER_CASE (UTF-8) and lower_case (utf-8)



---

** [tickets:#2632] amf: immxml-configure utility (tool) is failing with "UTF-8" 
encoding**

**Status:** review
**Milestone:** 5.17.10
**Created:** Tue Oct 17, 2017 07:28 AM UTC by Vijay Roy
**Last Updated:** Thu Oct 19, 2017 08:07 AM UTC
**Owner:** Vijay Roy


**Issue:** immxml-configure utility (tool) is failing when upper case "UTF-8" 
is supplied by user. 

Code changes goes at - /src/imm/tools/immxml-merge while validating. 


---

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] #2636 pyosaf: create a common pylint config file for pyosaf

2017-10-19 Thread Nguyen TK Luu via Opensaf-tickets
- **status**: accepted --> review



---

** [tickets:#2636] pyosaf: create a common pylint config file for pyosaf**

**Status:** review
**Milestone:** 5.17.10
**Created:** Thu Oct 19, 2017 07:43 AM UTC by Nguyen TK Luu
**Last Updated:** Thu Oct 19, 2017 07:44 AM UTC
**Owner:** Nguyen TK Luu


Create a common pylint config file for pyosaf, to use with running pylint.


---

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] #2632 amf: immxml-configure utility (tool) is failing with "UTF-8" encoding

2017-10-19 Thread Vijay Roy via Opensaf-tickets
- **status**: accepted --> review
- **Comment**:

Comments from - **zoran.milinko...@ericsson.com**
Hi Vijay,

Please fix indentation before you push the patch.
Ack from me.




---

** [tickets:#2632] amf: immxml-configure utility (tool) is failing with "UTF-8" 
encoding**

**Status:** review
**Milestone:** 5.17.10
**Created:** Tue Oct 17, 2017 07:28 AM UTC by Vijay Roy
**Last Updated:** Tue Oct 17, 2017 07:28 AM UTC
**Owner:** Vijay Roy


**Issue:** immxml-configure utility (tool) is failing when upper case "UTF-8" 
is supplied by user. 

Code changes goes at - /src/imm/tools/immxml-merge while validating. 


---

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] #2636 pyosaf: create a common pylint config file for pyosaf

2017-10-19 Thread Nguyen TK Luu via Opensaf-tickets
- **status**: unassigned --> accepted
- **assigned_to**: Nguyen TK Luu



---

** [tickets:#2636] pyosaf: create a common pylint config file for pyosaf**

**Status:** accepted
**Milestone:** 5.17.10
**Created:** Thu Oct 19, 2017 07:43 AM UTC by Nguyen TK Luu
**Last Updated:** Thu Oct 19, 2017 07:43 AM UTC
**Owner:** Nguyen TK Luu


Create a common pylint config file for pyosaf, to use with running pylint.


---

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] #2636 pyosaf: create a common pylint config file for pyosaf

2017-10-19 Thread Nguyen TK Luu via Opensaf-tickets



---

** [tickets:#2636] pyosaf: create a common pylint config file for pyosaf**

**Status:** unassigned
**Milestone:** 5.17.10
**Created:** Thu Oct 19, 2017 07:43 AM UTC by Nguyen TK Luu
**Last Updated:** Thu Oct 19, 2017 07:43 AM UTC
**Owner:** nobody


Create a common pylint config file for pyosaf, to use with running pylint.


---

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] #2635 log: logtest failed after introducing the ticket 2165

2017-10-19 Thread Vu Minh Nguyen via Opensaf-tickets
- **status**: accepted --> review



---

** [tickets:#2635] log: logtest failed after introducing the ticket 2165**

**Status:** review
**Milestone:** 5.17.10
**Created:** Thu Oct 19, 2017 07:14 AM UTC by Vu Minh Nguyen
**Last Updated:** Thu Oct 19, 2017 07:14 AM UTC
**Owner:** Vu Minh Nguyen


After introducing the ticket [#2165], writing log to log server will have its 
own log file name based on msg_id field. This change causes `logtest` failed. 
Previously, log was stored in `mds.log`.

> Suite 18: LOG OI tests, configure alternative destinations
> Failed to perform cmd grep "writing a record to destination_311281152" 
> /var/log/opensaf/mds.log 1> /dev/null
>13  FAILED   (expected EXIT_SUCCESS, got EXIT_FAILURE (1))   Write a log 
> record to destination, OK

`logtest` code needs to be updated accordingly .


---

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] #2635 log: logtest failed after introducing the ticket 2165

2017-10-19 Thread Vu Minh Nguyen via Opensaf-tickets



---

** [tickets:#2635] log: logtest failed after introducing the ticket 2165**

**Status:** accepted
**Milestone:** 5.17.10
**Created:** Thu Oct 19, 2017 07:14 AM UTC by Vu Minh Nguyen
**Last Updated:** Thu Oct 19, 2017 07:14 AM UTC
**Owner:** Vu Minh Nguyen


After introducing the ticket [#2165], writing log to log server will have its 
own log file name based on msg_id field. This change causes `logtest` failed. 
Previously, log was stored in `mds.log`.

> Suite 18: LOG OI tests, configure alternative destinations
> Failed to perform cmd grep "writing a record to destination_311281152" 
> /var/log/opensaf/mds.log 1> /dev/null
>13  FAILED   (expected EXIT_SUCCESS, got EXIT_FAILURE (1))   Write a log 
> record to destination, OK

`logtest` code needs to be updated accordingly .


---

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