#1237 Lock of SU having PI and NPI component fail with timeout.

[Syed Shareef Ali]

changeset: 6216:f75e056ebd43

Problem description.-

Lock of SU1 was failing with error "error - command timed out (alarm)"

SLES-64BIT-SLOT3:/opt/goahead/tetware/opensaffire/suites/avsv/common # amf-adm lock safSu=d_2n_1,safSg=SG_d_2n,safApp=2nApp
error - command timed out (alarm)

Steps followed.-

Configured 2N model runtime with below configuration:-
1) 2 SUs in lock-instantiation state and SU1 to be spawned on PL-3 and SU2 on SC-1. Each SU was having one PI and one NPI component.
2) successfully unlock-in and unlock of SU1
3) now tried to lock SU1 which hung and finally came out with timeout

Please note, it was observed that component in use was giving the response on time.

[Praveen]

In the configuration two SIs are configured. Each SI has two CSIS.
Since one of the component is NPI it can take only one assignment, one of the CSIs in second CSI can not be assigned to any component. At present AMF includes a check at SU level not at the component level. Due to this AMFND tries to assign CSI of second SI also, and could not respond to AMFD for assignment.

[Praveen]

changeset: 6310:b27c4fcca4d1
branch: opensaf-4.4.x
parent: 6307:f0cb8b273299
user: praveen.malviya@oracle.com
date: Fri Mar 06 14:26:03 2015 +0530
summary: amfd: assign only one csi per NPI component for PI SU [#1237]

changeset: 6311:d9cb4346ab12
branch: opensaf-4.5.x
parent: 6308:004951f807c0
user: praveen.malviya@oracle.com
date: Fri Mar 06 14:29:05 2015 +0530
summary: amfd: assign only one csi per NPI component for PI SU [#1237]

changeset: 6312:d4403c1b4dda
tag: tip
parent: 6309:bcaa40558166
user: praveen.malviya@oracle.com
date: Fri Mar 06 14:29:36 2015 +0530
summary: amfd: assign only one csi per NPI component for PI SU [#1237]

https://sourceforge.net/p/opensaf/mailman/message/33206996/