Issue is reproducbile but with the patch of #1540 it will not stuck into
Instantiating state and after cleanup AMF will try to instantiate the
component. The default value of no. of such retries comes from
SaAmfCompGlobalAttributes which according to spec is 2. Although #1540 sovles
the problem if SU is getting stuck into INSTANTIATING state, AMFND is not
honoring this count and keep on instantiating the component. So a minor patch
is needed to solve this no, of retries problem.
Also note that after no. of retries are finished, AMF will mark both the
component and SU as INST_FAILED and as per spec it will terminate/cleanup all
the other healthy instantiated components.
---
** [tickets:#1556] AMF : SU struck in instantiating state during adm su restart
op ( component reg failure )**
**Status:** assigned
**Milestone:** 4.5.2
**Created:** Thu Oct 22, 2015 06:44 AM UTC by Srikanth R
**Last Updated:** Thu Oct 22, 2015 07:10 AM UTC
**Owner:** Praveen
**Attachments:**
- [TwoN.sh](https://sourceforge.net/p/opensaf/tickets/1556/attachment/TwoN.sh)
(9.7 kB; application/x-shellscript)
Changeset : 6901
Application : 2N , two SUs
steps :
* Both the SUs are having full assignments.
* Issued restart operation on SU hosting standby assignment. The first
component in the SU did not register with AMF. Only the CLC CLI script exited
with success, but saAmfComponentRegister is not called by component .
Oct 17 13:40:37 SYSTEST-PLD-1 osafamfnd[28402]: NO Admin Restart request for
'safSu=TestApp_SU2,safSg=TestApp_SG1,safApp=TestApp_TwoN'
Oct 17 13:40:37 SYSTEST-PLD-1 osafamfnd[28402]: NO
'safSu=TestApp_SU2,safSg=TestApp_SG1,safApp=TestApp_TwoN' Presence State
INSTANTIATED => RESTARTING
Oct 17 13:40:37 SYSTEST-PLD-1 osafamfnd[28402]: NO
'safSu=TestApp_SU2,safSg=TestApp_SG1,safApp=TestApp_TwoN' Presence State
RESTARTING => INSTANTIATING
Oct 17 13:40:47 SYSTEST-PLD-1 osafamfnd[28402]: NO Instantiation of
'safComp=COMP1,safSu=TestApp_SU2,safSg=TestApp_SG1,safApp=TestApp_TwoN' failed
Oct 17 13:40:47 SYSTEST-PLD-1 osafamfnd[28402]: NO Reason: component
registration timer expired
Below is the state of SU after the admin operation timed out.
safSu=TestApp_SU2,safSg=TestApp_SG1,safApp=TestApp_TwoN
saAmfSUAdminState=LOCKED(2)
saAmfSUOperState=ENABLED(1)
saAmfSUPresenceState=INSTANTIATING(2)
saAmfSUReadinessState=OUT-OF-SERVICE(1)
---
Sent from sourceforge.net because opensaf-tickets@lists.sourceforge.net 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
Opensaf-tickets@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
