In the AMF code, there is a check in unlock operation of SG where it
sets the readiness state of SU to inservice if it is instantiated.
But at the same time there is a issue #493 which says that "Sis are
assigned to uninstantiated SU".
Please upload the traces for amfd and amfnd.
Thanks,
Prav
I've tracked this down to a race condition when using the ADMIN API. I
don't think this has anything to do with dynamically created CSIs.
The problem seems to be in amfnd.
If you have a component that takes a while to instantiate (in our case
~9 seconds), and issue the "UNLOCK-INSTANTIATE" adm
I'm seeing a problem when doing an administrative shutdown on an SG with
dynamically created CSIs.
I'm assuming that dynamically creating CSIs is supported...
I have an N+1 service group with one component entirely in the imm.xml
config file including CSIs. There is another component in this S
