[tickets] [opensaf:tickets] #2382 imm: reducing log level for ccb-committed messages
- **status**: review --> wontfix
- **Comment**:
The fix for the problem wil be a part of Enhancement #2306
---
** [tickets:#2382] imm: reducing log level for ccb-committed messages**
**Status:** wontfix
**Milestone:** 5.0.2
**Created:** Thu Mar 16, 2017 09:26 AM UTC by Neelakanta Reddy
**Last Updated:** Thu Mar 16, 2017 10:30 AM UTC
**Owner:** Neelakanta Reddy
if(i != sOwnerVector.end()) {
LOG_NO("Ccb %u COMMITTED (%s)", ccb->mId,
(*i)->mAdminOwnerName.c_str());
} else {
LOG_NO("Ccb %u COMMITTED (%s)", ccb->mId, "");
}
Reduce the LOG_NO to TRACE
---
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] #2387 clm_locked spare controller got standby role after failover
- **status**: unassigned --> assigned - **assigned_to**: Praveen - **Part**: - --> d - **Milestone**: 5.2.RC2 --> 5.0.2 --- ** [tickets:#2387] clm_locked spare controller got standby role after failover** **Status:** assigned **Milestone:** 5.0.2 **Created:** Fri Mar 17, 2017 12:13 PM UTC by Ritu Raj **Last Updated:** Fri Mar 17, 2017 12:13 PM UTC **Owner:** Praveen **Attachments:** - [SC-1.tar.bz2](https://sourceforge.net/p/opensaf/tickets/2387/attachment/SC-1.tar.bz2) (873.4 kB; application/x-bzip) - [SC-2.tar.bz2](https://sourceforge.net/p/opensaf/tickets/2387/attachment/SC-2.tar.bz2) (762.0 kB; application/x-bzip) - [SC-3.tar.bz2](https://sourceforge.net/p/opensaf/tickets/2387/attachment/SC-3.tar.bz2) (724.5 kB; application/x-bzip) ###Environment details OS : Suse 64bit Changeset : 8701 ( 5.2.RC1) 6 nodes setup(3 controller and 3 payload, with SC_ABSENCE enabled) ###Summary clm_locked spare controller got standby role after failover ###Steps followed & Observed behaviour 1. Initially SC-1 (ACTIVE), SC-2 (QUIESCED) , SC-3 (STANDBY) role 2. Performed clm_lock operation on SC-2(QUIESCED) controller 3. after, that perfomed on failover on Active controller (SC-1), by killing one director 4. Observed that SC-3 got Active role while SC-2 got Standby role, which is not expcted as node SC-2 is in clm_locked state 5. Later, SC-1 joined as QUIESCED controller (after recovery from failover) **Expected**: clm_lock node should not get standby role as it is in locked state and SC-1 should join as a Standby after recovery from failover. Syslog: Mar 17 17:56:59 suseR2-S2 osafimmnd[21809]: NO Implementer (applier) connected: 28 (@safSmf_applier1) <0, 2030f> Mar 17 17:56:59 suseR2-S2 osafamfnd[21859]: NO Assigning 'safSi=SC-2N,safApp=OpenSAF' STANDBY to 'safSu=SC-2,safSg=2N,safApp=OpenSAF' Mar 17 17:56:59 suseR2-S2 osafrded[21779]: NO RDE role set to STANDBY Mar 17 17:56:59 suseR2-S2 osafrded[21779]: NO Peer up on node 0x2030f Mar 17 17:56:59 suseR2-S2 osafrded[21779]: NO Got peer info request from node 0x2030f with role ACTIVE Mar 17 17:56:59 suseR2-S2 osafrded[21779]: NO Got peer info response from node 0x2030f with role ACTIVE Mar 17 17:56:59 suseR2-S2 osafimmd[21798]: NO MDS event from svc_id 24 (change:3, dest:13) Mar 17 17:56:59 suseR2-S2 osafimmd[21798]: NO MDS event from svc_id 24 (change:5, dest:13) Mar 17 17:56:59 suseR2-S2 osafimmd[21798]: NO MDS event from svc_id 24 (change:5, dest:13) Mar 17 17:56:59 suseR2-S2 osafimmd[21798]: NO MDS event from svc_id 25 (change:3, dest:566317113647120) Mar 17 17:56:59 suseR2-S2 osafimmd[21798]: NO MDS event from svc_id 25 (change:3, dest:565213543063568) Mar 17 17:56:59 suseR2-S2 osafimmd[21798]: IN AMF HA STANDBY request Mar 17 17:56:59 suseR2-S2 osafimmd[21798]: IN Added IMMND node with dest 566317113647120 Mar 17 17:56:59 suseR2-S2 osafimmd[21798]: IN Added IMMND node with dest 565213543063568 Mar 17 17:56:59 suseR2-S2 osafsmfd[21878]: WA saClmClusterNodeGet failed, rc=SA_AIS_ERR_UNAVAILABLE (31) Mar 17 17:56:59 suseR2-S2 osafsmfd[21878]: WA proc_mds_info: SMFND UP failed Mar 17 17:56:59 suseR2-S2 osafsmfd[21878]: WA saClmClusterNodeGet failed, rc=SA_AIS_ERR_UNAVAILABLE (31) Mar 17 17:56:59 suseR2-S2 osafsmfd[21878]: WA proc_mds_info: SMFND UP failed From Traces: SC-2 left the cluster as clm lock operation performed and later SC-1 left the cluster as one failover performed: ~~~ SC-2::: Mar 17 17:54:24.123134 osafamfnd [6773:src/amf/amfnd/clm.cc:0196] >> clm_track_cb: '0' '4' '1' Mar 17 17:54:24.123142 osafamfnd [6773:src/amf/amfnd/clm.cc:0217] TR Node has left the cluster 'safNode=SC-2,safCluster=myClmCluster', avnd_cb->first_time_up 0,notifItem->clusterNode.nodeId 131599, avnd_cb->node_info.nodeId 131343 - - SC-1::: Mar 17 17:57:03.514477 osafamfnd [9266:src/amf/amfnd/clm.cc:0196] >> clm_track_cb: '0' '4' '1' Mar 17 17:57:03.514484 osafamfnd [9266:src/amf/amfnd/clm.cc:0217] TR Node has left the cluster 'safNode=SC-1,safCluster=myClmCluster', avnd_cb->first_time_up 0,notifItem->clusterNode.nodeId 131343, avnd_cb->node_info.nodeId 131855 ~~~ after failover SC-2 got standby role and SC-3 Active : ~~~ SC::2 Mar 17 17:56:59.941081 osafamfnd [21859:src/amf/amfnd/susm.cc:1043] NO Assigned 'safSi=SC-2N,safApp=OpenSAF' STANDBY to 'safSu=SC-2,safSg=2N,safApp=OpenSAF' Mar 17 17:56:59.941089 osafamfnd [21859:src/amf/amfnd/err.cc:1639] >> is_no_assignment_due_to_escalations Mar 17 17:56:59.941097 osafamfnd [21859:src/amf/amfnd/err.cc:1651] << is_no_assignment_due_to_escalations: false Mar 17 17:56:59.941104 osafamfnd [21859:src/amf/amfnd/di.cc:0829] >> avnd_di_susi_resp_send: Sending Resp su=safSu=SC-2,safSg=2N,safApp=OpenSAF, si=safSi=SC-2N,safApp=OpenSAF, curr_state=2, prv_state=0 Mar 17 17:56:59.941112 osafamfnd [21859:src/amf/amfnd/di.cc:0839] TR curr_assign_state '3 SC:::3 Mar 17 17:57:03.656105 osafamfnd [9266:src/amf/amfnd/susm.cc:1043] NO Assigned 'safSi=SC-2N,safApp=OpenSAF' ACTIVE
[tickets] [opensaf:tickets] #2368 amf: CLC CLI command env variables are not correctly printed in traces
- **status**: review --> fixed
- **Comment**:
changeset: 8708:9073359c83b4 [staging:907335]
branch: opensaf-5.0.x
tag: tip
parent: 8703:49e0054b8b9a
user: Nguyen Luu
date: Mon Mar 20 15:07:19 2017 +1100
summary: amfnd: print list of CLC CLI command env variables correctly [#2368]
changeset: 8707:4e47c66382f3 [staging:4e47c6]
branch: opensaf-5.1.x
parent: 8704:43263bc53403
user: Nguyen Luu
date: Mon Mar 20 15:07:11 2017 +1100
summary: amfnd: print list of CLC CLI command env variables correctly [#2368]
changeset: 8706:e85fab0da695 [staging:e85fab]
user: Nguyen Luu
date: Mon Mar 20 15:05:48 2017 +1100
summary: amfnd: print list of CLC CLI command env variables correctly [#2368]
---
** [tickets:#2368] amf: CLC CLI command env variables are not correctly printed
in traces**
**Status:** fixed
**Milestone:** 5.2.RC2
**Created:** Mon Mar 13, 2017 04:27 AM UTC by Nguyen TK Luu
**Last Updated:** Mon Mar 13, 2017 04:56 AM UTC
**Owner:** Nguyen TK Luu
The list of CLC CLI command env variables of a component are not correctly
printed in the AMFND traces. As shown below, only the first variable in the
list got printed repeatedly for the length of the list.
Mar 13 10:48:24.767739 osafamfnd [285:src/amf/amfnd/clc.cc:3098] T1 CLC CLI
script:'/usr/local/lib/opensaf/clc-cli/osaf-ntfd'
Mar 13 10:48:24.767742 osafamfnd [285:src/amf/amfnd/clc.cc:3100] T1 CLC CLI
command arguments[1] ='instantiate'
Mar 13 10:48:24.767745 osafamfnd [285:src/amf/amfnd/clc.cc:3103] T1 CLC CLI
command timeout: In nano secs:100 In milli secs: 1
Mar 13 10:48:24.767748 osafamfnd [285:src/amf/amfnd/clc.cc:3107] T1 CLC CLI
command env variable name = 'SA_AMF_COMPONENT_NAME': value
='safComp=NTF,safSu=SC-1,safSg=2N,safApp=OpenSAF'
Mar 13 10:48:24.767750 osafamfnd [285:src/amf/amfnd/clc.cc:3107] T1 CLC CLI
command env variable name = 'SA_AMF_COMPONENT_NAME': value
='safComp=NTF,safSu=SC-1,safSg=2N,safApp=OpenSAF'
Mar 13 10:48:24.767845 osafamfnd [285:src/mds/mds_dt_trans.c:0608] >>
mdtm_process_poll_recv_data_tcp
Mar 13 10:48:24.768555 osafamfnd [285:src/amf/amfnd/clc.cc:3139] T2 The CLC CLI
command execution success
.
Mar 13 10:48:24.789082 osafamfnd [285:src/amf/amfnd/clc.cc:3098] T1 CLC CLI
script:'/usr/local/lib/opensaf/clc-cli/osaf-clmd'
Mar 13 10:48:24.789085 osafamfnd [285:src/amf/amfnd/clc.cc:3100] T1 CLC CLI
command arguments[1] ='instantiate'
Mar 13 10:48:24.789088 osafamfnd [285:src/amf/amfnd/clc.cc:3103] T1 CLC CLI
command timeout: In nano secs:100 In milli secs: 1
Mar 13 10:48:24.789091 osafamfnd [285:src/amf/amfnd/clc.cc:3107] T1 CLC CLI
command env variable name = 'SA_AMF_COMPONENT_NAME': value
='safComp=CLM,safSu=SC-1,safSg=2N,safApp=OpenSAF'
Mar 13 10:48:24.789094 osafamfnd [285:src/amf/amfnd/clc.cc:3107] T1 CLC CLI
command env variable name = 'SA_AMF_COMPONENT_NAME': value
='safComp=CLM,safSu=SC-1,safSg=2N,safApp=OpenSAF'
Mar 13 10:48:24.789201 osafamfnd [285:src/mds/mds_dt_trans.c:0608] >>
mdtm_process_poll_recv_data_tcp
Mar 13 10:48:24.789650 osafamfnd [285:src/amf/amfnd/clc.cc:3139] T2 The CLC CLI
command execution success
.
Mar 13 10:53:05.010777 osafamfnd [285:src/amf/amfnd/clc.cc:3098] T1 CLC CLI
script:'/opt/amf_demo/amf_demo_script'
Mar 13 10:53:05.010781 osafamfnd [285:src/amf/amfnd/clc.cc:3100] T1 CLC CLI
command arguments[1] ='instantiate'
Mar 13 10:53:05.010786 osafamfnd [285:src/amf/amfnd/clc.cc:3103] T1 CLC CLI
command timeout: In nano secs:100 In milli secs: 1
Mar 13 10:53:05.010790 osafamfnd [285:src/amf/amfnd/clc.cc:3107] T1 CLC CLI
command env variable name = 'AMF_DEMO_VAR2': value ='CT_VALUE2'
Mar 13 10:53:05.010794 osafamfnd [285:src/amf/amfnd/clc.cc:3107] T1 CLC CLI
command env variable name = 'AMF_DEMO_VAR2': value ='CT_VALUE2'
Mar 13 10:53:05.010798 osafamfnd [285:src/amf/amfnd/clc.cc:3107] T1 CLC CLI
command env variable name = 'AMF_DEMO_VAR2': value ='CT_VALUE2'
Mar 13 10:53:05.010801 osafamfnd [285:src/amf/amfnd/clc.cc:3107] T1 CLC CLI
command env variable name = 'AMF_DEMO_VAR2': value ='CT_VALUE2'
Mar 13 10:53:05.010805 osafamfnd [285:src/amf/amfnd/clc.cc:3107] T1 CLC CLI
command env variable name = 'AMF_DEMO_VAR2': value ='CT_VALUE2'
Mar 13 10:53:05.010809 osafamfnd [285:src/amf/amfnd/clc.cc:3107] T1 CLC CLI
command env variable name = 'AMF_DEMO_VAR2': value ='CT_VALUE2'
Mar 13 10:53:05.010813 osafamfnd [285:src/amf/amfnd/clc.cc:3107] T1 CLC CLI
command env variable name = 'AMF_DEMO_VAR2': value ='CT_VALUE2'
Mar 13 10:53:05.011176 osafamfnd [285:src/amf/amfnd/clc.cc:3139] T2 The CLC CLI
command execution success
This is due to an error in the code that prints the list of CLC CLI command env
variables:
~~~
src/amf/amfnd/clc.cc:
for(count=0;countnum_args;count++)
TRACE_1("CLC CLI command env variable name = '%s': value
='%s'",
cmd_info.i_set_env_args->env_arg->name,cmd_info.i_set_env_args->env_arg->value);
~~~
---
Sent from sourceforge.net because opensaf-tickets@lists.sourceforge.net is
subscribed t
