#301 AMF: SU operational state is not moved to disabled

[Nagendra Kumar]

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)

[Nagendra Kumar]

sc2logs

[Nagendra Kumar]

pl3logs

[Hans Feldt]

changeset: 4317:7d726fdf6978
branch: opensaf-4.2.x
parent: 4311:8343c97e3b3a
user: Hans Feldt hans.feldt@ericsson.com
date: Tue Jun 25 15:13:49 2013 +0200
summary: amfnd: set SU DISABLED at TERM-FAILED [#301]

changeset: 4318:40048d531c0e
branch: opensaf-4.3.x
parent: 4312:55ae14ab1739
user: Hans Feldt hans.feldt@ericsson.com
date: Tue Jun 25 15:13:49 2013 +0200
summary: amfnd: set SU DISABLED at TERM-FAILED [#301]

changeset: 4319:df0acc9fa78b
tag: tip
parent: 4316:28b36fb4ae16
user: Hans Feldt hans.feldt@ericsson.com
date: Tue Jun 25 15:13:49 2013 +0200
summary: amfnd: set SU DISABLED at TERM-FAILED [#301]