- **Milestone**: 4.7.2 --> 5.1.FC
---
** [tickets:#1916] Amf: Amfnd calling Imm API from avnd_comp_config_reinit
during headless**
**Status:** review
**Milestone:** 5.1.FC
**Created:** Thu Jul 14, 2016 05:38 AM UTC by Nagendra Kumar
**Last Updated:** Mon Jul 18, 2016 12:57 PM UTC
**Owner:** Nagendra Kumar
Steps to reproduce
------------------
1. Start one controller and two payloads.
2. Perform the following operation:
immcfg -f /tmp/1916.xml; amf-adm unlock-in
safSu=SU1,safSg=AmfDemo_2N,safApp=AmfDemo1; immcfg -m -a
saAmfCompInstantiateCmdArgv=instantiate
safComp=AmfDemo,safSu=SU1,safSg=AmfDemo_2N,safApp=AmfDemo1
3. Keep sleep in the instantiate script:
start|instantiate)
shift
logger -st $name "1. Instantiate $SA_AMF_COMPONENT_NAME ......"
sleep 7
logger -st $name "2. Instantiate $SA_AMF_COMPONENT_NAME ......"
start $*
4. Restart a component on payload and stop controller.
5. Kill Immnd on PL-3
Observed behaviour
------------------
During headless, avnd_comp_config_reinit() calls saImmOmInitialize_cond(),
which intern calls saImmOmInitialize, which is not halding try again.
So, Imm returns TRY_AGAIN and Amfnd is not handling TRY AGAIN in headelss.
So, saImmOmInitialize_cond return TRY_AGAIN, in tern prints:
"saImmOmInitialize FAILED for "
So, avnd_comp_config_reinit() return res as -1.
Expected behaviour
------------------
In this case, we can avoid callind Imm apis if we know that right now, the
condition is headless and Imm can give TRY AGAIN for longer time.
So, we can restart the component with old configuration. In worst case,
component will go into instantiation/termination failures, but that could be
recovered using admin command after cluster recovers from headless using repair
admin command.
The other alternative to this problem is allow Imm reader thread to hung in
TRY_AGAIN and let Amfnd keep exchanging Health checks and other activities. But
this again will need major revamp of the code.
Error messages
------------------
saImmOmInitialize FAILED for
safComp=AmfDemo,safSu=SU1,safSg=AmfDemo,safApp=AmfDemo1_NPI
---
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.------------------------------------------------------------------------------
What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic
patterns at an interface-level. Reveals which users, apps, and protocols are
consuming the most bandwidth. Provides multi-vendor support for NetFlow,
J-Flow, sFlow and other flows. Make informed decisions using capacity planning
reports.http://sdm.link/zohodev2dev
_______________________________________________
Opensaf-tickets mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
