-> In addition to the steps mentioned in the ticket, for the below operations
following message is printed in syslog.
Sep 8 12:06:29 CONTROLLER-1 osafamfd[2222]: ER exec: create FAILED 12
Sep 8 12:06:35 CONTROLLER-1 osafamfd[2222]: ER exec: create FAILED 12
Sep 8 12:06:45 CONTROLLER-1 osafamfd[2222]: ER exec: create FAILED 12
Sep 8 12:06:55 CONTROLLER-1 osafamfd[2222]: ER exec: create FAILED 12
Below are the steps.
-> Delete all the application objects.
-> Perform the middleware switchover / failover.
-> New active controller is trying to access the application SI object which
is already deleted earlier.
Sep 8 12:08:36.647738 osafamfd [2222:main.cc:0810] << process_event
Sep 8 12:08:36.647743 osafamfd [2222:imm.cc:0396] >> execute
Sep 8 12:08:36.647748 osafamfd [2222:imm.cc:0142] >> exec: Create
safCsi=CSI1,safSi=TestApp_SI4,safApp=TestApp_TwoN
Sep 8 12:08:36.647754 osafamfd [2222:imma_oi_api.c:2786] >>
rt_object_create_common
Sep 8 12:08:36.647761 osafamfd [2222:imma_oi_api.c:2892] TR attr:safCSIComp
Sep 8 12:08:36.647768 osafamfd [2222:imma_oi_api.c:2892] TR
attr:saAmfCSICompHAState
Sep 8 12:08:36.647795 osafamfd [2222:imma_oi_api.c:2892] TR
attr:saAmfCSICompHAReadinessState
Sep 8 12:08:36.650289 osafamfd [2222:imma_oi_api.c:3063] <<
rt_object_create_common
Sep 8 12:08:36.650330 osafamfd [2222:imm.cc:0163] ER exec: create FAILED 12
---
** [tickets:#2009] AMF: App Si is moving to UNASSIGNED state after middleware
failover**
**Status:** unassigned
**Milestone:** 4.7.2
**Created:** Thu Sep 08, 2016 06:07 AM UTC by Srikanth R
**Last Updated:** Thu Sep 08, 2016 06:09 AM UTC
**Owner:** nobody
Environment details
------------------
OS : Suse 64bit
Changeset : 7997 ( 5.1.FC)
Setup : 5 nodes ( 2 controllers and 3 payloads with headless feature enabled &
no PBE )
AMF Application : 2N model with SUs mapped on PL-3,PL-4 ( si-si deps enabled)
Summary :
------------------
Application SIs are moving to UNASSIGNED state after middleware failover.
Steps followed & Observed behaviour
------------------
-> Initially brought up AMF application (2n model) on two payloads.
-> All the SIs are fully assigned state and SUs are in INSERVICE state.
-> Performed middleware failover.
-> After standby became active controller, SIs moved to unassigned state. But
'amf-state siass' is showing proper output.
-> Application received CSI remove callbacks after locking the SUs
Expected behaviour
------------------
-> As no fault happened on the application, SIs should not move to UNASSIGNED
state for middleware failover.
---
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
