This steps have problems.
When a component is getting added in Instatiated SU, then it is like
undeterministic state.
After that lock-in doesn't not succeed, su stuck into terminating state,
because the uninstantiated component can't be terminated and the below error
log will come:
osafamfnd [13826:avnd_clc.c:0863] T1
'safComp=New_add,safSu=SU1,safSg=2N,safApp=App1':Entering CLC FSM: presence
state:'SA_AMF_PRESENCE_UNINSTANTIATED(1)',
Event:'AVND_COMP_CLC_PRES_FSM_EV_TERM'
Ideal way should be like 7.1AMF Dynamic configuration changes in AMF PR doc:
1. Perform Lock and Lock-in admin operations Standby SU(say SU2). Add
component CMXH in SU2.
2. Perform Unlock-in and Unlock admin operations Standby SU(say SU2).
3. Perform Lock and Lock-in admin operations Standby SU(say SU1). Add
component CMXH in SU1.
4. Perform Unlock-in and Unlock admin operations Standby SU(say SU1).
5. Add SI and CSI.
I remember a new component used to get added in the lock-in SU, but now it
seems the check is removed. A component is being added in unlocked SU, which
creates problem.
---
** [tickets:#194] AMF: Creating new comp/csi in existing N-way active SG does
not work**
**Status:** unassigned
**Created:** Tue May 14, 2013 09:09 AM UTC by Bertil Engelholm
**Last Updated:** Wed Jul 03, 2013 11:00 AM UTC
**Owner:** nobody
I'm trying to add a new component (and csi for it) in an existing N-way active
SG and it does not work. If I create all new objects in the same IMM CCB AMF
complains about missing Compcsi.
If the new CSI is created in a separate CCB the creating works but the new
component is not started. If I in this state locks/unlocks (amf-adm
lock/unlock) the SuA1 all components comes up. But if I in this state also try
to lock/unlock SuA2, the amf-adm lock hangs.
I have attached a tar file that contains three campaigns that creates the
configurations.
install_JavaSgA_campaign.xml installs a basic simulated Java configuration.
addCompCsi-1_campaign.xml tries to add the comp/csi in one CCB which fails.
addCompCsi-2_campaign.xml adds the csi in a separate CCB which works but comp
does not start and SU lock/unlock hangs.
So first run the install campaign and then either addCompCsi-1 or addCompCsi-2.
---
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.
------------------------------------------------------------------------------
This SF.net email is sponsored by Windows:
Build for Windows Store.
http://p.sf.net/sfu/windows-dev2dev
_______________________________________________
Opensaf-tickets mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
