- **assigned_to**: Praveen -->  nobody 


---

** [tickets:#311] standby su has no assignments after unlock of sg.**

**Status:** unassigned
**Milestone:** future
**Created:** Fri May 24, 2013 08:29 AM UTC by Nagendra Kumar
**Last Updated:** Wed Dec 11, 2013 06:27 AM UTC
**Owner:** nobody

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

changeset : 3969 with pataches :2986,2884,2865,2977
Model : 2N
configuration : 1SG,2SUs,4SIs,each SU has 4comps.1CSIs in each SI
no si-si deps configured. 
SU1 is mapped to pl-3 and Su2 to pl-4


Steps:
========
1) Shutdown SG
2) In the quiescing cbk reject the quiescing assignment by sending 
ERR_FAILED_OP in saAmfResponse() api.
3) Unlock the SG.


After Unlock of SG, standby got no assignments. 


Active ctrl syslog show:
Feb 26 12:18:48 SLES1 osafamfd[2713]: ER avd_su_si_assign_evh: invalid act 2


/etc/init.d/opensafd status:
============================
/etc/init.d/opensafd status
safSISU=safSu=PL-3\,safSg=NoRed?\,safApp=OpenSAF,safSi=NoRed?3,safApp=OpenSAF


saAmfSISUHAState=ACTIVE(1)


safSISU=safSu=SC-2\,safSg=NoRed?\,safApp=OpenSAF,safSi=NoRed?1,safApp=OpenSAF


saAmfSISUHAState=ACTIVE(1)


safSISU=safSu=SC-1\,safSg=2N\,safApp=OpenSAF,safSi=SC-2N,safApp=OpenSAF


saAmfSISUHAState=ACTIVE(1)


safSISU=safSu=SU1\,safSg=SG\,safApp=test2nApp,safSi=SI3,safApp=test2nApp


saAmfSISUHAState=ACTIVE(1)


safSISU=safSu=SC-2\,safSg=2N\,safApp=OpenSAF,safSi=SC-2N,safApp=OpenSAF


saAmfSISUHAState=STANDBY(2)


safSISU=safSu=SU1\,safSg=SG\,safApp=test2nApp,safSi=SI1,safApp=test2nApp


saAmfSISUHAState=ACTIVE(1)


safSISU=safSu=SU1\,safSg=SG\,safApp=test2nApp,safSi=SI2,safApp=test2nApp


saAmfSISUHAState=ACTIVE(1)


safSISU=safSu=SC-1\,safSg=NoRed?\,safApp=OpenSAF,safSi=NoRed?2,safApp=OpenSAF


saAmfSISUHAState=ACTIVE(1)


safSISU=safSu=PL-4\,safSg=NoRed?\,safApp=OpenSAF,safSi=NoRed?4,safApp=OpenSAF


saAmfSISUHAState=ACTIVE(1)


safSISU=safSu=SU1\,safSg=SG\,safApp=test2nApp,safSi=SI4,safApp=test2nApp


saAmfSISUHAState=ACTIVE(1)


safSISU=safSu=PL-5\,safSg=NoRed?\,safApp=OpenSAF,safSi=NoRed?5,safApp=OpenSAF


saAmfSISUHAState=ACTIVE(1)


SU states:
============
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=UNLOCKED(1)
saAmfSUOperState=ENABLED(1)
saAmfSUPresenceState=INSTANTIATED(3)
saAmfSUReadinessState=IN-SERVICE(2)




Changed 3 months ago by praveenmalviya ¶
  Analysis:
When unlock operation on SG was performed, amfd sent four initial asignments to 
amfnd for SU1. Amfnd issued callbacks to four components for CSIs. After this, 
one by one components started responding back to amfnd. Issue here is amfnd did 
not send any SI level response to amfd when first three components responded. 
Now when fourth component responded, amfnd sent SU level response to amfd. This 
is incorrect. Amfnd should sent four SI level response to amfd separately. I 
think SU_SI_ALL remained set because of side effects of some previous 
operations (in which su_si_oper_done was not called which resets the flag). 
Since SU_SI_ALL is set amfnd will wait for the assignments of all the SIs. Once 
completed it will send SU level response.


Changed 3 months ago by hafe ¶
  Should be solved by my 2990 patches, please confirm. Would be nice to close 
2990...


Changed 2 months ago by hafe ¶
  I reproduced and checked logs/traces. The reason for this is that there is a 
redundant SUSI delete message sent from avd to avnd. The assignment has already 
been deleted. avnd silently discards this message without logging, responding 
or anyhing...


So what are the problems here? Obviously the silent discard is one. But what 
should avnd do? Reply with an error code, reply OK (since delete is 
idempotent), panic etc. The real bug is in avd. But how should these types of 
problems be handled, what should happen when the master (avd) is faulty, what 
should its slaves (avnd) do?


Comes back to the high level protocol between avd-avnd





---

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.
------------------------------------------------------------------------------
BPM Camp - Free Virtual Workshop May 6th at 10am PDT/1PM EDT
Develop your own process in accordance with the BPMN 2 standard
Learn Process modeling best practices with Bonita BPM through live exercises
http://www.bonitasoft.com/be-part-of-it/events/bpm-camp-virtual- event?utm_
source=Sourceforge_BPM_Camp_5_6_15&utm_medium=email&utm_campaign=VA_SF
_______________________________________________
Opensaf-tickets mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets

Reply via email to