- **status**: review --> fixed
- **Comment**:

commit 05148767b54a95bfc5171c8a1b0ab42e9c70c8fb (HEAD -> develop, 
origin/develop, ticket-3390)
Author: Thien Minh Huynh <[email protected]>
Date:   Wed Jan 7 08:41:10 2026 +0000
 
    immnd: fix cannot set implementer returning SA_AIS_ERR_EXIST [#3390]
    Setting an implementer during cluster merge or split‑brain recovery
    could fail with SA_AIS_ERR_EXIST even though the coord accepted the new
    implementer and the operation should be retried.
    When this happens, visible symptoms include the imm agent timing out or
    receiving a response that later leads to SA_AIS_ERR_EXIST on retries.
    After a network merge, IMMND re-introduces and enters a sync phase with
    the coordinator (mIntroduced == 2). While syncing, IMMND may drop the
    set-implementer response but the coordinator can still accept and set the
    implementer. This creates a mismatch: the imm agent either times out or
    gets a stale/absent response, and when it retries the operation the IMMND
    now reports SA_AIS_ERR_EXIST because the implementer is already set on
    the coordinator.
    Add an early check in case IMMND need to be synced with coord.
    This prevents further processing while IMMND is syncing and makes
    the retryable condition explicit so the agent can try again later.



---

**[tickets:#3390] imm: cannot set implementer after merge network**

**Status:** fixed
**Milestone:** 5.27.01
**Created:** Mon Nov 17, 2025 07:17 AM UTC by Thien Minh Huynh
**Last Updated:** Fri Feb 27, 2026 11:03 PM UTC
**Owner:** Thien Minh Huynh


The issue observes when testing roaming SC with split brain recovery.

~~~
Oct 08 19:07:20 SC-1 immagent[4920]: m_immHandle != 0 - re-init. rc: SA_AIS_OK
Oct 08 19:07:27 SC-1 immagent[4920]: initialize: saImmOiInitialize_2 - SA_AIS_OK
Oct 08 19:07:27 SC-1 immagent[4920]: initialize: saImmOiImplementerSet - 
SA_AIS_ERR_TRY_AGAIN
Oct 08 19:07:31 SC-1 immagent[4920]: initialize: saImmOiImplementerSet - 
SA_AIS_ERR_TRY_AGAIN
Oct 08 19:07:39 SC-1 immagent[4920]: initialize: saImmOiImplementerSet - 
SA_AIS_ERR_TRY_AGAIN
Oct 08 19:07:51 SC-1 immagent[4920]: initialize: saImmOiImplementerSet - 
SA_AIS_ERR_TRY_AGAIN
Oct 08 19:08:07 SC-1 immagent[4920]: initialize: saImmOiImplementerSet - 
SA_AIS_ERR_TRY_AGAIN
Oct 08 19:08:37 SC-1 immagent[4920]: initialize: saImmOiImplementerSet - 
SA_AIS_ERR_TIMEOUT
Oct 08 19:09:01 SC-1 immagent[4920]: initialize: saImmOiImplementerSet - 
SA_AIS_ERR_BAD_HANDLE
Oct 08 19:09:01 SC-1 immagent[4920]: initialize: init failed, finalize - 
SA_AIS_OK
Oct 08 19:09:01 SC-1 immagent[4920]: initialize: saImmOiImplementerSet - 
killing application - SA_AIS_ERR_BAD_HANDLE
Oct 08 19:09:11 SC-1 immagent[25217]: initialize: saImmOiInitialize_2 - 
SA_AIS_OK
Oct 08 19:09:11 SC-1 immagent[25217]: initialize: saImmOiImplementerSet - 
SA_AIS_ERR_EXIST
~~~

cannot set implementer even immagent process already restart. It's always 
return SA_AIS_ERR_EXIST



---

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

Reply via email to