- **Milestone**: future --> never
- **Comment**:
A duplicate of #538.
---
** [tickets:#183] component's operational state and SU's presence state are not
updated in the multiple NPI components instantiation failure**
**Status:** unassigned
**Milestone:** never
**Created:** Tue May 14, 2013 07:00 AM UTC by Nagendra Kumar
**Last Updated:** Tue Jul 28, 2015 07:04 AM UTC
**Owner:** nobody
Migrated from http://devel.opensaf.org/ticket/2178
1.Unlocked the NPI SU having 4 components.
2. First two components got instantiated properly, third component got
instantiation failed.
3. AMF tried to cleanup third component, which got failed and third component
moved to instantiation-failure.
4. Now amf should termiante the instantiated compnents, where the presence
state for SU and component should be set to TERMINATING, but presence state is
not updated for SU in the current implementation.
5.AMF tried to terminate the first and second components, which got failed and
cleanup also failed. Hence termination failure for first and second components.
It's OK and according to section 3.2 in page 62
But according to spec section 4.8, as presence state is set to
termination-failed.component's operational state should be set to DISABLED ,
which is not set in the current implementation.
Finally SU's presence state should be set to termination-failure.
which is not updated in the current implementation
---
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.
------------------------------------------------------------------------------
_______________________________________________
Opensaf-tickets mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
