- **assigned_to**: Hans Feldt


---

** [tickets:#301] AMF: SU operational state is not moved to disabled**

**Status:** unassigned
**Created:** Wed May 22, 2013 11:43 AM UTC by Nagendra Kumar
**Last Updated:** Thu May 23, 2013 05:13 AM UTC
**Owner:** Hans Feldt

Migrated from http://devel.opensaf.org/ticket/3119

Changeset : 4200
Transport : TCP/ipv6 ( link local )
patches : 2794 2595 3067
PBE enabled.
Model : 2n
configuration : 1SG,2SUs,4comps in each su, 4Sis with 1csi each. 
SU1 is hosted on PL-3 and SU2 on PL-4


scenario:
1) Bring up the model. Initially all the SUs are in lock-in state.
Note that the instantiation,termination scripts are not available
2) Do unlock-in of SU1, the SUs goes to termination-failed state. 


The SU's operational state doesn't move to DISABLED. 


console output:


amf-adm unlock-in safSu=SU1,safSg=SG,safApp=test2nApp
error - saImmOmAdminOperationInvoke_2 admin-op RETURNED: 
SA_AIS_ERR_REPAIR_PENDING (29)


safSu=SU1,safSg=SG,safApp=test2nApp


saAmfSUAdminState=LOCKED(2)
saAmfSUOperState=ENABLED(1)
saAmfSUPresenceState=TERMINATION-FAILED(7)
saAmfSUReadinessState=OUT-OF-SERVICE(1)





---

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

Reply via email to