- **Milestone**: future --> never
---
** [tickets:#291] Admin repaired operation is not instantiating the SU from
instantiation-failed state**
**Status:** invalid
**Milestone:** never
**Created:** Wed May 22, 2013 11:20 AM UTC by Nagendra Kumar
**Last Updated:** Wed Feb 18, 2015 03:56 PM UTC
**Owner:** Nagendra Kumar
Migrated from http://devel.opensaf.org/ticket/2518
Changeset: 3384
A wrong instantiation command path caused the component and the enclosing SU to
move to instantiation-failed state.
In this condition, after correcting the path and performing an admin-repaired
operation is not re-instantiating the SU eventhough its admin-state is unlocked.
The similar case is observed even when the node is rebooted with the SU is in
instantiation-failed state.
The following is the flow:
SU state:
--------------------------------------------------------------------------------
safSu=testSu2,safSg=testSg,safApp=testApp
saAmfSUAdminState=LOCKED-INSTANTIATION(3)
saAmfSUOperState=ENABLED(1)
saAmfSUPresenceState=UNINSTANTIATED(1)
saAmfSUReadinessState=OUT-OF-SERVICE(1)
Unlock-in operation on the SU:
--------------------------------------------------------------------------------
amf-adm unlock-in safSu=testSu2,safSg=testSg,safApp=testApp
error - saImmOmAdminOperationInvoke_2 admin-op RETURNED:
SA_AIS_ERR_REPAIR_PENDING (29)
/var/log/messages:
--------------------------------------------------------------------------------
Mar 1 19:36:23 SLES11-SLOT-1 osafamfnd[2917]:
'safSu=testSu2,safSg=testSg,safApp=testApp' Presence State UNINSTANTIATED =>
INSTANTIATING
Mar 1 19:36:23 SLES11-SLOT-1 osafamfnd[3865]: Could not stat
/opt/goahead/tetware/framework/amf_comp_script - No such file or directory
Mar 1 19:36:23 SLES11-SLOT-1 osafamfnd[2917]: Instantiation of
'safComp=testComp2,safSu=testSu2,safSg=testSg,safApp=testApp' failed
Mar 1 19:36:23 SLES11-SLOT-1 osafamfnd[2917]: Reason:'Exec of script failed
(script not readable or path wrong)'
Mar 1 19:36:23 SLES11-SLOT-1 osafamfnd[2917]: CLC CLI
script:'/opt/goahead/tetware/framework/amf_comp_script instantiate'
Mar 1 19:36:23 SLES11-SLOT-1 osafamfnd[3866]: Could not stat
/opt/goahead/tetware/framework/amf_comp_script - No such file or directory
Mar 1 19:36:23 SLES11-SLOT-1 osafamfnd[2917]: Cleanup of
'safComp=testComp2,safSu=testSu2,safSg=testSg,safApp=testApp' failed
Mar 1 19:36:23 SLES11-SLOT-1 osafamfnd[2917]: Reason:'Exec of script failed
(script not readable or path wrong)'
Mar 1 19:36:23 SLES11-SLOT-1 osafamfnd[2917]: CLC CLI
script:'/opt/goahead/tetware/framework/amf_comp_script cleanup'
Mar 1 19:36:23 SLES11-SLOT-1 osafamfnd[2917]:
'safSu=testSu2,safSg=testSg,safApp=testApp' Presence State INSTANTIATING =>
INSTANTIATION_FAILED
SU state:
--------------------------------------------------------------------------------
safSu=testSu2,safSg=testSg,safApp=testApp
saAmfSUAdminState=LOCKED(2)
saAmfSUOperState=DISABLED(2)
saAmfSUPresenceState=INSTANTIATION-FAILED(6)
saAmfSUReadinessState=OUT-OF-SERVICE(1)
Admin Repaired Operation:
--------------------------------------------------------------------------------
amf-adm repaired safSu=testSu2,safSg=testSg,safApp=testApp
/var/log/messages:
--------------------------------------------------------------------------------
Mar 1 19:38:51 SLES11-SLOT-1 osafamfnd[2917]:
'safSu=testSu2,safSg=testSg,safApp=testApp' Presence State INSTANTIATION_FAILED
=> UNINSTANTIATED
Final SU state even after node reboot:
--------------------------------------------------------------------------------
safSu=testSu2,safSg=testSg,safApp=testApp
saAmfSUAdminState=LOCKED(2)
saAmfSUOperState=ENABLED(1)
saAmfSUPresenceState=UNINSTANTIATED(1)
saAmfSUReadinessState=OUT-OF-SERVICE(1)
Changed 15 months ago by pavan ¶
■description modified (diff)
follow-up: ↓ 3 Changed 15 months ago by hafe ¶
I cannot reproduce this problem. It is working just fine for me.
Please provide more syslogs and traces from when repaired is performed.
Changed 15 months ago by pavan
■attachment 2518.tgz added
in reply to: ↑ 2 Changed 15 months ago by pavan ¶
Replying to hafe:
I cannot reproduce this problem. It is working just fine for me.
Please provide more syslogs and traces from when repaired is performed.
I added the zip file which includes amfd trace (of Active controller) and
syslog, amfnd traces (on the node hosing the SU)
To refer the logs, the timestamp for the admin repair operation is:
Fri Mar 2 10:50:03 IST 2012
follow-up: ↓ 5 Changed 15 months ago by hafe ¶
Repair is not magic. You will have to repair the system before the admin op
is performed. I cannot see anything wrong in the logs. Please redo the test and
provide proper logs that indicate that there is a problem.
in reply to: ↑ 4 ; follow-up: ↓ 6 Changed 15 months ago by pavan ¶
Replying to hafe:
Repair is not magic. You will have to repair the system before the admin op is
performed. I cannot see anything wrong in the logs. Please redo the test and
provide proper logs that indicate that there is a problem.
Before performing the admin repaired operation, I have corrected the
instantiation script path so that it comes up successfully after repair. But,
after repair action, I did not see AMF trying to instantiate the SU when it is
in locked, enabled state.
in reply to: ↑ 5 Changed 15 months ago by hafe ¶
Replying to pavan:
Replying to hafe:
Repair is not magic. You will have to repair the system before the admin op is
performed. I cannot see anything wrong in the logs. Please redo the test and
provide proper logs that indicate that there is a problem.
Before performing the admin repaired operation, I have corrected the
instantiation script path so that it comes up successfully after repair. But,
after repair action, I did not see AMF trying to instantiate the SU when it is
in locked, enabled state.
"that it comes up successfully after repair" so what is wrong? You need to
provide better information. It is working for me.
Changed 15 months ago by nagendra ¶
■version changed from 4.2.0 to 4.1.0
Not working because saAmfSGNumPrefInserviceSUs is configured as zero. Error
exists on 4.1.1 itself.
Changed 15 months ago by nagendra ¶
■priority changed from major to minor
Changed 14 months ago by nagendra ¶
■milestone changed from 4.2.1 to future_releases
saAmfSGNumPrefInserviceSUs attribute is not implemented as of now in 2N red
model. We need to implement it. It may require significant effort and it is
kind of invalid configuration by making saAmfSGNumPrefInserviceSUs as zero. So,
moving it into 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.
------------------------------------------------------------------------------
Don't Limit Your Business. Reach for the Cloud.
GigeNET's Cloud Solutions provide you with the tools and support that
you need to offload your IT needs and focus on growing your business.
Configured For All Businesses. Start Your Cloud Today.
https://www.gigenetcloud.com/
_______________________________________________
Opensaf-tickets mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
