- **Milestone**: 4.5.2 --> 4.6.2
---
** [tickets:#326] amf: proxied SU's presence state hangs at INSTANTIATING
state.**
**Status:** unassigned
**Milestone:** 4.6.2
**Created:** Fri May 24, 2013 09:34 AM UTC by Praveen
**Last Updated:** Thu Aug 06, 2015 10:26 AM UTC
**Owner:** nobody
Migrated from http://devel.opensaf.org/ticket/2213.
setup: 1 controller
Model observed: TwoN
Configuration of proxy : 1 App, 1SG, 1SU, 1 proxy comps
Configuration of proxied : 1App, 1SG, 1SU, 1 proxied component with
saAmfCtCompCategory=12
The proxy code is modelled to respond to amf with ERR_FAILED_OP inside
SaAmfProxiedComponentInstantiateCallback?() api
By default, the SU's of proxy and proxied are in locked-instantiation state.
Scenario:
--------------------------------------------------------------------------------
Bringup the proxy and proxied configuration.
Do unlock-in and unlock of the proxy. The proxy should be up and running, and
the proxied registration should be successful.
Now do unlock-in of proxied SU. The below is the console output
console text:
amf-adm unlock-in safSu=SU_pxd,safSg=SG_pxd,safApp=pxd_App
error - saImmOmAdminOperationInvoke_2 FAILED: SA_AIS_ERR_TIMEOUT (5)
Retrying again gives the below output.
SLES11-SLOT-2:/home/surender/amf # amf-adm unlock-in
safSu=SU_pxd,safSg=SG_pxd,safApp=pxd_App
error - saImmOmAdminOperationInvoke_2 admin-op RETURNED: SA_AIS_ERR_TRY_AGAIN
(6)
SLES11-SLOT-2:/home/surender/amf # amf-adm unlock-in
safSu=SU_pxd,safSg=SG_pxd,safApp=pxd_App
error - saImmOmAdminOperationInvoke_2 admin-op RETURNED: SA_AIS_ERR_TRY_AGAIN
(6)
/var/log/messages output for above op's:
Oct 11 15:13:15 SLES11-SLOT-2 osafamfnd[3852]:
saAmfCtDefQuiescingCompleteTimeout for
'safVersion=4.0.0,safCompType=Comp_nored' initialized with
saAmfCtDefCallbackTimeout
Oct 11 15:13:15 SLES11-SLOT-2 osafamfnd[3852]:
'safSu=SU_mycomp,safSg=SG_mycomp,safApp=mycompApp' Presence State
UNINSTANTIATED => INSTANTIATING
Oct 11 15:13:16 SLES11-SLOT-2 osafamfnd[3852]:
'safSu=SU_mycomp,safSg=SG_mycomp,safApp=mycompApp' Presence State INSTANTIATING
=> INSTANTIATED
Oct 11 15:13:16 SLES11-SLOT-2 osafamfnd[3852]:
saAmfCtDefQuiescingCompleteTimeout for
'safVersion=4.0.0,safCompType=Comp_pxd_basetype' initialized with
saAmfCtDefCallbackTimeout
Oct 11 15:13:41 SLES11-SLOT-2 osafamfnd[3852]:
'safSu=SU_pxd,safSg=SG_pxd,safApp=pxd_App' Presence State UNINSTANTIATED =>
INSTANTIATING
Oct 11 15:15:55 SLES11-SLOT-2 osafamfd[3711]: Admin operation is already going
Oct 11 15:15:58 SLES11-SLOT-2 osafamfd[3711]: Admin operation is already going
SU states of proxy and proxied:
safSu=SU_mycomp,safSg=SG_mycomp,safApp=mycompApp
saAmfSUAdminState=UNLOCKED(1)
saAmfSUOperState=ENABLED(1)
saAmfSUPresenceState=INSTANTIATED(3)
saAmfSUReadinessState=IN-SERVICE(2)
safSu=SU_pxd,safSg=SG_pxd,safApp=pxd_App
saAmfSUAdminState=LOCKED(2)
saAmfSUOperState=ENABLED(1)
saAmfSUPresenceState=INSTANTIATING(2)
saAmfSUReadinessState=OUT-OF-SERVICE(1)
Comp state of proxy and proxied:
safComp=mycomp,safSu=SU_mycomp,safSg=SG_mycomp,safApp=mycompApp
saAmfCompOperState=ENABLED(1)
saAmfCompPresenceState=INSTANTIATED(3)
saAmfCompReadinessState=IN-SERVICE(2)
safComp=Comp_pxd,safSu=SU_pxd,safSg=SG_pxd,safApp=pxd_App
saAmfCompOperState=DISABLED(2)
saAmfCompPresenceState=INSTANTIATING(2)
saAmfCompReadinessState=OUT-OF-SERVICE(1)
Here the proxied comp is in DISABLED state, but its SU is in ENABLED state.
Also the proxied comp waits in Instantiating state indefinitely.
---
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
