- **status**: unassigned --> assigned
- **assigned_to**: Nagendra Kumar
---
** [tickets:#485] SU stuck in terminating state when being lock-in**
**Status:** assigned
**Created:** Fri Jul 05, 2013 10:38 AM UTC by Nagendra Kumar
**Last Updated:** Mon Jul 08, 2013 11:05 AM UTC
**Owner:** 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..
---
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
