ummary: plm: correct first arguement of API saPlmEntityGroupAdd() in apitest
[#1983]
Review request for Ticket(s): 1983
Peer Reviewer(s):ajo...@rbbn.com
Pull request to: Alex
Affected branch(es): all
Development branch: ticket-1983
Base revision: 1c19eddc9f03ebd18ab85b67ab50e3e5037b449e
Personal
---
src/plm/apitest/test_saPlmEntityGroupAdd.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/src/plm/apitest/test_saPlmEntityGroupAdd.c
b/src/plm/apitest/test_saPlmEntityGroupAdd.c
index 842147c..01f62ac 100644
--- a/src/plm/apitest/test_saPlmEntityGroupAdd.c
+++
---
src/plm/apitest/test_saPlmEntityGroupAdd.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/src/plm/apitest/test_saPlmEntityGroupAdd.c
b/src/plm/apitest/test_saPlmEntityGroupAdd.c
index 842147c..01f62ac 100644
--- a/src/plm/apitest/test_saPlmEntityGroupAdd.c
+++
Summary: plm: correct first arguement of API saPlmEntityGroupAdd() in apitest
[#1983]
Review request for Ticket(s): 1983
Peer Reviewer(s):ajo...@rbbn.com
Pull request to: Alex
Affected branch(es): all
Development branch: ticket-1983
Base revision: 1c19eddc9f03ebd18ab85b67ab50e3e5037b449e
Personal
When NTFD is started, the NtfAdmin class object is defined and log client is
initialized in this object. The initialiation of client may be loop forever
if TRY_AGAIN error always return. Somehow log service has not been started on
time or log service is busy, NTFD is kept in the loop. And the AMF
Summary: ntf: Update timeout for initializing log client [#2878]
Review request for Ticket(s): 2878
Peer Reviewer(s): Lennart, Minh, Vu
Pull request to: *** LIST THE PERSON WITH PUSH ACCESS HERE ***
Affected branch(es): develop
Development branch: ticket-2878
Base revision:
Hi Canh,
Ack. See my minor misspell comment below
Thanks
Lennart
> -Original Message-
> From: Canh Van Truong
> Sent: den 20 augusti 2018 10:48
> To: Minh Hon Chau ; Gary Lee
> ; Hans Nordebäck
> ; Lennart Lund
>
> Cc: opensaf-devel@lists.sourceforge.net; Canh Van Truong
>
> Subject:
Hi Canh,
ack, code review only. /Thanks HansN
On 08/20/2018 10:48 AM, Canh Van Truong wrote:
When processing "MBCSV_PEER_UP_MSG" msg in case dispatch all from user,
the msg may be too old. The msg may be come from the node that already rebooted.
This reason cause mbcsv loop forever in WHILE
Summary: mbc: fix mbcsv loop forever while it is being dispatch ALL [#2899]
Review request for Ticket(s): 2899
Peer Reviewer(s): Hans, Minh, Gary, Lennart
Pull request to: *** LIST THE PERSON WITH PUSH ACCESS HERE ***
Affected branch(es): develop
Development branch: ticket-2899
Base revision:
When processing "MBCSV_PEER_UP_MSG" msg in case dispatch all from user,
the msg may be too old. The msg may be come from the node that already rebooted.
This reason cause mbcsv loop forever in WHILE loop, because the active node
cannot
find the adest of peer msg.
The solution is that find entity
10 matches
Mail list logo