For SI operation AMF is responding immediately.
There is already one ticket #505 for this.
Also for SHUTDOWN operation on SI, AMF PR document is not properly updated.
So for this ticket AMF PR doc will be updated with following documentation:
1) During shutdown operation on SI if component faults and it leads to
component-failover, sufailover or nodefailover, then shutdown operation will
not be completed and SI will remain in assigned state.
2) There is, however, one deviation when SI dependency is configured and
component's fault leads to component-failover. In this case SI will go to
locked state with no assignments.
With above documentation this ticket will be marked as duplicate of #505 for
the problem of immediate reply for admin operation on SI.
---
** [tickets:#672] SI doesn't go to locked state after shutdown having
dependencies**
**Status:** review
**Created:** Wed Dec 18, 2013 09:17 AM UTC by surender khetavath
**Last Updated:** Fri Jan 10, 2014 11:44 AM UTC
**Owner:** Praveen
changeset : 4733
model : 2n
configuration : 1App,1SG,2SUs with 4comps each, 4SIs with 1 CSI each
si-si deps configured as SI1 sponsor for SI2,3,4 resp
SU1 is active, SU2 is standby.
SU1 is mapped to pl-3 and SU2 to pl-4
saAmfSGAutoRepair=1(True)
SuFailover=1(True)
Test:
1.shutdown SI1(sponsor)
2.reject the Quiescingcompletecbk
3.unlock
console output:
error - saImmOmAdminOperationInvoke_2 admin-op RETURNED: SA_AIS_ERR_NO_OP (28)
error-string: SI unlock of safSi=SI1,safApp=test2nApp failed, already unlocked
immfind | grep safDep
safDepend=safSi=SI1\,safApp=test2nApp,safSi=SI2,safApp=test2nApp
safDepend=safSi=SI1\,safApp=test2nApp,safSi=SI3,safApp=test2nApp
safDepend=safSi=SI1\,safApp=test2nApp,safSi=SI4,safApp=test2nApp
/var/log/messages on pl-3:
Dec 18 14:23:12 PL-3 osafamfnd[3491]: NO Assigning 'safSi=SI1,safApp=test2nApp'
QUIESCING to 'safSu=SU1,safSg=SG,safApp=test2nApp'
Dec 18 14:23:22 PL-3 osafamfnd[3491]: NO saAmfSUFailover is true for
'safSu=SU1,safSg=SG,safApp=test2nApp'
Dec 18 14:23:22 PL-3 osafamfnd[3491]: NO
'safComp=COMP1,safSu=SU1,safSg=SG,safApp=test2nApp' faulted due to
'qscingCompleteTimeout' : Recovery is 'suFailover'
Dec 18 14:23:22 PL-3 osafamfnd[3491]: NO Terminating components of
'safSu=SU1,safSg=SG,safApp=test2nApp'(abruptly & unordered)
Dec 18 14:23:22 PL-3 osafamfnd[3491]: NO 'safSu=SU1,safSg=SG,safApp=test2nApp'
Presence State INSTANTIATED => TERMINATING
Dec 18 14:23:22 PL-3 logger: CLC-CLI spawnd cleanup for
safComp=COMP3,safSu=SU1,safSg=SG,safApp=test2nApp
Dec 18 14:23:22 PL-3 logger: CLC-CLI spawnd cleanup for
safComp=COMP2,safSu=SU1,safSg=SG,safApp=test2nApp
Dec 18 14:23:22 PL-3 logger: CLC-CLI spawnd cleanup for
safComp=COMP4,safSu=SU1,safSg=SG,safApp=test2nApp
Dec 18 14:23:22 PL-3 logger: CLC-CLI spawnd cleanup for
safComp=COMP1,safSu=SU1,safSg=SG,safApp=test2nApp
Dec 18 14:23:22 PL-3 osafamfnd[3491]: NO 'safSu=SU1,safSg=SG,safApp=test2nApp'
Presence State TERMINATING => UNINSTANTIATED
Dec 18 14:23:22 PL-3 osafamfnd[3491]: NO Terminated all components in
'safSu=SU1,safSg=SG,safApp=test2nApp'
Dec 18 14:23:22 PL-3 osafamfnd[3491]: NO Informing director of sufailover
---
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.
------------------------------------------------------------------------------
CenturyLink Cloud: The Leader in Enterprise Cloud Services.
Learn Why More Businesses Are Choosing CenturyLink Cloud For
Critical Workloads, Development Environments & Everything In Between.
Get a Quote or Start a Free Trial Today.
http://pubads.g.doubleclick.net/gampad/clk?id=119420431&iu=/4140/ostg.clktrk
_______________________________________________
Opensaf-tickets mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
