- **Type**: defect --> enhancement


---

** [tickets:#391] In nwayactive, Lock of all sponsors SIs along with controller 
failover makes SG unstable.**

**Status:** unassigned
**Milestone:** future
**Created:** Fri May 31, 2013 05:08 AM UTC by Nagendra Kumar
**Last Updated:** Fri Aug 30, 2013 10:06 AM UTC
**Owner:** nobody

Migrated from http://devel.opensaf.org/ticket/2566

Cgset : 3406


In nway active model, Lock of all sponsors SIs along with controller failover 
makes SG unstable.


Configuration:-
================
Nway Active model
5 Node setup
5SUs, 2 component per SU with same compType
7SIs, 1CSIs per SI, No SIRankedSU configured.
saAmfSGMaxActiveSIsperSU=3
saAmfSGNumPrefInserviceSUs=8
saAmfSIPrefActiveAssignments=2


SU2 spawned on PL-4
SU3 spawned on SC-1
SU4 spawned on SC-2
SU1 and SU5 spawned on PL-3


SI-SI dependency configured in binary form as shown below:-


SI1 is sponser for SI2(tol=1min) and SI3(tol=0)
SI2 is sponser for SI4(tol=1min) and SI5(tol=0)
SI3 is sponser for SI6(tol=1min) and SI7(tol=0)


1. Performed unlock-in and unlock of each SUs in the order SU1,SU2,SU3,SU4,SU5.
Initial assignments are:-


SU1 - SI1 SI2 SI3 Active
SU2 - SI1 SI2 SI3 Active
SU3 - SI4 SI5 SI6 Active
SU4 - SI4 SI5 SI6 Active
SU5 - SI7 Active


2. On SC-1, performed lock of all sponser SI1s followed by controller 
failover(kill amfd)


amf-adm lock safSi=SI1,safApp=testNActiveApp ; amf-adm lock 
safSi=SI2,safApp=testNActiveApp ; amf-adm lock safSi=SI3,safApp=testNActiveApp 
; kill -9 3707


error - saImmOmAdminOperationInvoke_2 admin-op RETURNED: 
SA_AIS_ERR_BAD_OPERATION (20)
error - saImmOmAdminOperationInvoke_2 admin-op RETURNED: 
SA_AIS_ERR_BAD_OPERATION (20)


Here SI1 got locked but lock of SI2 and SI3 failed with 
SA_AIS_ERR_BAD_OPERATION.


SC-1 /var/log/messages prints the below message after performing above 
operations.


Mar 7 11:32:19 linux-xc76 osafamfnd[3717]: Assigned 
'safSi=SI6,safApp=testNActiveApp' ACTIVE to 
'safSu=SU3,safSg=SG,safApp=testNActiveApp'
Mar 7 11:33:27 linux-xc76 osafamfd[3707]: SI lock of 
safSi=SI2,safApp=testNActiveApp failed, SG not stable
Mar 7 11:33:27 linux-xc76 osafamfd[3707]: 'safSi=SI2,safApp=testNActiveApp' 
other semantics...
Mar 7 11:33:27 linux-xc76 osafamfd[3707]: SI lock of 
safSi=SI3,safApp=testNActiveApp failed, SG not stable
Mar 7 11:33:27 linux-xc76 osafamfd[3707]: 'safSi=SI3,safApp=testNActiveApp' 
other semantics...
Mar 7 11:33:27 linux-xc76 osafamfnd[3717]: AMF director unexpectedly crashed
Mar 7 11:33:27 linux-xc76 osafamfnd[3717]: Rebooting OpenSAF NodeId? = 131343 
EE Name = , Reason: local AVD down(Adest) or both AVD down(Vdest) received
Mar 7 11:33:27 linux-xc76 osaflckd[3804]: Event from unknown glnd: node_id 
131599
Mar 7 11:33:27 linux-xc76 osaflckd[3804]: Event from unknown glnd: node_id 
131855
Mar 7 11:33:27 linux-xc76 osaflckd[3804]: Event from unknown glnd: node_id 
132111


Also observed that SI1 has QUIESCED state for SU1 for ever.


SUSI HA States snap:-
======
linux-xc76:~ # amf-state siass ha
safSISU=safSu=SC-1\,safSg=NoRed?\,safApp=OpenSAF,safSi=NoRed?2,safApp=OpenSAF


saAmfSISUHAState=ACTIVE(1)


safSISU=safSu=SC-2\,safSg=NoRed?\,safApp=OpenSAF,safSi=NoRed?1,safApp=OpenSAF


saAmfSISUHAState=ACTIVE(1)


safSISU=safSu=SC-2\,safSg=2N\,safApp=OpenSAF,safSi=SC-2N,safApp=OpenSAF


saAmfSISUHAState=ACTIVE(1)


safSISU=safSu=PL-3\,safSg=NoRed?\,safApp=OpenSAF,safSi=NoRed?5,safApp=OpenSAF


saAmfSISUHAState=ACTIVE(1)


safSISU=safSu=PL-4\,safSg=NoRed?\,safApp=OpenSAF,safSi=NoRed?4,safApp=OpenSAF


saAmfSISUHAState=ACTIVE(1)


safSISU=safSu=PL-5\,safSg=NoRed?\,safApp=OpenSAF,safSi=NoRed?3,safApp=OpenSAF


saAmfSISUHAState=ACTIVE(1)


safSISU=safSu=SU1\,safSg=SG\,safApp=testNActiveApp,safSi=SI1,safApp=testNActiveApp


saAmfSISUHAState=QUIESCED(3)


safSISU=safSu=SC-1\,safSg=2N\,safApp=OpenSAF,safSi=SC-2N,safApp=OpenSAF


saAmfSISUHAState=STANDBY(2)


SI States:-
======
safSi=SI1,safApp=testNActiveApp


saAmfSIAdminState=LOCKED(2)
saAmfSIAssignmentState=UNASSIGNED(1)


safSi=SI2,safApp=testNActiveApp


saAmfSIAdminState=UNLOCKED(1)
saAmfSIAssignmentState=UNASSIGNED(1)


safSi=SI4,safApp=testNActiveApp


saAmfSIAdminState=UNLOCKED(1)
saAmfSIAssignmentState=UNASSIGNED(1)


safSi=SI3,safApp=testNActiveApp


saAmfSIAdminState=UNLOCKED(1)
saAmfSIAssignmentState=UNASSIGNED(1)


safSi=SI5,safApp=testNActiveApp


saAmfSIAdminState=UNLOCKED(1)
saAmfSIAssignmentState=UNASSIGNED(1)


safSi=SI6,safApp=testNActiveApp


saAmfSIAdminState=UNLOCKED(1)
saAmfSIAssignmentState=UNASSIGNED(1)


safSi=SI7,safApp=testNActiveApp


saAmfSIAdminState=UNLOCKED(1)
saAmfSIAssignmentState=UNASSIGNED(1)


Node states:-
========
safAmfNode=SC-2,safAmfCluster=myAmfCluster


saAmfNodeAdminState=UNLOCKED(1)
saAmfNodeOperState=ENABLED(1)


safAmfNode=SC-1,safAmfCluster=myAmfCluster


saAmfNodeAdminState=UNLOCKED(1)
saAmfNodeOperState=ENABLED(1)


safAmfNode=PL-5,safAmfCluster=myAmfCluster


saAmfNodeAdminState=UNLOCKED(1)
saAmfNodeOperState=ENABLED(1)


safAmfNode=PL-4,safAmfCluster=myAmfCluster


saAmfNodeAdminState=UNLOCKED(1)
saAmfNodeOperState=ENABLED(1)


safAmfNode=PL-3,safAmfCluster=myAmfCluster


saAmfNodeAdminState=UNLOCKED(1)
saAmfNodeOperState=ENABLED(1)





---

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.
------------------------------------------------------------------------------
Don't Limit Your Business. Reach for the Cloud.
GigeNET's Cloud Solutions provide you with the tools and support that
you need to offload your IT needs and focus on growing your business.
Configured For All Businesses. Start Your Cloud Today.
https://www.gigenetcloud.com/
_______________________________________________
Opensaf-tickets mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets

Reply via email to