- **Milestone**: 4.6.2 --> 4.7.2
---
** [tickets:#1541] AMF : Both the 2N SUs are assigned Standby SI Assignment run
time objects.**
**Status:** unassigned
**Milestone:** 4.7.2
**Created:** Tue Oct 13, 2015 07:17 AM UTC by Srikanth R
**Last Updated:** Mon Nov 02, 2015 09:06 AM UTC
**Owner:** nobody
**Attachments:**
- [1541.sh](https://sourceforge.net/p/opensaf/tickets/1541/attachment/1541.sh)
(16.7 kB; application/x-shellscript)
Changeset : 6901
Configuration : 2N
2 SUs and 4 SIs with out si-si deps.
Component recovery = 3 ( suFailoverflag disabled )
Steps :
* Initially all the SIs are in assigned state.
* Performed shutdown operation on the SU hosting active assignment
* In the quiescing callback, ensure that component do not respond.
* As part of recovery, the other SU got active callbacks. But the SI
assignment objects for active are not created. Only the standby SI assignments
are present in IMM.
* After unlocking the locked SU, both the SUs are showing standby assignment
from the siass runtime objects.
safSISU=safSu=TestApp_SU1\,safSg=TestApp_SG1\,safApp=TestApp_TwoN,safSi=TestApp_SI2,safApp=TestApp_TwoN
saAmfSISUHAState=STANDBY(2)
safSISU=safSu=TestApp_SU1\,safSg=TestApp_SG1\,safApp=TestApp_TwoN,safSi=TestApp_SI4,safApp=TestApp_TwoN
saAmfSISUHAState=STANDBY(2)
safSISU=safSu=TestApp_SU1\,safSg=TestApp_SG1\,safApp=TestApp_TwoN,safSi=TestApp_SI3,safApp=TestApp_TwoN
saAmfSISUHAState=STANDBY(2)
safSISU=safSu=TestApp_SU2\,safSg=TestApp_SG1\,safApp=TestApp_TwoN,safSi=TestApp_SI1,safApp=TestApp_TwoN
saAmfSISUHAState=STANDBY(2)
safSISU=safSu=TestApp_SU1\,safSg=TestApp_SG1\,safApp=TestApp_TwoN,safSi=TestApp_SI1,safApp=TestApp_TwoN
saAmfSISUHAState=STANDBY(2)
safSISU=safSu=TestApp_SU2\,safSg=TestApp_SG1\,safApp=TestApp_TwoN,safSi=TestApp_SI2,safApp=TestApp_TwoN
saAmfSISUHAState=STANDBY(2)
safSISU=safSu=TestApp_SU2\,safSg=TestApp_SG1\,safApp=TestApp_TwoN,safSi=TestApp_SI3,safApp=TestApp_TwoN
saAmfSISUHAState=STANDBY(2)
safSISU=safSu=TestApp_SU2\,safSg=TestApp_SG1\,safApp=TestApp_TwoN,safSi=TestApp_SI4,safApp=TestApp_TwoN
saAmfSISUHAState=STANDBY(2)
Below is the error logged in active controller syslog.
Oct 13 00:19:51 CONTROLLER-2 osafamfd[11712]: EM sg_2n_fsm.cc:2359:
safSu=TestApp_SU1,safSg=TestApp_SG1,safApp=TestApp_TwoN (55)
Configuration to create the application is attached. Same issue is observed for
the similar scenario during Node shutdown operation
---
Sent from sourceforge.net because opensaf-tickets@lists.sourceforge.net 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.------------------------------------------------------------------------------
Find and fix application performance issues faster with Applications Manager
Applications Manager provides deep performance insights into multiple tiers of
your business applications. It resolves application problems quickly and
reduces your MTTR. Get your free trial!
https://ad.doubleclick.net/ddm/clk/302982198;130105516;z
_______________________________________________
Opensaf-tickets mailing list
Opensaf-tickets@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
