- **status**: assigned --> invalid
- **Milestone**: 4.3.3 --> never
- **Comment**:
This issue reports three problems. Out of these three problems, first two
problems does not exist anymore. Here is the state of SU when component
instantiation amd clean up fails:
safSu=SU1,safSg=AmfDemo,safApp=AmfDemo1
saAmfSUAdminState=UNLOCKED(1)
saAmfSUOperState=DISABLED(2)
saAmfSUPresenceState=TERMINATION-FAILED(7)
saAmfSUReadinessState=OUT-OF-SERVICE(1)
Fixing third issue will bring change in behavior because at present node reboot
clears inst-failed and term-failed state of all the components and SU hosted on
that node. Thus repair is done without any external intervention. Also there
are two node level attributes that are associated with failed state of SU/comp:
saAmfNodeFailfastOnTerminationFailure and
saAmfNodeFailfastOnInstantiationFailure.
AMF currently supports saAmfNodeFailfastOnTerminationFailure only.
Support of saAmfNodeFailfastOnInstantiationFailure will be an enhancement.
I will raise a new enhancement for the implementation of
saAmfNodeFailfastOnInstantiationFailure and for the change in behavior for
TERM_FAILED and INST_FAILED states.
---
** [tickets:#160] AMF SU/comp presence state issues**
**Status:** invalid
**Milestone:** never
**Created:** Tue May 14, 2013 04:11 AM UTC by Nagendra Kumar
**Last Updated:** Mon Feb 17, 2014 09:36 AM UTC
**Owner:** Praveen
Migrated from http://devel.opensaf.org/ticket/1119
The following list are a set of issues I've noticed with the SU & component
presence state computations:
1. If the component on a payload node fails to instantiate successfully, i.e.
its presence state is set to 'instantiation-failed', the containing SU is in an
invalid combination of AMF states given the state of the component:
safSu=SU1,safSg=AmfDemo?,safApp=AmfDemo?1:
Name Type Value(s)
========================================================================
saAmfSUReadinessState SA_UINT32_T 2 (0x2) [IN_SERVICE]
saAmfSUPresenceState SA_UINT32_T 6 (0x6) [INSTANTIATION_FAILED]
saAmfSUOperState SA_UINT32_T 1 (0x1) [ENABLED]
saAmfSUAdminState SA_UINT32_T 1 (0x1) [UNLOCKED]
safComp=AmfDemo?,safSu=SU1,safSg=AmfDemo?,safApp=AmfDemo?1:
Name Type Value(s)
========================================================================
saAmfCompReadinessState SA_UINT32_T 1 (0x1) [OUT_OF_SERVICE]
saAmfCompPresenceState SA_UINT32_T 6 (0x6) [INSTANTIATION_FAILED]
saAmfCompOperState SA_UINT32_T 2 (0x2) [DISABLED]
If a member component for an SU is in the instantiation-failed state, the SU
should be in the out-of-service/instantiation-failed/disabled/unlocked states
rather than what is shown above.
2. If when attempting to instantiate a component and the instantiation fails,
AMF initiates the component's CLEANUP CLC-CLI operation as it should. However,
if the component's CLEANUP CLC-CLI operation also fails the component's
presence state is set to 'instantiation-failed' rather than
'termination-failed' as it should be.
3. If a component on a payload node is in the 'instantiation-failed' presence
state when the node exits the cluster, the component's presence state (along
with the containing SU's presence state) is being changed to 'uninstantiated'.
However, the 'instantiation-failed' and 'termination-failed' presence states
are "latched" presence states, that is the only way the component (and SU)
should transition out of that presence state is if the operator explicitly
initiates the REPAIRED admin operation on the SU to indicate that the SU is now
configured to be successfully instantiated or if AMF automatically performs an
automatic repair action. The fact that the host node has left the cluster is
not sufficient reason to transition the component (and SU) out of the
'instantiation-failed' or 'termination-failed' presence states.
The following shows the state of the component and SU shown under item #1 after
the host payload node has left the cluster:
safSu=SU1,safSg=AmfDemo?,safApp=AmfDemo?1:
Name Type Value(s)
========================================================================
saAmfSUReadinessState SA_UINT32_T 1 (0x1) [OUT_OF_SERVICE]
saAmfSUPresenceState SA_UINT32_T 1 (0x1) [UNINSTANITATED]
saAmfSUOperState SA_UINT32_T 2 (0x2) [DISABLED]
saAmfSUAdminState SA_UINT32_T 1 (0x1) [UNLOCKED]
safComp=AmfDemo?,safSu=SU1,safSg=AmfDemo?,safApp=AmfDemo?1:
Name Type Value(s)
========================================================================
saAmfCompReadinessState SA_UINT32_T 1 (0x1) [OUT_OF_SERVICE]
saAmfCompPresenceState SA_UINT32_T 1 (0x1) [UNINSTANITATED]
saAmfCompOperState SA_UINT32_T 2 (0x2) [DISABLED]
Changed 3 years ago by nagendra ¶
■owner set to nagendra
■status changed from new to accepted
Changed 3 years ago by nagendra ¶
■patch_waiting changed from no to yes
Changed 3 years ago by nagendra ¶
Fixed Issue (1):
changeset: 1445:6f1367a277be
tag: tip
user: Nagendra Kumar <nagendra.kumar@…>
date: Thu May 20 15:07:58 2010 +0530
summary: Ticket #1119: AMF SU/comp presence state issues
Changed 3 years ago by nagendra ¶
■priority changed from major to minor
Changing priority to minor as fixed the major issue.
Changed 2 years ago by jfournier ¶
■milestone changed from 4.0.RC1 to 4.0.1
Changed 12 months ago by hafe ¶
■patch_waiting changed from yes to no
■milestone changed from 4.0.3.GA to future_releases
---
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.------------------------------------------------------------------------------
Want fast and easy access to all the code in your enterprise? Index and
search up to 200,000 lines of code with a free copy of Black Duck
Code Sight - the same software that powers the world's largest code
search on Ohloh, the Black Duck Open Hub! Try it now.
http://p.sf.net/sfu/bds
_______________________________________________
Opensaf-tickets mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
