This issue is reproducible on changeset: 4565:e8ae1895d8e3.
Attached 182.tgz contains Traces and 182.xml (reproducible configuration).
Steps to reproduce and observation:
1)immcfg -f 182.xml
2)amf-adm unlock-in and unlock safSu=SU1,safSg=AmfDemo,safApp=AmfDemo_NPI
error - saImmOmAdminOperationInvoke_2 admin-op RETURNED: SA_AIS_ERR_TIMEOUT
(5)
States of components after unlock operation:
safComp=AmfDemo,safSu=SU1,safSg=AmfDemo,safApp=AmfDemo_NPI
saAmfCompOperState=DISABLED(2)
saAmfCompPresenceState=INSTANTIATION-FAILED(6)
saAmfCompReadinessState=OUT-OF-SERVICE(1)
safComp=AmfDemo1,safSu=SU1,safSg=AmfDemo,safApp=AmfDemo_NPI
saAmfCompOperState=ENABLED(1)
saAmfCompPresenceState=UNINSTANTIATED(1)
saAmfCompReadinessState=OUT-OF-SERVICE(1)
Now correct instantiation script and perform repair.
3)amf-adm repaired safSu=SU1,safSg=AmfDemo,safApp=AmfDemo_NPI
Component Process :
root 17281 1 0 15:15 ? 00:00:00 /opt/amf_demo/npi/amf_comp_npi
root 17289 1 0 15:15 ? 00:00:00 /opt/amf_demo/npi/amf_comp_npi
safComp=AmfDemo,safSu=SU1,safSg=AmfDemo,safApp=AmfDemo_NPI
saAmfCompOperState=DISABLED(2)
saAmfCompPresenceState=INSTANTIATED(3)
saAmfCompReadinessState=OUT-OF-SERVICE(1)
safComp=AmfDemo1,safSu=SU1,safSg=AmfDemo,safApp=AmfDemo_NPI
saAmfCompOperState=ENABLED(1)
saAmfCompPresenceState=INSTANTIATED(3)
saAmfCompReadinessState=IN-SERVICE(2)
amf-state si all:
safSi=AmfDemo,safApp=AmfDemo_NPI
saAmfSIAdminState=UNLOCKED(1)
saAmfSIAssignmentState=PARTIALLY_ASSIGNED(3)
safSu=SU1,safSg=AmfDemo,safApp=AmfDemo_NPI
saAmfSUAdminState=UNLOCKED(1)
saAmfSUOperState=ENABLED(1)
saAmfSUPresenceState=INSTANTIATED(3)
saAmfSUReadinessState=IN-SERVICE(2)
At AMFND during repair operation request, only PI components are enabled in
amfnd/su.cc:
if (m_AVND_COMP_TYPE_IS_PREINSTANTIABLE(comp)) {
m_AVND_COMP_OPER_STATE_SET(comp, SA_AMF_OPERATIONAL_ENABLED);
avnd_di_uns32_upd_send(AVSV_SA_AMF_COMP, saAmfCompOperState_ID,
&comp->name, comp->oper);
}
---
** [tickets:#182] operational state of NPI component is not cleared to ENABLED
when SU admin repaired is performed**
**Status:** assigned
**Created:** Tue May 14, 2013 06:56 AM UTC by Nagendra Kumar
**Last Updated:** Fri Sep 06, 2013 01:17 PM UTC
**Owner:** Praveen
Migrated from http://devel.opensaf.org/ticket/2168
1. Brought NPI component to instantiation failure state for NPI component. SU
and component moved to instantiation failure state and operational state is set
to disabled.
2. After appropriate action is taken, admin repaired action on SU is performed.
3. SU's presence state moved to INSTANTIATED and operational state to ENABLED
and readiness state to IN_SERVICE as the component is successfully spawned.
But component's operational state is not changed to ENABLED and readiness is
not set to IN_SERVICE, which should be set accordingly
---
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.------------------------------------------------------------------------------
Android is increasing in popularity, but the open development platform that
developers love is also attractive to malware creators. Download this white
paper to learn more about secure code signing practices that can help keep
Android apps secure.
http://pubads.g.doubleclick.net/gampad/clk?id=65839951&iu=/4140/ostg.clktrk
_______________________________________________
Opensaf-tickets mailing list
Opensaf-tickets@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
