Attached 1141.tgz contains the traces, simple configuration based on amf demo
and test patch to reproduce the problem.
steps to reproduce:
1)Bring two controllers up after compiling amfd with the attached patch.
2)Bring amf demo up.
3) Lock active su.
4) Since active amfd will not be able to update imm, after failover, user will
see
safSISU=safSu=SC-2\,safSg=NoRed\,safApp=OpenSAF,safSi=NoRed1,safApp=OpenSAF
saAmfSISUHAState=ACTIVE(1)
safSISU=safSu=SC-2\,safSg=2N\,safApp=OpenSAF,safSi=SC-2N,safApp=OpenSAF
saAmfSISUHAState=ACTIVE(1)
safSISU=safSu=SU1\,safSg=AmfDemo\,safApp=AmfDemo1,safSi=AmfDemo,safApp=AmfDemo1
saAmfSISUHAState=QUIESCED(3)
safSISU=safSu=SU2\,safSg=AmfDemo\,safApp=AmfDemo1,safSi=AmfDemo,safApp=AmfDemo1
saAmfSISUHAState=STANDBY(2)
But syslog of sc-2 clearly shows that SU2 became active.
Attachments:
-
[1141.tgz](https://sourceforge.net/p/opensaf/tickets/_discuss/thread/87962c8a/5b19/attachment/1141.tgz)
(559.1 kB; application/x-compressed)
---
** [tickets:#1141] si assignments are not removed after lock/lock-in of su with
failover**
**Status:** accepted
**Milestone:** 4.5.2
**Created:** Mon Sep 29, 2014 02:03 PM UTC by surender khetavath
**Last Updated:** Wed Jul 15, 2015 01:13 PM UTC
**Owner:** Praveen
**Attachments:**
-
[logs.tgz](https://sourceforge.net/p/opensaf/tickets/1141/attachment/logs.tgz)
(11.3 MB; application/x-compressed-tar)
changeset : 5918
model : 2n
configuration:
1App,1SG,2SUs with 50comps each,50SIs with 1CSI each
bring up the application. lock SU and parallely kill amfd on active node
Here sc2 was active. PL-3 and PL-4 hosts SU1 & SU2 resp.
safSu=SU1,safSg=SG,safApp=test2nApp
saAmfSUAdminState=UNLOCKED(1)
saAmfSUOperState=ENABLED(1)
saAmfSUPresenceState=INSTANTIATED(3)
saAmfSUReadinessState=IN-SERVICE(2)
safSu=SU2,safSg=SG,safApp=test2nApp
saAmfSUAdminState=LOCKED-INSTANTIATION(3)
saAmfSUOperState=ENABLED(1)
saAmfSUPresenceState=UNINSTANTIATED(1)
saAmfSUReadinessState=OUT-OF-SERVICE(1)
safSi=SI1,safApp=test2nApp
saAmfSIAdminState=UNLOCKED(1)
saAmfSIAssignmentState=FULLY_ASSIGNED(2)
safSi=SI2,safApp=test2nApp
saAmfSIAdminState=UNLOCKED(1)
saAmfSIAssignmentState=FULLY_ASSIGNED(2)
safSi=SI3,safApp=test2nApp
saAmfSIAdminState=UNLOCKED(1)
saAmfSIAssignmentState=FULLY_ASSIGNED(2)
safSi=SI4,safApp=test2nApp
saAmfSIAdminState=UNLOCKED(1)
saAmfSIAssignmentState=FULLY_ASSIGNED(2)
.....
....
safSISU=safSu=SU1\,safSg=SG\,safApp=test2nApp,safSi=SI49,safApp=test2nApp
saAmfSISUHAState=ACTIVE(1)
safSISU=safSu=SU1\,safSg=SG\,safApp=test2nApp,safSi=SI50,safApp=test2nApp
saAmfSISUHAState=ACTIVE(1)
safSISU=safSu=SU2\,safSg=SG\,safApp=test2nApp,safSi=SI27,safApp=test2nApp
saAmfSISUHAState=STANDBY(2)
safSISU=safSu=SU2\,safSg=SG\,safApp=test2nApp,safSi=SI28,safApp=test2nApp
saAmfSISUHAState=STANDBY(2)
safSISU=safSu=SU2\,safSg=SG\,safApp=test2nApp,safSi=SI29,safApp=test2nApp
saAmfSISUHAState=STANDBY(2)
....
....
---
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.------------------------------------------------------------------------------
_______________________________________________
Opensaf-tickets mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
