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


---

** [tickets:#390] Controller moves to disabled state during sponser SI unlock 
followed by controller switchover.**

**Status:** unassigned
**Milestone:** future
**Created:** Fri May 31, 2013 04:30 AM UTC by Nagendra Kumar
**Last Updated:** Fri May 31, 2013 04:30 AM UTC
**Owner:** nobody

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

Cgset : 3406


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 parent sponser SI1 followed by controller 
failover(kill amfd)


amf-adm lock safSi=SI1,safApp=testNActiveApp ; sleep 1 ; kill -9 2817


Immediately observed the below SUSI HA states:-


safSISU=safSu=SU2\,safSg=SG\,safApp=testNActiveApp,safSi=SI6,safApp=testNActiveApp


saAmfSISUHAState=ACTIVE(1)


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


saAmfSISUHAState=ACTIVE(1)


safSISU=safSu=SU2\,safSg=SG\,safApp=testNActiveApp,safSi=SI2,safApp=testNActiveApp


saAmfSISUHAState=ACTIVE(1)


safSISU=safSu=SU4\,safSg=SG\,safApp=testNActiveApp,safSi=SI4,safApp=testNActiveApp


saAmfSISUHAState=ACTIVE(1)


safSISU=safSu=SU4\,safSg=SG\,safApp=testNActiveApp,safSi=SI5,safApp=testNActiveApp


saAmfSISUHAState=ACTIVE(1)


safSISU=safSu=SU4\,safSg=SG\,safApp=testNActiveApp,safSi=SI6,safApp=testNActiveApp


saAmfSISUHAState=ACTIVE(1)


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


saAmfSISUHAState=ACTIVE(1)



After tolerance timer expires , observed that all SIs moved to unassigned.


3. On SC-1, performed unlock of sponser SI1 followed by controller switchover 
but it failed with below error message:-


amf-adm unlock safSi=SI1,safApp=testNActiveApp ; sleep 1 ; immadm -o 7 
safSi=SC-2N,safApp=OpenSAF


error - command timed out (alarm)
linux-xc76:~ #


After this observed that SC-1 node moves to disabled state.
safAmfNode=SC-1,safAmfCluster=myAmfCluster
saAmfNodeAdminState=UNLOCKED(1)
saAmfNodeOperState=DISABLED(2)


Hence no SUSI assignments for SU3 running on SC-1


/var/log/messages of SC-1 (standby) was printing the below messages:-
======
r 6 18:21:21 linux-xc76 osafimmnd[2720]: Assuming reply for adminOp 
906238099458 arrived before request.
Mar 6 18:21:36 linux-xc76 osafimmnd[2720]: Assuming reply for adminOp 
906238099473 arrived before request.
Mar 6 18:21:51 linux-xc76 osafimmnd[2720]: Assuming reply for adminOp 
906238099488 arrived before request.
Mar 6 18:22:05 linux-xc76 osafimmnd[2720]: Assuming reply for adminOp 
906238099502 arrived before request.
Mar 6 18:22:06 linux-xc76 osafimmnd[2720]: Assuming reply for adminOp 
906238099503 arrived before request.
Mar 6 18:22:09 linux-xc76 osafimmnd[2720]: Assuming reply for adminOp 
906238099506 arrived before request.
Mar 6 18:22:10 linux-xc76 osafimmnd[2720]: Assuming reply for adminOp 
906238099507 arrived before request.
Mar 6 18:22:16 linux-xc76 osafimmnd[2720]: Assuming reply for adminOp 
906238099513 arrived before request.


/var/log/messages of SC-2 (active)
======
Mar 6 18:21:21 linux-xc76 osafamfd[18549]: safSi=SC-2N,safApp=OpenSAF SWAP 
failed - SG not stable (1)
Mar 6 18:21:22 linux-xc76 osafamfd[18549]: safSi=SC-2N,safApp=OpenSAF SWAP 
failed - SG not stable (1)
Mar 6 18:21:23 linux-xc76 osafamfd[18549]: safSi=SC-2N,safApp=OpenSAF SWAP 
failed - SG not stable (1)
Mar 6 18:21:24 linux-xc76 osafamfd[18549]: safSi=SC-2N,safApp=OpenSAF SWAP 
failed - SG not stable (1)
Mar 6 18:21:25 linux-xc76 osafamfd[18549]: safSi=SC-2N,safApp=OpenSAF SWAP 
failed - SG not stable (1)


Assginments after step3:-


SU1 - SI1 SI2 SI3 Active
SU2 - SI1 SI2 SI3 Active
SU3 - No assignments since SC-1 on which SU3 was running moves to disabled 
state 
SU4 - SI4 SI5 SI6 Active
SU5 - SI4 SI5 SI6 Active


safSi=SI1,safApp=testNActiveApp


saAmfSIAdminState=UNLOCKED(1)
saAmfSIAssignmentState=FULLY_ASSIGNED(2)


safSi=SI2,safApp=testNActiveApp


saAmfSIAdminState=UNLOCKED(1)
saAmfSIAssignmentState=FULLY_ASSIGNED(2)


safSi=SI3,safApp=testNActiveApp


saAmfSIAdminState=UNLOCKED(1)
saAmfSIAssignmentState=FULLY_ASSIGNED(2)


safSi=SI4,safApp=testNActiveApp


saAmfSIAdminState=UNLOCKED(1)
saAmfSIAssignmentState=FULLY_ASSIGNED(2)


afSi=SI5,safApp=testNActiveApp


saAmfSIAdminState=UNLOCKED(1)
saAmfSIAssignmentState=FULLY_ASSIGNED(2)


safSi=SI6,safApp=testNActiveApp


saAmfSIAdminState=UNLOCKED(1)
saAmfSIAssignmentState=FULLY_ASSIGNED(2)


safSi=SI7,safApp=testNActiveApp


saAmfSIAdminState=UNLOCKED(1)
saAmfSIAssignmentState=UNASSIGNED(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