---
** [tickets:#1101] AMF: Dependent SIs are not removed if SU (assigned sponsored
SIs) escalated to SuFailover**
**Status:** unassigned
**Milestone:** 4.5.0
**Created:** Wed Sep 17, 2014 01:26 AM UTC by Minh Hon Chau
**Last Updated:** Wed Sep 17, 2014 01:26 AM UTC
**Owner:** nobody
Configuration:
- 1App, 2SG:
- NpM: 3SUs (SU1, SU2, SU3) with 1 components each, 2SIs (SI1A, SI1B)
- NwayActive: 2SUs (SU4, SU5) with 1 components each, 1SIs (SI2)
- SI2 depends on SI1A
- saAmfSUFailover=1 for SU1, SU2, SU3
- saAmfSGCompRestartMax=2, saAmfSGCompRestartProb=10000000000,
saAmfSGSuRestartMax=2, saAmfSGSuRestartProb=10000000000 for NpM SG
- saAmfNodeSuFailoverMax=3, saAmfNodeSuFailOverProb=10000000000 for all
safAmfNode
Test:
- unlock-in, unlock all SUs
- All SI assignments
safSISU=safSu=SU2\,safSg=AmfDemo1\,safApp=AmfDemo2,safSi=AmfDemo1A,safApp=AmfDemo2
saAmfSISUHAState=ACTIVE(1)
saAmfSISUHAReadinessState=READY_FOR_ASSIGNMENT(1)
safSISU=safSu=SU1\,safSg=AmfDemo1\,safApp=AmfDemo2,safSi=AmfDemo1B,safApp=AmfDemo2
saAmfSISUHAState=ACTIVE(1)
saAmfSISUHAReadinessState=READY_FOR_ASSIGNMENT(1)
--
safSISU=safSu=SU4\,safSg=AmfDemo2\,safApp=AmfDemo2,safSi=AmfDemo2,safApp=AmfDemo2
saAmfSISUHAState=ACTIVE(1)
saAmfSISUHAReadinessState=READY_FOR_ASSIGNMENT(1)
safSISU=safSu=SU3\,safSg=AmfDemo1\,safApp=AmfDemo2,safSi=AmfDemo1A,safApp=AmfDemo2
saAmfSISUHAState=STANDBY(2)
saAmfSISUHAReadinessState=READY_FOR_ASSIGNMENT(1)
safSISU=safSu=SU3\,safSg=AmfDemo1\,safApp=AmfDemo2,safSi=AmfDemo1B,safApp=AmfDemo2
saAmfSISUHAState=STANDBY(2)
saAmfSISUHAReadinessState=READY_FOR_ASSIGNMENT(1)
safSISU=safSu=SU5\,safSg=AmfDemo2\,safApp=AmfDemo2,safSi=AmfDemo2,safApp=AmfDemo2
saAmfSISUHAState=ACTIVE(1)
saAmfSISUHAReadinessState=READY_FOR_ASSIGNMENT(1)
- In SC-2, pkill amf_demo untill SuFailover, assignments:
safSISU=safSu=SU1\,safSg=AmfDemo1\,safApp=AmfDemo2,safSi=AmfDemo1B,safApp=AmfDemo2
saAmfSISUHAState=ACTIVE(1)
saAmfSISUHAReadinessState=READY_FOR_ASSIGNMENT(1)
--
safSISU=safSu=SU4\,safSg=AmfDemo2\,safApp=AmfDemo2,safSi=AmfDemo2,safApp=AmfDemo2
saAmfSISUHAState=ACTIVE(1)
saAmfSISUHAReadinessState=READY_FOR_ASSIGNMENT(1)
safSISU=safSu=SU3\,safSg=AmfDemo1\,safApp=AmfDemo2,safSi=AmfDemo1A,safApp=AmfDemo2
saAmfSISUHAState=ACTIVE(1)
saAmfSISUHAReadinessState=READY_FOR_ASSIGNMENT(1)
safSISU=safSu=SU5\,safSg=AmfDemo2\,safApp=AmfDemo2,safSi=AmfDemo2,safApp=AmfDemo2
saAmfSISUHAState=ACTIVE(1)
saAmfSISUHAReadinessState=READY_FOR_ASSIGNMENT(1)
- In PL-3, pkill amf_demo untill SuFailover, assignments:
safSISU=safSu=SU1\,safSg=AmfDemo1\,safApp=AmfDemo2,safSi=AmfDemo1B,safApp=AmfDemo2
saAmfSISUHAState=ACTIVE(1)
saAmfSISUHAReadinessState=READY_FOR_ASSIGNMENT(1)
--
safSISU=safSu=SU4\,safSg=AmfDemo2\,safApp=AmfDemo2,safSi=AmfDemo2,safApp=AmfDemo2
saAmfSISUHAState=ACTIVE(1)
saAmfSISUHAReadinessState=READY_FOR_ASSIGNMENT(1)
safSISU=safSu=SU5\,safSg=AmfDemo2\,safApp=AmfDemo2,safSi=AmfDemo2,safApp=AmfDemo2
saAmfSISUHAState=ACTIVE(1)
saAmfSISUHAReadinessState=READY_FOR_ASSIGNMENT(1)
safSi=AmfDemo2 should be removed since safSi=AmfDemo1A has been removed
Instead of error escalation, locking SU2, SU3 can get the safSi=AmfDemo2
removed as expected.
---
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.------------------------------------------------------------------------------
Want excitement?
Manually upgrade your production database.
When you want reliability, choose Perforce
Perforce version control. Predictably reliable.
http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.clktrk
_______________________________________________
Opensaf-tickets mailing list
Opensaf-tickets@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
