It is one of the Action Item of #517:
So, after this patch, we need to work on the following work items in this
ticket:
Pushing Imm reading information in other flows of the code in the separate
thread created in the floated patch: This is not going to be easy as Amfnd
execution and Readin
- **status**: review --> fixed
- **Comment**:
changeset: 7642:83ee28ff2284
branch: opensaf-5.0.x
parent: 7640:5259a416781a
user:Anders Widell
date:Tue May 17 09:06:45 2016 +0200
summary: fm: Start activation supervision timer properly [#1831]
changeset: 7643:1fe
Unfortunately this is causing issues for us now. So I think it's important
enough to create its own ticket.
---
** [tickets:#1833] amfnd: node director does not handle OM BAD_HANDLE**
**Status:** unassigned
**Milestone:** 4.7.2
**Created:** Tue May 17, 2016 06:41 AM UTC by Gary Lee
**Last Upda
mds.log PL-29
May 13 3:17:48.910042 osafamfnd[855] ERR |MDS_SND_RCV: msg loss detected, Src
svc_id = IMMND(25), Src vdest id= 65535,
Src Adest = 594903869623256,
local svc_id = IMMA_OM(26) msg num=6, recvd cnt=0
May 13 3:17:48.910672 osafamfnd[85
- Description has changed:
Diff:
--- old
+++ new
@@ -4,3 +4,9 @@
May 13 03:17:48 PL-29 osafamfnd[855]: WA marking handle as exposed
May 13 03:17:48 PL-29 osafamfnd[855]: ER saImmOmSearchInitialize_2 failed: 9
May 13 03:17:48 PL-29 osafamfnd[855]: ER 'avnd_evt_avd_su_pres_evh':FAILED
+
+m
So, how is the plan to fix it. Are you going to initialize the handle again in
the same thread ?
---
** [tickets:#1833] amfnd: node director does not handle OM BAD_HANDLE**
**Status:** unassigned
**Milestone:** 4.7.2
**Created:** Tue May 17, 2016 06:41 AM UTC by Gary Lee
**Last Updated:** Tue
Don't we have the same problem with an IMM reader thread too?
---
** [tickets:#1833] amfnd: node director does not handle OM BAD_HANDLE**
**Status:** unassigned
**Milestone:** 4.7.2
**Created:** Tue May 17, 2016 06:41 AM UTC by Gary Lee
**Last Updated:** Tue May 17, 2016 08:36 AM UTC
**Owner:**
Handling BAD_HANDLE is not implemented in IMM reader thread, it is mentioned in
the ticket #517. Now, since IMM reader is a separate thread, it is safe to
initialize it in the same thread for multiple times.
---
** [tickets:#1833] amfnd: node director does not handle OM BAD_HANDLE**
**Status:
I'm not sure I understand. Can't we initialize again, without the IMM reader
thread?
---
** [tickets:#1833] amfnd: node director does not handle OM BAD_HANDLE**
**Status:** unassigned
**Milestone:** 4.7.2
**Created:** Tue May 17, 2016 06:41 AM UTC by Gary Lee
**Last Updated:** Tue May 17, 2016
Yes, You can initialize in the same thread, but you may get TRY_AGAIN or other
errors and may continue in the loop. But anyway, I just wanted to know the way
you want to solve it. May be we can send the patch, then we can talk.
---
** [tickets:#1833] amfnd: node director does not handle OM BAD
- **status**: unassigned --> assigned
- **assigned_to**: Pham Hoang Nhat
- **Comment**:
Hi Nhat Pham,
This error "osafckptnd[19133]: ncs_sel_obj_ind: write failed - Bad file
descriptor" we are getting
because of heedless support changes "cpnd: To improve handling fault code
returned by saClm
I'm not sure yet. There are IMM calls in lots of places, and potentially any of
the IMM calls can return BAD_HANDLE.
---
** [tickets:#1833] amfnd: node director does not handle OM BAD_HANDLE**
**Status:** unassigned
**Milestone:** 4.7.2
**Created:** Tue May 17, 2016 06:41 AM UTC by Gary Lee
**
---
** [tickets:#1834] amf: amfd crashes during deletion of MW NoRed SI while
standby SC is coming up.**
**Status:** accepted
**Milestone:** 4.7.2
**Created:** Tue May 17, 2016 09:16 AM UTC by Praveen
**Last Updated:** Tue May 17, 2016 09:16 AM UTC
**Owner:** Praveen
**Attachments:**
-
[amf
Yes, that is true. You can refer to Amfd code for handling BAD HANDLE.
---
** [tickets:#1833] amfnd: node director does not handle OM BAD_HANDLE**
**Status:** unassigned
**Milestone:** 4.7.2
**Created:** Tue May 17, 2016 06:41 AM UTC by Gary Lee
**Last Updated:** Tue May 17, 2016 09:11 AM UTC
*
Note that I wrote tickets [#1607] and [#1609] some time ago, for cleaning up
this sort of problems "properly". We can of course patch the system to solve
the most urgent problems, but I would like to see a long-term proper solution
as well - maybe in the next release?
---
** [tickets:#1833] a
---
** [tickets:#1835] Imm: Immd helathcheck callback got timed-out on active
controller when starting opensaf on PL-4 and stopping opensaf on PL-3
simultaneously.**
**Status:** unassigned
**Milestone:** 4.7.2
**Created:** Tue May 17, 2016 10:27 AM UTC by Madhurika Koppula
**Last Updated:**
4 nodes cluster with single PBE with load of 10k objects.
---
** [tickets:#1835] Imm: Immd helathcheck callback got timed-out on active
controller when starting opensaf on PL-4 and stopping opensaf on PL-3
simultaneously.**
**Status:** unassigned
**Milestone:** 4.7.2
**Created:** Tue May 17,
IMMD is struck. Similar to #1291 ticket
May 17 14:59:56.578839 osafimmd [11154:immd_mds.c:0766] >> immd_mds_bcast_send
May 17 14:59:56.578845 osafimmd [11154:immsv_evt.c:5459] T8 Sending:
IMMND_EVT_D2ND_GLOB_FEVS_REQ_2 to 0
May 17 15:05:46.992261 osafimmd [2208:immd_main.c:0112] >> immd_initiali
The test-case (simplified);
1. Start a virtual cluster
2. Installs the SW-under-test with a "campaign" with cluster reboot ~02:19, SAF
started ~02:20:09
3. Performs some tests (most likely not related)
4. Starts a "scale-out" by starting 2 new VM's in the cluster ~02:30
5. The new VM's boot
Hi Nagu
I think we have the same problem in amfd. BAD_HANDLE is only handled for the OI
handle, not OM.
---
** [tickets:#1833] amfnd: node director does not handle OM BAD_HANDLE**
**Status:** unassigned
**Milestone:** 4.7.2
**Created:** Tue May 17, 2016 06:41 AM UTC by Gary Lee
**Last Updated
---
** [tickets:#1836] CKPT: Section is not deleted during switchover, after
expiration time**
**Status:** unassigned
**Milestone:** 4.7.2
**Created:** Wed May 18, 2016 01:20 AM UTC by Srikanth R
**Last Updated:** Wed May 18, 2016 01:20 AM UTC
**Owner:** nobody
**Attachments:**
-
[1836.tgz]
- **status**: assigned --> accepted
---
** [tickets:#1830] ncs_sel_obj_ind: write failed message observed in syslog
during OpenSAF start**
**Status:** accepted
**Milestone:** 4.7.2
**Created:** Mon May 16, 2016 12:36 PM UTC by Ritu Raj
**Last Updated:** Tue May 17, 2016 09:07 AM UTC
**Owner:*
This issue is observed on SLES VMs. We shall modify the application and try
with sleep of 1.2 seconds or more and check whether the issue is observed.
---
** [tickets:#1836] CKPT: Section is not deleted during switchover, after
expiration time**
**Status:** unassigned
**Milestone:** 4.7.2
**C
- **status**: accepted --> review
---
** [tickets:#1830] ncs_sel_obj_ind: write failed message observed in syslog
during OpenSAF start**
**Status:** review
**Milestone:** 4.7.2
**Created:** Mon May 16, 2016 12:36 PM UTC by Ritu Raj
**Last Updated:** Wed May 18, 2016 02:15 AM UTC
**Owner:** Ph
---
** [tickets:#1837] TIPC: loading model gives: "osafimmpbed: ER Failed in
saImmOmSearchNext_2:5 - exiting" and "osafimmpbed: ER immpbe.cc
dumpObjectsToPbe failed - exiting (line:265)**
**Status:** unassigned
**Milestone:** 5.1.FC
**Created:** Wed May 18, 2016 05:41 AM UTC by beatriz brand
- **status**: unassigned --> invalid
- **Comment**:
This issue is not observed for sleep of 1.2 seconds
---
** [tickets:#1836] CKPT: Section is not deleted during switchover, after
expiration time**
**Status:** invalid
**Milestone:** 4.7.2
**Created:** Wed May 18, 2016 01:20 AM UTC by Srika
- **status**: review --> fixed
- **Milestone**: 4.7.2 --> 5.0.1
- **Comment**:
changeset: 7644:c893131ce311
user:Nhat Pham
date:Wed May 18 10:31:16 2016 +0530
summary: cpnd: To indicate clm_updated_sel_obj in cpnd_clm_init_thread
[#1830]
changeset: 7645:ea188b1ec260
bra
Yes, but handling of BAD HANDLE of OM API in Amfnd will be similar like the
handling BAD HANDLE of OI API in Amfd..
---
** [tickets:#1833] amfnd: node director does not handle OM BAD_HANDLE**
**Status:** unassigned
**Milestone:** 4.7.2
**Created:** Tue May 17, 2016 06:41 AM UTC by Gary Lee
**L
28 matches
Mail list logo
