- Attachments has changed:
Diff:
~~~~
--- old
+++ new
@@ -1,2 +1,4 @@
logs.tar (2.5 MB; application/x-gzip-compressed)
pl_logs.tar (1.3 MB; application/x-gzip-compressed)
+osafamfnd (122.8 kB; application/octet-stream)
+osafamfd (228.2 kB; application/octet-stream)
~~~~
- **Type**: enhancement --> defect
- **Comment**:
Attached is configuration to reprodue the problem. Also traces from amfd and
amfnd from active controller. The issue is not related to SI-SI deps in NWAY.
The problem is purely related to NWAY SG FSM. There are other enhancements
tickets for SI deps in nway.
So marking this ticket as defect.
steps to reproduce the probelm with attached configuration:
1)Bring up the app on two controllers.
2)2)Lock SU1 and make sure to delay the active assignment for Si1 from SU2.
3)SU1 will remain quiesced for Si1.
4)safSISU=safSu=SU1\,safSg=AmfDemo\,safApp=AmfDemo1,safSi=AmfDemo1,safApp=AmfDemo1
saAmfSISUHAState=QUIESCED(3)
5)Now try to lock-n SU1, AMF will retrun try agian as SU1 is assigned.
---
** [tickets:#316] SI Assignments are not removed for a SU in Nway redundancy
model**
**Status:** accepted
**Milestone:** 4.7.FC
**Created:** Fri May 24, 2013 08:39 AM UTC by Nagendra Kumar
**Last Updated:** Tue Aug 25, 2015 04:08 PM UTC
**Owner:** Praveen
**Attachments:**
- [logs.tar](https://sourceforge.net/p/opensaf/tickets/316/attachment/logs.tar)
(2.5 MB; application/x-gzip-compressed)
-
[pl_logs.tar](https://sourceforge.net/p/opensaf/tickets/316/attachment/pl_logs.tar)
(1.3 MB; application/x-gzip-compressed)
-
[osafamfnd](https://sourceforge.net/p/opensaf/tickets/316/attachment/osafamfnd)
(122.8 kB; application/octet-stream)
- [osafamfd](https://sourceforge.net/p/opensaf/tickets/316/attachment/osafamfd)
(228.2 kB; application/octet-stream)
Migrated from http://devel.opensaf.org/ticket/2987
changeset : 3855
Model : NWay
configuration : 1App,1SG,5SU with 3comps each, 5SIs with 3csi each.
si-si deps configured as SI1<-SI2<-SI3<-SI4
SIrankedSus not configured.
Node mapping : SU1 on SC-1, SU2 on SC-2, SU3 on PL-3, SU4,SU5 on PL-4.
While running the campaign, smf performs lock,lock-in of the activation units
i.e SUs. The SIs for SU3 are not removed though SU3 is in locked-state.
Subsequent unlock-in,unlock of SU3 fails.
/var/log/messages of active ctrl- SC-1 shows
============================================
Feb 3 22:45:14 linux-xc76 osafamfd[20055]: WA SIs still assigned to this SU
Feb 3 22:45:16 linux-xc76 osafamfd[20055]: WA SIs still assigned to this SU
Feb 3 22:45:18 linux-xc76 osafamfd[20055]: WA SIs still assigned to this SU
Feb 3 22:45:20 linux-xc76 osafamfd[20055]: WA SIs still assigned to this SU
Feb 3 22:45:23 linux-xc76 osafamfd[20055]: WA SIs still assigned to this SU
Feb 3 22:45:23 linux-xc76 osafsmfd[20081]: ER Fail to invoke admin operation,
too many SA_AIS_ERR_TRY_AGAIN, giving up.
dn=[safSu=SU3,safSg=SGONE,safApp=NWAYAPP], opId=[3]
Feb 3 22:45:23 linux-xc76 osafsmfd[20081]: ER Failed to call admin operation 3
on safSu=SU3,safSg=SGONE,safApp=NWAYAPP
Feb 3 22:45:23 linux-xc76 osafsmfd[20081]: ER Failed to Terminate activation
units in step=safSmfStep=0003
Feb 3 22:45:23 linux-xc76 osafsmfd[20081]: ER Step undoing failed
Feb 3 22:45:23 linux-xc76 osafsmfd[20081]: ER Step safSmfStep=0003 in procedure
safSmfProc=amfClusterProc-1 failed, step result 5
Feb 3 22:45:23 linux-xc76 osafsmfd[20081]: NO CAMP: Procedure
safSmfProc=amfClusterProc-1 returned FAILED
SU Assignments brief:
=======================
safSISU=safSu=SU1\,safSg=SGONE\,safApp=NWAYAPP,safSi=NWAYSI3,safApp=NWAYAPP
saAmfSISUHAState=ACTIVE(1)
safSISU=safSu=SU1\,safSg=SGONE\,safApp=NWAYAPP,safSi=NWAYSI2,safApp=NWAYAPP
saAmfSISUHAState=STANDBY(2)
safSISU=safSu=SU3\,safSg=SGONE\,safApp=NWAYAPP,safSi=NWAYSI5,safApp=NWAYAPP
saAmfSISUHAState=QUIESCED(3)
safSISU=safSu=SU4\,safSg=SGONE\,safApp=NWAYAPP,safSi=NWAYSI5,safApp=NWAYAPP
saAmfSISUHAState=ACTIVE(1)
safSISU=safSu=SU2\,safSg=SGONE\,safApp=NWAYAPP,safSi=NWAYSI1,safApp=NWAYAPP
saAmfSISUHAState=ACTIVE(1)
SU States:
==========
safSu=SU3,safSg=SGONE,safApp=NWAYAPP
saAmfSUAdminState=LOCKED(2)
saAmfSUOperState=ENABLED(1)
saAmfSUPresenceState=INSTANTIATED(3)
saAmfSUReadinessState=OUT-OF-SERVICE(1)
changed 4 months ago by bertil ¶
■owner changed from ingber to ravisekhar
■component changed from saf/smfsv to saf/avsv
I beleave this is an AMF problem. SMF only uses the AMF admin ops (lock, unlock
etc).
---
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
