Similar issue is observed for different N way configuration. This one is random
Application is configured with 1 App, 1 SG, 2 SUs, 3SIs with 3 CSIs ( and
maxActiveSis configured the value 2)
Initially SG is in unlocked state, and unlock-in operation is performed on all
the SUs, followed by unlock operation. This resulted in one SU with 2 active SI
assignments and 1 standby assignment and another SU with 1 active SI assignment
and 2 standby assignments.
If lock operation is performed on the SU1, quiesced assignment is not removed
for this SU and the lock-in operation is failing with TRY-AGAIN return value.
Apr 18 11:15:27.463346 osafamfd [5579:imm.cc:1816] >> report_admin_op_error:
inv:1103806595132, res:6, Error String: 'SIs still assigned to this SU
'safSu=cust_NWay_1Norm_1,safSg=SG_cust_n,safApp=N''
safSISU=safSu=cust_NWay_1Norm_1\,safSg=SG_cust_n\,safApp=N,safSi=cust_NWay_1Norm_1,safApp=N
saAmfSISUHAState=QUIESCED(3)
safSISU=safSu=cust_NWay_1Norm_2\,safSg=SG_cust_n\,safApp=N,safSi=cust_NWay_1Norm_3,safApp=N
saAmfSISUHAState=ACTIVE(1)
safSISU=safSu=cust_NWay_1Norm_2\,safSg=SG_cust_n\,safApp=N,safSi=cust_NWay_1Norm_1,safApp=N
saAmfSISUHAState=ACTIVE(1)
safSISU=safSu=cust_NWay_1Norm_1\,safSg=SG_cust_n\,safApp=N,safSi=cust_NWay_1Norm_3,safApp=N
saAmfSISUHAState=STANDBY(2)
In this scenario, if I perform the lock operation of SU2, all the assignments
in the app are removed and the lock-in operation of the first SU is succeeded.
This scenario is random.
---
** [tickets:#316] SI Assignments are not removed for a SU in Nway redundancy
model**
**Status:** assigned
**Milestone:** 4.7-Tentative
**Created:** Fri May 24, 2013 08:39 AM UTC by Nagendra Kumar
**Last Updated:** Wed Apr 15, 2015 11:37 AM UTC
**Owner:** Praveen
Migrated from http://devel.opensaf.org/ticket/2987
changeset : 3855
Model : NWay
configuration : 1App,1SG,5SU with 3comps each, 5SIs with 3csi each.
si-si deps configured as SI1<-SI2<-SI3<-SI4
SIrankedSus not configured.
Node mapping : SU1 on SC-1, SU2 on SC-2, SU3 on PL-3, SU4,SU5 on PL-4.
While running the campaign, smf performs lock,lock-in of the activation units
i.e SUs. The SIs for SU3 are not removed though SU3 is in locked-state.
Subsequent unlock-in,unlock of SU3 fails.
/var/log/messages of active ctrl- SC-1 shows
============================================
Feb 3 22:45:14 linux-xc76 osafamfd[20055]: WA SIs still assigned to this SU
Feb 3 22:45:16 linux-xc76 osafamfd[20055]: WA SIs still assigned to this SU
Feb 3 22:45:18 linux-xc76 osafamfd[20055]: WA SIs still assigned to this SU
Feb 3 22:45:20 linux-xc76 osafamfd[20055]: WA SIs still assigned to this SU
Feb 3 22:45:23 linux-xc76 osafamfd[20055]: WA SIs still assigned to this SU
Feb 3 22:45:23 linux-xc76 osafsmfd[20081]: ER Fail to invoke admin operation,
too many SA_AIS_ERR_TRY_AGAIN, giving up.
dn=[safSu=SU3,safSg=SGONE,safApp=NWAYAPP], opId=[3]
Feb 3 22:45:23 linux-xc76 osafsmfd[20081]: ER Failed to call admin operation 3
on safSu=SU3,safSg=SGONE,safApp=NWAYAPP
Feb 3 22:45:23 linux-xc76 osafsmfd[20081]: ER Failed to Terminate activation
units in step=safSmfStep=0003
Feb 3 22:45:23 linux-xc76 osafsmfd[20081]: ER Step undoing failed
Feb 3 22:45:23 linux-xc76 osafsmfd[20081]: ER Step safSmfStep=0003 in procedure
safSmfProc=amfClusterProc-1 failed, step result 5
Feb 3 22:45:23 linux-xc76 osafsmfd[20081]: NO CAMP: Procedure
safSmfProc=amfClusterProc-1 returned FAILED
SU Assignments brief:
=======================
safSISU=safSu=SU1\,safSg=SGONE\,safApp=NWAYAPP,safSi=NWAYSI3,safApp=NWAYAPP
saAmfSISUHAState=ACTIVE(1)
safSISU=safSu=SU1\,safSg=SGONE\,safApp=NWAYAPP,safSi=NWAYSI2,safApp=NWAYAPP
saAmfSISUHAState=STANDBY(2)
safSISU=safSu=SU3\,safSg=SGONE\,safApp=NWAYAPP,safSi=NWAYSI5,safApp=NWAYAPP
saAmfSISUHAState=QUIESCED(3)
safSISU=safSu=SU4\,safSg=SGONE\,safApp=NWAYAPP,safSi=NWAYSI5,safApp=NWAYAPP
saAmfSISUHAState=ACTIVE(1)
safSISU=safSu=SU2\,safSg=SGONE\,safApp=NWAYAPP,safSi=NWAYSI1,safApp=NWAYAPP
saAmfSISUHAState=ACTIVE(1)
SU States:
==========
safSu=SU3,safSg=SGONE,safApp=NWAYAPP
saAmfSUAdminState=LOCKED(2)
saAmfSUOperState=ENABLED(1)
saAmfSUPresenceState=INSTANTIATED(3)
saAmfSUReadinessState=OUT-OF-SERVICE(1)
changed 4 months ago by bertil ¶
■owner changed from ingber to ravisekhar
■component changed from saf/smfsv to saf/avsv
I beleave this is an AMF problem. SMF only uses the AMF admin ops (lock, unlock
etc).
---
Sent from sourceforge.net because [email protected] 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.------------------------------------------------------------------------------
BPM Camp - Free Virtual Workshop May 6th at 10am PDT/1PM EDT
Develop your own process in accordance with the BPMN 2 standard
Learn Process modeling best practices with Bonita BPM through live exercises
http://www.bonitasoft.com/be-part-of-it/events/bpm-camp-virtual- event?utm_
source=Sourceforge_BPM_Camp_5_6_15&utm_medium=email&utm_campaign=VA_SF
_______________________________________________
Opensaf-tickets mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
