- **status**: review --> fixed
- **Comment**:
changeset: 5883:616211c61bab
branch: opensaf-4.4.x
parent: 5880:68d02af29aaa
user: praveen.malv...@oracle.com
date: Mon Sep 22 15:37:32 2014 +0530
summary: amfnd : do not send susi success response during su-failover
[#1015]
changeset: 5884:6424ba2339cd
branch: opensaf-4.5.x
parent: 5881:5eb83933838d
user: praveen.malv...@oracle.com
date: Mon Sep 22 15:37:42 2014 +0530
summary: amfnd : do not send susi success response during su-failover
[#1015]
changeset: 5885:9729ed4ff681
tag: tip
parent: 5882:af237b5d8bc8
user: praveen.malv...@oracle.com
date: Mon Sep 22 15:37:51 2014 +0530
summary: amfnd : do not send susi success response during su-failover
[#1015]
[staging:616211]
[staging:6424ba]
[staging:9729ed]
---
** [tickets:#1015] si's are not assigned to su after si-swap with fault**
**Status:** fixed
**Milestone:** 4.4.1
**Created:** Tue Aug 26, 2014 09:22 AM UTC by surender khetavath
**Last Updated:** Mon Sep 01, 2014 11:53 AM UTC
**Owner:** Praveen
changeset : 5608
model : 2n
configuration : 1App,1SG,2SUs with 4comps each, 4SIs with 1 CSI each
si-si deps configured as SI1 is sponsor to SI2,3,&4.
SU1 is active, SU2 is standby.
SU1 is mapped to pl-3 and SU2 to pl-4
saAmfSGAutoRepair=1(True)
SuFailover=1(True)
Test:
----
perform si-swap.
Make a dependent si reject the new active assignment.
/var/log/messages on pl-4:
-----------------------------
Aug 26 14:48:12 PL-4 osafamfnd[18496]: NO
'safComp=COMP3,safSu=SU2,safSg=SG,safApp=test2nApp' faulted due to
'csiSetcallbackFailed' : Recovery is 'suFailover'
Aug 26 14:48:12 PL-4 osafamfnd[18496]: NO Terminating components of
'safSu=SU2,safSg=SG,safApp=test2nApp'(abruptly & unordered)
Aug 26 14:48:12 PL-4 osafamfnd[18496]: NO 'safSu=SU2,safSg=SG,safApp=test2nApp'
Presence State INSTANTIATED => TERMINATING
Aug 26 14:48:12 PL-4 osafamfnd[18496]: NO Assigned 'safSi=SI2,safApp=test2nApp'
ACTIVE to 'safSu=SU2,safSg=SG,safApp=test2nApp'
Aug 26 14:48:12 PL-4 osafamfnd[18496]: NO Assigned 'safSi=SI4,safApp=test2nApp'
ACTIVE to 'safSu=SU2,safSg=SG,safApp=test2nApp'
Aug 26 14:48:12 PL-4 osafamfnd[18496]: NO Assigned 'safSi=SI3,safApp=test2nApp'
ACTIVE to 'safSu=SU2,safSg=SG,safApp=test2nApp'
Aug 26 14:48:12 PL-4 osafamfnd[18496]: NO 'safSu=SU2,safSg=SG,safApp=test2nApp'
Presence State TERMINATING => UNINSTANTIATED
Aug 26 14:48:12 PL-4 osafamfnd[18496]: NO Terminated all components in
'safSu=SU2,safSg=SG,safApp=test2nApp'
Aug 26 14:48:12 PL-4 osafamfnd[18496]: NO Informing director of sufailover
Aug 26 14:48:12 PL-4 osafamfnd[18496]: ER susi_assign_evh:
'safSi=SI1,safApp=test2nApp' is not assigned to
'safSu=SU2,safSg=SG,safApp=test2nApp'
Aug 26 14:48:12 PL-4 osafamfnd[18496]: ER susi_assign_evh:
'safSi=SI2,safApp=test2nApp' is not assigned to
'safSu=SU2,safSg=SG,safApp=test2nApp'
Aug 26 14:48:12 PL-4 osafamfnd[18496]: ER susi_assign_evh:
'safSi=SI3,safApp=test2nApp' is not assigned to
'safSu=SU2,safSg=SG,safApp=test2nApp'
Aug 26 14:48:12 PL-4 osafamfnd[18496]: ER susi_assign_evh:
'safSi=SI4,safApp=test2nApp' is not assigned to
'safSu=SU2,safSg=SG,safApp=test2nApp'
Aug 26 14:48:12 PL-4 osafamfnd[18496]: NO Repair request for
'safSu=SU2,safSg=SG,safApp=test2nApp'
Aug 26 14:48:12 PL-4 osafamfnd[18496]: NO 'safSu=SU2,safSg=SG,safApp=test2nApp'
Presence State UNINSTANTIATED => UNINSTANTIATED
Aug 26 14:48:12 PL-4 osafamfnd[18496]: NO 'safSu=SU2,safSg=SG,safApp=test2nApp'
Presence State UNINSTANTIATED => INSTANTIATING
Aug 26 14:48:12 PL-4 osafamfnd[18496]: NO 'safSu=SU2,safSg=SG,safApp=test2nApp'
Presence State INSTANTIATING => INSTANTIATED
safSi=SI3,safApp=test2nApp
saAmfSIAdminState=UNLOCKED(1)
saAmfSIAssignmentState=UNASSIGNED(1)
safSi=SI1,safApp=test2nApp
saAmfSIAdminState=UNLOCKED(1)
saAmfSIAssignmentState=UNASSIGNED(1)
safSi=SI2,safApp=test2nApp
saAmfSIAdminState=UNLOCKED(1)
saAmfSIAssignmentState=UNASSIGNED(1)
safSi=SI4,safApp=test2nApp
saAmfSIAdminState=UNLOCKED(1)
saAmfSIAssignmentState=UNASSIGNED(1)
/etc/init.d/opensafd status
safSISU=safSu=SC-1\,safSg=NoRed\,safApp=OpenSAF,safSi=NoRed2,safApp=OpenSAF
saAmfSISUHAState=ACTIVE(1)
safSISU=safSu=SC-1\,safSg=2N\,safApp=OpenSAF,safSi=SC-2N,safApp=OpenSAF
saAmfSISUHAState=ACTIVE(1)
safSISU=safSu=SC-2\,safSg=2N\,safApp=OpenSAF,safSi=SC-2N,safApp=OpenSAF
saAmfSISUHAState=STANDBY(2)
safSISU=safSu=SC-2\,safSg=NoRed\,safApp=OpenSAF,safSi=NoRed1,safApp=OpenSAF
saAmfSISUHAState=ACTIVE(1)
safSISU=safSu=PL-3\,safSg=NoRed\,safApp=OpenSAF,safSi=NoRed3,safApp=OpenSAF
saAmfSISUHAState=ACTIVE(1)
safSISU=safSu=PL-4\,safSg=NoRed\,safApp=OpenSAF,safSi=NoRed5,safApp=OpenSAF
saAmfSISUHAState=ACTIVE(1)
safSISU=safSu=PL-5\,safSg=NoRed\,safApp=OpenSAF,safSi=NoRed4,safApp=OpenSAF
saAmfSISUHAState=ACTIVE(1)
safSu=SU1,safSg=SG,safApp=test2nApp
saAmfSUAdminState=UNLOCKED(1)
saAmfSUOperState=ENABLED(1)
saAmfSUPresenceState=INSTANTIATED(3)
saAmfSUReadinessState=IN-SERVICE(2)
safSu=SU2,safSg=SG,safApp=test2nApp
saAmfSUAdminState=UNLOCKED(1)
saAmfSUOperState=ENABLED(1)
saAmfSUPresenceState=INSTANTIATED(3)
saAmfSUReadinessState=IN-SERVICE(2)
---
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.------------------------------------------------------------------------------
Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer
Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports
Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper
Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer
http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk
_______________________________________________
Opensaf-tickets mailing list
Opensaf-tickets@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
