- **status**: accepted --> review
- **Part**: - --> d
- **Milestone**: future --> 5.18.09
---
** [tickets:#197] admin operation on second entity fails when response to first
admin operation is with held and sent later**
**Status:** review
**Milestone:** 5.18.09
**Created:** Tue May 14, 2013 09:18 AM UTC by Mathi Naickan
**Last Updated:** Wed Sep 12, 2018 05:01 PM UTC
**Owner:** Alex Jones
Issued admin lock operation with trylock option on three entities
a) safEE=PL-5,safHE=4555_slot_5,safDomain=domain_1
b) safEE=PL-12,safHE=7220_slot_13,safDomain=domain_1
c) safEE=PL-13,safHE=7220_slot_1,safDomain=domain_1
The test application did not give response to any one of the lock operations
immediatley. Instead it waited for all admin operations to get started.
After all the admin operations got invoked, response is sent as each callback
is processed.
So, the scenario is such that, 3 validate callbacks are in the mail box and the
testing application has processed all the 3 validate callbacks
But lock operation pertaining to
safEE=PL-5,safHE=4555_slot_5,safDomain=domain_1 is processed.
Following is the snippet for the corresponding failure in admin operations.
Jan 22 11:09:03 localhost osafplmd[3988]: Invocation id mentioned in the resp,
is not found in the grp->inocation_list. inv_id: 9
Jan 22 11:09:07 localhost osafplmd[3988]: Invocation id mentioned in the resp,
is not found in the grp->inocation_list. inv_id: 12
Breakpoint 1, pycbk_SaPlmReadinessTrackCallbackT (entityGroupHandle=36,
trackCookie=100, invocation=6, cause=SA_PLM_CAUSE_LOCK,
rootCauseEntity=0xac003bd0, rootCorrelationId=0, trackedEntities=0xac003cdc,
step=SA_PLM_CHANGE_VALIDATE, error1=SA_AIS_OK)
at saPlm_wrap.c:2838
2838 in saPlm_wrap.c
(gdb) c
Continuing.
***********************PLM CALLBACK***************************
cookie—> 100
cause—-> SA_PLM_CAUSE_LOCK (2)
root_cause_entity—-> safEE=PL-5,safHE=4555_slot_5,safDomain=domain_1
step—> SA_PLM_CHANGE_VALIDATE (1)
error—> 1
num_tracked_entities—> 1
entity—> safEE=PL-5,safHE=4555_slot_5,safDomain=domain_1
entity change —> SA_PLM_GROUP_MEMBER_READINESS_CHANGE (4)
Current_RStatus —> ('IN_SERVICE', 0)
Expected_RStatus —> ('OUT_OF_SERVICE', 0)
Invoking the function <built-in function saPlmReadinessTrackResponse> with the
arguments (36L, 6L, 1)
('Return Value of the function : <—', 1)
**************************************************************
Breakpoint 1, pycbk_SaPlmReadinessTrackCallbackT (entityGroupHandle=36,
trackCookie=100, invocation=9, cause=SA_PLM_CAUSE_LOCK,
rootCauseEntity=0xac004c38, rootCorrelationId=0, trackedEntities=0xac004d44,
step=SA_PLM_CHANGE_VALIDATE, error1=SA_AIS_OK)
at saPlm_wrap.c:2838
2838 in saPlm_wrap.c
(gdb) c
Continuing.
***********************PLM CALLBACK***************************
cookie—> 100
cause—-> SA_PLM_CAUSE_LOCK (2)
root_cause_entity—-> safEE=PL-12,safHE=7220_slot_13,safDomain=domain_1
step—> SA_PLM_CHANGE_VALIDATE (1)
error—> 1
num_tracked_entities—> 1
entity—> safEE=PL-12,safHE=7220_slot_13,safDomain=domain_1
entity change —> SA_PLM_GROUP_MEMBER_READINESS_CHANGE (4)
Current_RStatus —> ('IN_SERVICE', 0)
Expected_RStatus —> ('OUT_OF_SERVICE', 0)
Invoking the function <built-in function saPlmReadinessTrackResponse> with the
arguments (36L, 9L, 1)
('Return Value of the function : <—', 1)
**************************************************************
Breakpoint 1, pycbk_SaPlmReadinessTrackCallbackT (entityGroupHandle=36,
trackCookie=100, invocation=12, cause=SA_PLM_CAUSE_LOCK,
rootCauseEntity=0xac005dd0, rootCorrelationId=0, trackedEntities=0xac005edc,
step=SA_PLM_CHANGE_VALIDATE, error1=SA_AIS_OK)
at saPlm_wrap.c:2838
2838 in saPlm_wrap.c
(gdb) c
Continuing.
***********************PLM CALLBACK***************************
cookie—> 100
cause—-> SA_PLM_CAUSE_LOCK (2)
root_cause_entity—-> safEE=PL-13,safHE=7220_slot_1,safDomain=domain_1
step—> SA_PLM_CHANGE_VALIDATE (1)
error—> 1
num_tracked_entities—> 1
entity—> safEE=PL-13,safHE=7220_slot_1,safDomain=domain_1
entity change —> SA_PLM_GROUP_MEMBER_READINESS_CHANGE (4)
Current_RStatus —> ('IN_SERVICE', 0)
Expected_RStatus —> ('OUT_OF_SERVICE', 0)
Invoking the function <built-in function saPlmReadinessTrackResponse> with the
arguments (36L, 12L, 1)
('Return Value of the function : <—', 1)
**************************************************************
Breakpoint 1, pycbk_SaPlmReadinessTrackCallbackT (entityGroupHandle=36,
trackCookie=100, invocation=15, cause=SA_PLM_CAUSE_LOCK,
rootCauseEntity=0xac003bd0, rootCorrelationId=0, trackedEntities=0xac003cdc,
step=SA_PLM_CHANGE_START, error1=SA_AIS_OK)
at saPlm_wrap.c:2838
2838 in saPlm_wrap.c
(gdb) c
Continuing.
***********************PLM CALLBACK***************************
cookie—> 100
cause—-> SA_PLM_CAUSE_LOCK (2)
root_cause_entity—-> safEE=PL-5,safHE=4555_slot_5,safDomain=domain_1
step—> SA_PLM_CHANGE_START (2)
error—> 1
num_tracked_entities—> 1
entity—> safEE=PL-5,safHE=4555_slot_5,safDomain=domain_1
entity change —> SA_PLM_GROUP_MEMBER_READINESS_CHANGE (4)
Current_RStatus —> ('IN_SERVICE', 0)
Expected_RStatus —> ('OUT_OF_SERVICE', 0)
Invoking the function <built-in function saPlmReadinessTrackResponse> with the
arguments (36L, 15L, 1)
('Return Value of the function : <—', 1)
**************************************************************
---
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
