#322 amf: SU's presence state doesn't become uninstantiated instead remains instantiated when the only component calls saAmfFinalize()

[Praveen]

Migrated from http://devel.opensaf.org/ticket/2193.
SetUp? : 1 controller
Model Observed : TwoN
Configuration : 1 App, 1 SG, 1 SU with 1 sa-aware component.
Component Recommended Recovery : COMPONENT_FAILOVER
By default the component is made to register itself, then finalize itself by call saAmfFinalize()

Bring up the configuration. Unlock-in and Unlock of SU will bring the component up and running. When the component Finalizes, the SU's state becomes as shown

safSu=SU_mycomp,safSg=SG_mycomp,safApp=mycompApp

saAmfSUAdminState=UNLOCKED(1)
saAmfSUOperState=DISABLED(2)
saAmfSUPresenceState=INSTANTIATED(3)
saAmfSUReadinessState=OUT-OF-SERVICE(1)

Component's state is :

---

safComp=mycomp,safSu=SU_mycomp,safSg=SG_mycomp,safApp=mycompApp
saAmfCompOperState=DISABLED(2)
saAmfCompPresenceState=INSTANTIATED(3)
saAmfCompReadinessState=OUT-OF-SERVICE(1)

In the fig4 on page 102, there is no such state.

[Nagendra Kumar]

Related ticket https://sourceforge.net/p/opensaf/tickets/495/

[Nagendra Kumar]

Not able to find any valid use case for this ticket. Reporting error could be a better way to report the component specific problem.