- **Milestone**: 4.5.2 --> 4.6.2
---
** [tickets:#1479] amf: issue with quiesced state failure during admin op.**
**Status:** assigned
**Milestone:** 4.6.2
**Labels:** Quiesced
**Created:** Tue Sep 15, 2015 04:59 AM UTC by Praveen
**Last Updated:** Tue Sep 15, 2015 05:00 AM UTC
**Owner:** Praveen
**Attachments:**
-
[traces.tgz](https://sourceforge.net/p/opensaf/tickets/1479/attachment/traces.tgz)
(101.3 kB; application/x-compressed)
-
[AppConfig-2N_2Comp_2SI_2CSI.xml](https://sourceforge.net/p/opensaf/tickets/1479/attachment/AppConfig-2N_2Comp_2SI_2CSI.xml)
(15.7 kB; text/xml)
During admin operation like si-swap, lock on su and lock on si, if any comp
fails with component failover recovery then AMF removes assignment from the
failed SU after performing failover of the SU.
Since only faulty component is cleaned up, AMF should perform failover only
after removing assignments from other healthy components of the failed SU.
Attached are the traces and configuration to reproduce the problem.
Since most of the time SUs are hosted on different nodes, the problem may not
become visible.Hosting two SUs on the same node clearly shows it.
Observed in 2N and NWay model. But may be applicable to other red models.
messages when SUs hosted on same node:
Sep 15 08:38:15 CON-PC osafamfnd[4442]: NO Assigning 'all (2) SIs' QUIESCED to
'safSu=SU1,safSg=AmfDemo,safApp=AmfDemo1'
Sep 15 08:38:15 CON-PC osafamfnd[4442]: NO Assigning
'safSi=AmfDemo,safApp=AmfDemo1' QUIESCED to
'safSu=SU1,safSg=AmfDemo,safApp=AmfDemo1'
Sep 15 08:38:15 CON-PC osafamfnd[4442]: NO Assigning
'safSi=AmfDemo1,safApp=AmfDemo1' QUIESCED to
'safSu=SU1,safSg=AmfDemo,safApp=AmfDemo1'
Sep 15 08:38:15 CON-PC amf_demo[5035]: =====CSI SET====>
Sep 15 08:38:15 CON-PC amf_demo[5035]:
Comp---->:'safComp=AmfDemo1,safSu=SU1,safSg=AmfDemo,safApp=AmfDemo1'
Sep 15 08:38:15 CON-PC amf_demo[5035]: CSI FLAG----->:SA_AMF_CSI_TARGET_ALL
Sep 15 08:38:15 CON-PC amf_demo[5035]: HAState---->:Quiesced
Sep 15 08:38:15 CON-PC amf_demo[5035]: <================
Sep 15 08:38:15 CON-PC amf_demo[5035]: Waiting for the flag being set
Sep 15 08:38:15 CON-PC amf_demo[5050]: =====CSI SET====>
Sep 15 08:38:15 CON-PC amf_demo[5050]:
Comp---->:'safComp=AmfDemo,safSu=SU1,safSg=AmfDemo,safApp=AmfDemo1'
Sep 15 08:38:15 CON-PC amf_demo[5050]: CSI FLAG----->:SA_AMF_CSI_TARGET_ALL
Sep 15 08:38:15 CON-PC amf_demo[5050]: HAState---->:Quiesced
Sep 15 08:38:15 CON-PC amf_demo[5050]: <================
Sep 15 08:38:15 CON-PC amf_demo[5050]: Waiting for the flag being set
Sep 15 08:38:24 CON-PC osafamfnd[4442]: NO saAmfCompDisableRestart is true for
'safComp=AmfDemo,safSu=SU1,safSg=AmfDemo,safApp=AmfDemo1'
Sep 15 08:38:24 CON-PC osafamfnd[4442]: NO recovery action 'comp restart'
escalated to 'comp failover'
Sep 15 08:38:24 CON-PC osafamfnd[4442]: NO Performing failover of
'safSu=SU1,safSg=AmfDemo,safApp=AmfDemo1' (SU failover count: 3)
Sep 15 08:38:24 CON-PC osafamfnd[4442]: NO
'safComp=AmfDemo,safSu=SU1,safSg=AmfDemo,safApp=AmfDemo1' recovery action
escalated from 'componentRestart' to 'componentFailover'
Sep 15 08:38:24 CON-PC osafamfnd[4442]: NO
'safComp=AmfDemo,safSu=SU1,safSg=AmfDemo,safApp=AmfDemo1' faulted due to
'csiSetcallbackFailed' : Recovery is 'componentFailover'
Sep 15 08:38:24 CON-PC osafamfnd[4442]: NO
'safSu=SU1,safSg=AmfDemo,safApp=AmfDemo1' Presence State INSTANTIATED =>
TERMINATING
Sep 15 08:38:24 CON-PC logger: 5135:CLEANUP PI START =====>:
safComp=AmfDemo,safSu=SU1,safSg=AmfDemo,safApp=AmfDemo1
Sep 15 08:38:24 CON-PC logger: CLEANUP PI END:
safComp=AmfDemo,safSu=SU1,safSg=AmfDemo,safApp=AmfDemo1 <=======
Sep 15 08:38:24 CON-PC osafamfnd[4442]: NO Assigned
'safSi=AmfDemo,safApp=AmfDemo1' QUIESCED to
'safSu=SU1,safSg=AmfDemo,safApp=AmfDemo1'
Sep 15 08:38:24 CON-PC osafamfnd[4442]: NO Assigned
'safSi=AmfDemo1,safApp=AmfDemo1' QUIESCED to
'safSu=SU1,safSg=AmfDemo,safApp=AmfDemo1'
Sep 15 08:38:24 CON-PC osafamfnd[4442]: NO Assigned 'all SIs' QUIESCED of
'safSu=SU1,safSg=AmfDemo,safApp=AmfDemo1'
Sep 15 08:38:24 CON-PC osafamfnd[4442]: NO Assigning 'all (2) SIs' ACTIVE to
'safSu=SU2,safSg=AmfDemo,safApp=AmfDemo1'
Sep 15 08:38:24 CON-PC osafamfnd[4442]: NO Assigning
'safSi=AmfDemo,safApp=AmfDemo1' ACTIVE to
'safSu=SU2,safSg=AmfDemo,safApp=AmfDemo1'
Sep 15 08:38:24 CON-PC osafamfnd[4442]: NO Assigning
'safSi=AmfDemo1,safApp=AmfDemo1' ACTIVE to
'safSu=SU2,safSg=AmfDemo,safApp=AmfDemo1'
Sep 15 08:38:24 CON-PC amf_demo[4887]: =====CSI SET====>
Sep 15 08:38:24 CON-PC amf_demo[4887]:
Comp---->:'safComp=AmfDemo,safSu=SU2,safSg=AmfDemo,safApp=AmfDemo1'
Sep 15 08:38:24 CON-PC amf_demo[4887]: CSI FLAG----->:SA_AMF_CSI_TARGET_ALL
Sep 15 08:38:24 CON-PC amf_demo[4887]: HAState---->:Active
Sep 15 08:38:24 CON-PC amf_demo[4887]: <================
Sep 15 08:38:24 CON-PC amf_demo[4887]: Waiting for the flag being set
Sep 15 08:38:24 CON-PC amf_demo[4872]: =====CSI SET====>
Sep 15 08:38:24 CON-PC amf_demo[4872]:
Comp---->:'safComp=AmfDemo1,safSu=SU2,safSg=AmfDemo,safApp=AmfDemo1'
Sep 15 08:38:24 CON-PC amf_demo[4872]: CSI FLAG----->:SA_AMF_CSI_TARGET_ALL
Sep 15 08:38:24 CON-PC amf_demo[4872]: HAState---->:Active
Sep 15 08:38:24 CON-PC amf_demo[4872]: <================
Sep 15 08:38:24 CON-PC amf_demo[4872]: Waiting for the flag being set
Sep 15 08:38:24 CON-PC osafamfnd[4442]: NO Assigned
'safSi=AmfDemo,safApp=AmfDemo1' ACTIVE to
'safSu=SU2,safSg=AmfDemo,safApp=AmfDemo1'
Sep 15 08:38:24 CON-PC osafamfnd[4442]: NO Assigned
'safSi=AmfDemo1,safApp=AmfDemo1' ACTIVE to
'safSu=SU2,safSg=AmfDemo,safApp=AmfDemo1'
Sep 15 08:38:24 CON-PC osafamfnd[4442]: NO Assigned 'all SIs' ACTIVE of
'safSu=SU2,safSg=AmfDemo,safApp=AmfDemo1'
Sep 15 08:38:24 CON-PC osafamfnd[4442]: NO Removing 'all (2) SIs' from
'safSu=SU1,safSg=AmfDemo,safApp=AmfDemo1'
Sep 15 08:38:24 CON-PC osafamfnd[4442]: NO Removing
'safSi=AmfDemo,safApp=AmfDemo1' from 'safSu=SU1,safSg=AmfDemo,safApp=AmfDemo1'
Sep 15 08:38:24 CON-PC osafamfnd[4442]: NO Removing
'safSi=AmfDemo1,safApp=AmfDemo1' from 'safSu=SU1,safSg=AmfDemo,safApp=AmfDemo1'
Sep 15 08:38:24 CON-PC amf_demo[5035]: ========>CSI Remove=====>
Sep 15 08:38:24 CON-PC amf_demo[5035]:
Comp---->:'safComp=AmfDemo1,safSu=SU1,safSg=AmfDemo,safApp=AmfDemo1'
Sep 15 08:38:24 CON-PC amf_demo[5035]: CSI FLAG ----------->:
SA_AMF_CSI_TARGET_ALL
Sep 15 08:38:24 CON-PC amf_demo[5035]: <=======================
Sep 15 08:38:24 CON-PC osafamfnd[4442]: NO Removed
'safSi=AmfDemo,safApp=AmfDemo1' from 'safSu=SU1,safSg=AmfDemo,safApp=AmfDemo1'
Sep 15 08:38:24 CON-PC osafamfnd[4442]: NO Removed
'safSi=AmfDemo1,safApp=AmfDemo1' from 'safSu=SU1,safSg=AmfDemo,safApp=AmfDemo1'
Sep 15 08:38:24 CON-PC osafamfnd[4442]: NO Removed 'all SIs' from
'safSu=SU1,safSg=AmfDemo,safApp=AmfDemo1'
Sep 15 08:38:24 CON-PC amf_demo[5035]: saAmfResponse after lopp- 1
Sep 15 08:38:24 CON-PC logger: 5146:INSTANTIATE ======>:
safComp=AmfDemo,safSu=SU1,safSg=AmfDemo,safApp=AmfDemo1
Sep 15 08:38:24 CON-PC amf_demo[5156]:
'safComp=AmfDemo,safSu=SU1,safSg=AmfDemo,safApp=AmfDemo1' started
Sep 15 08:38:24 CON-PC logger: 5146:INSTANTIATON DONE:
safComp=AmfDemo,safSu=SU1,safSg=AmfDemo,safApp=AmfDemo1 <=======
Sep 15 08:38:24 CON-PC osafamfnd[4442]: NO
'safSu=SU1,safSg=AmfDemo,safApp=AmfDemo1' Presence State TERMINATING =>
INSTANTIATED
---
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.
------------------------------------------------------------------------------
_______________________________________________
Opensaf-tickets mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
