Ack
Thanks
-Nagu
> -Original Message-
> From: Hans Nordeback [mailto:hans.nordeb...@ericsson.com]
> Sent: 08 July 2016 19:06
> To: Praveen Malviya; Nagendra Kumar
> Cc: opensaf-devel@lists.sourceforge.net
> Subject: [PATCH 1 of 1] amfnd: Incorrect ER messages in syslog [#1911]
>
>
osaf/services/saf/amf/amfnd/su.cc | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/osaf/services/saf/amf/amfnd/su.cc
b/osaf/services/saf/amf/amfnd/su.cc
--- a/osaf/services/saf/amf/amfnd/su.cc
+++ b/osaf/services/saf/amf/amfnd/su.cc
@@ -422,7 +422,7 @@ uint32_t
Summary: amfnd: Incorrect ER messages in syslog
Review request for Trac Ticket(s): #1911
Peer Reviewer(s): Nagu, Praveen
Pull request to:
Affected branch(es): default
Development branch: default
Impacted area Impact y/n
On 08/07/16 16:05, praveen malviya wrote:
>
>
> On 07-Jul-16 6:31 PM, minh chau wrote:
>> Hi Praveen,
>>
>> NoRed MW allows locking SU only, and not allow locking SI, which means
>> to me if NoRed MW SUs are unlocked it must provide its services (SMFND,
>> IMMND, CPND, CLMNA)
>> I'm not sure
Hi Praveen,
Ack, code review only, you can ignore my comment below, I just remember it has
been discussed in ticket #1465. /Thanks Hans
-Original Message-
From: Hans Nordebäck [mailto:hans.nordeb...@ericsson.com]
Sent: den 8 juli 2016 14:27
To: praveen malviya
Summary: rde: Change syslog priority from ER to WA when MDS send fails [#1907]
Review request for Trac Ticket(s): 1907
Peer Reviewer(s): Ramesh
Pull request to:
Affected branch(es): opensaf-5.0.x, default(5.1)
Development branch: default
Impacted area
osaf/services/infrastructure/rde/rde_mds.cc | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
RDE may fail to send MDS messages to its peer, e.g. when the peer node is down.
This should not be considered an error and therefore the syslog messages should
not have ER priority. The
Hi Praveen,
a question, the alarm "Service Instance Unassigned" is still raised when
locking NoRed MW, shouldn't it be suppressed?
/Thanks HansN
On 07/08/2016 08:05 AM, praveen malviya wrote:
>
>
> On 07-Jul-16 6:31 PM, minh chau wrote:
>> Hi Praveen,
>>
>> NoRed MW allows locking SU only, and
Hi Mahesh,
To make long DN work (e.g: long DN at @Ng token), we have to do some
settings first. IMM is one of them.
You can refer to ` setUpTestEnv()` @ tet_log_longDN.c for details on this.
One question, have you tried to run the added test suite #13 for verifying
long DN?
With this test suite,
Hi Mahesh,
Could you please have a look into this patch? Thanks.
Best regards,
Nhat Pham
-Original Message-
From: Nhat Pham [mailto:nhat.p...@dektech.com.au]
Sent: Friday, May 13, 2016 9:11 AM
To: mahesh.va...@oracle.com; anders.wid...@ericsson.com
Cc:
Hi Mahesh,
It looks like long DN is no allowed in IMM.
Check how you have configured IMM.
Thanks,
Zoran
-Original Message-
From: A V Mahesh [mailto:mahesh.va...@oracle.com]
Sent: den 8 juli 2016 11:00
To: Vu Minh Nguyen; Lennart Lund
Cc: opensaf-devel@lists.sourceforge.net
Subject: Re:
Hi Vu,
While validating the patch , i received following errors , do we need to
apply any other IMM patchs
to validate this patch ?
==
# Jul 8 13:03:03 SC-1 osafimmnd[23888]: NO ERR_INVALID_PARAM: RDN
attribute
Hi,
Thanks for your response.
If that is the case please move ticket to accepted state.
Thanks,
Praveen
On 06-Jul-16 8:58 AM, Vo Minh Hoang wrote:
> Dear Praveen,
>
> I am sorry to say that after applying #1818, this problem still occur in the
> same phenomenon.
> The occur rate is small when
On 07-Jul-16 6:31 PM, minh chau wrote:
> Hi Praveen,
>
> NoRed MW allows locking SU only, and not allow locking SI, which means
> to me if NoRed MW SUs are unlocked it must provide its services (SMFND,
> IMMND, CPND, CLMNA)
> I'm not sure whether this is a must-have requirement or not, since
14 matches
Mail list logo
