- Description has changed:
Diff:
~~~~
--- old
+++ new
@@ -11,6 +11,18 @@
Step1 will return SA_AIS_ERR_TIMEOUT (Expected)
Step2 is returning SA_AIS_ERR_BAD_HANDLE (SA_AIS_OK is expected)
-Note: Test passed in OpenSAF release 5.0
+Sep 6 12:22:27 SLOT1 python2.5: logtrace: trace enabled to file
/tmp/imma_oi_callbacktimeout.trace, mask=0xffffffff
+Sep 6 12:22:27 SLOT1 python2.5: NO IMMA library TRACE initialize done
pid:1147 svid:26 file:/tmp/imma_oi_callbacktimeout.trace
+Sep 6 12:22:27 SLOT1 osafimmnd[838]: NO Implementer connected: 14
(testOiTmout_verifyAdminOpCallback_37) <343, 2010f>
+Sep 6 12:22:42 SLOT1 osafimmnd[838]: WA IMMND - Client went down so no
response
+Sep 6 12:22:42 SLOT1 osafimmnd[838]: WA MDS Send Failed to service:IMMND rc:2
+Sep 6 12:22:42 SLOT1 osafimmnd[838]: ER Problem in sending to peer IMMND over
MDS. Discarding admin op reply.
+Sep 6 12:22:42 SLOT1 osafimmnd[838]: WA Error code 2 returned for message
type 21 - ignoring
+Sep 6 12:22:47 SLOT1 osafimmnd[838]: WA IMMND - Client 1468878946575 went
down on syncronous request, discarding request
+Sep 6 12:22:47 SLOT1 osafimmnd[838]: NO Implementer locally disconnected.
Marking it as doomed 14 <343, 2010f> (testOiTmout_verifyAdminOpCallback_37)
+Sep 6 12:22:47 SLOT1 osafimmnd[838]: NO Implementer disconnected 14 <343,
2010f> (testOiTmout_verifyAdminOpCallback_37)
+
+
+Note: **Test passed in OpenSAF release 5.0**
Agent traces and immnd, immd traces attached
~~~~
---
** [tickets:#2001] IMM: AdminOperation returns BAD_HANDLE when invoked second
time**
**Status:** unassigned
**Milestone:** 5.1.RC1
**Created:** Tue Sep 06, 2016 07:14 AM UTC by Chani Srivastava
**Last Updated:** Tue Sep 06, 2016 07:14 AM UTC
**Owner:** nobody
**Attachments:**
-
[AdminCbkTmOut.zip](https://sourceforge.net/p/opensaf/tickets/2001/attachment/AdminCbkTmOut.zip)
(95.1 kB; application/zip)
OS : Suse 64bit
Changeset : 7997 ( 5.1.FC)
Setup : 4 nodes 1 PBE enabled
Summary:
Steps to Reproduce
1. Invoke saImmOmAdminOperationInvokeAsync_2() while waiting in callback with
time more that OI_CALLBACK_TIMEOUT value
2. Invoke saImmOmAdminOperationInvokeAsync_2() again and do not wait
Observed Bahavior:
Step1 will return SA_AIS_ERR_TIMEOUT (Expected)
Step2 is returning SA_AIS_ERR_BAD_HANDLE (SA_AIS_OK is expected)
Sep 6 12:22:27 SLOT1 python2.5: logtrace: trace enabled to file
/tmp/imma_oi_callbacktimeout.trace, mask=0xffffffff
Sep 6 12:22:27 SLOT1 python2.5: NO IMMA library TRACE initialize done pid:1147
svid:26 file:/tmp/imma_oi_callbacktimeout.trace
Sep 6 12:22:27 SLOT1 osafimmnd[838]: NO Implementer connected: 14
(testOiTmout_verifyAdminOpCallback_37) <343, 2010f>
Sep 6 12:22:42 SLOT1 osafimmnd[838]: WA IMMND - Client went down so no response
Sep 6 12:22:42 SLOT1 osafimmnd[838]: WA MDS Send Failed to service:IMMND rc:2
Sep 6 12:22:42 SLOT1 osafimmnd[838]: ER Problem in sending to peer IMMND over
MDS. Discarding admin op reply.
Sep 6 12:22:42 SLOT1 osafimmnd[838]: WA Error code 2 returned for message type
21 - ignoring
Sep 6 12:22:47 SLOT1 osafimmnd[838]: WA IMMND - Client 1468878946575 went down
on syncronous request, discarding request
Sep 6 12:22:47 SLOT1 osafimmnd[838]: NO Implementer locally disconnected.
Marking it as doomed 14 <343, 2010f> (testOiTmout_verifyAdminOpCallback_37)
Sep 6 12:22:47 SLOT1 osafimmnd[838]: NO Implementer disconnected 14 <343,
2010f> (testOiTmout_verifyAdminOpCallback_37)
Note: **Test passed in OpenSAF release 5.0**
Agent traces and immnd, immd traces attached
---
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.
------------------------------------------------------------------------------
_______________________________________________
Opensaf-tickets mailing list
Opensaf-tickets@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
