#485 SU stuck in terminating state when being lock-in

[Nagendra Kumar]

Test Steps:
1. 2N Red with 2 Sus(SU1 and SU2).
2. Configure 3 comp in each SU, 3 csi in each SI i.e. 3 SI. Each CSI/SI is for one component.
3. Add a new component in each SU.
4. Assign SI along csi.
5. Lock/lock-in, unlock-in. Su stuck in terminating.

Reason: When su fsm is running and it is termination all component, it see one component in uninstantiated state, it stuck there.

More logs follows..

[Nagendra Kumar]

osafamfnd

[Nagendra Kumar]

[Nagendra Kumar]

changeset: 4351:4ec165b0397f
branch: opensaf-4.2.x
parent: 4348:1f772ee1b2af
user: Nagendra Kumarnagendra.k@oracle.com
date: Wed Jul 24 11:47:47 2013 +0530
summary: amfnd: Don't execute terminate command for uninstantiated component [#485]

changeset: 4352:c6cc078e7e33
branch: opensaf-4.3.x
parent: 4349:ba0fd9dc8517
user: Nagendra Kumarnagendra.k@oracle.com
date: Wed Jul 24 11:48:20 2013 +0530
summary: amfnd: Don't execute terminate command for uninstantiated component [#485]

changeset: 4353:282a72622205
tag: tip
parent: 4350:95387cffda33
user: Nagendra Kumarnagendra.k@oracle.com
date: Wed Jul 24 11:48:37 2013 +0530
summary: amfnd: Don't execute terminate command for uninstantiated component [#485]