- **status**: unassigned --> accepted
- **assigned_to**: Hans Feldt
---
** [tickets:#569] AMF: make saAmfSGSuHostNodeGroup WRITEABLE**
**Status:** accepted
**Created:** Wed Sep 18, 2013 06:10 AM UTC by Hans Feldt
**Last Updated:** Wed Sep 18, 2013 06:10 AM UTC
**Owner:** Hans Feldt
The saAmfS
- **status**: review --> fixed
---
** [tickets:#570] AMF: ava down event ignored in TERMINATING state**
**Status:** fixed
**Created:** Wed Sep 18, 2013 06:45 AM UTC by Hans Feldt
**Last Updated:** Wed Oct 16, 2013 07:51 AM UTC
**Owner:** nobody
If a component crash or exit in context of the t
changeset: 4577:07e88841d268
branch: opensaf-4.2.x
parent: 4574:b424e8c4e643
user:Hans Feldt
date:Tue Oct 29 21:57:47 2013 +0100
summary: amf: change saAmfResponse to be synchronous in TerminateCallback
context [#570]
changeset: 4578:19f8ca3ee0e3
branch: op
This issue is reproducible on the changeset: 4565:e8ae1895d8e3.
However there is slight change in the steps to reproduce it.
Si-swap operation should be issued two times on two different SIs.
In the first si-swap on a SI2 one of the components should return
FAILED_OPERATION.
Second si-swap sho
changeset: 4574:b424e8c4e643
branch: opensaf-4.2.x
parent: 4569:dc118b8f1a07
user:Hans Feldt
date:Tue Oct 29 21:24:35 2013 +0100
summary: leap: change ncs_os_lock to syslog before abort [#605]
changeset: 4575:03c46e565f76
branch: opensaf-4.3.x
parent: 4
- **status**: review --> fixed
- **assigned_to**: Hans Feldt --> nobody
---
** [tickets:#605] immomtest: os_defs.c:447: ncs_os_lock: Assertion `0' failed.**
**Status:** fixed
**Created:** Wed Oct 23, 2013 11:33 AM UTC by Hans Feldt
**Last Updated:** Wed Oct 23, 2013 01:16 PM UTC
**Owner:** n
- **assigned_to**: Zoran Milinkovic --> Anders Bjornerstedt
---
** [tickets:#19] IMM: PBE should periodically audit the imm.db file**
**Status:** assigned
**Created:** Tue May 07, 2013 08:43 AM UTC by Anders Bjornerstedt
**Last Updated:** Tue May 07, 2013 08:43 AM UTC
**Owner:** Anders Bjorner
- **Milestone**: 4.4.FC --> future
---
** [tickets:#16] IMM: Support the saImmOiTimeout config attribute in the
SaImmMngt class**
**Status:** unassigned
**Created:** Tue May 07, 2013 08:28 AM UTC by Anders Bjornerstedt
**Last Updated:** Mon Sep 16, 2013 01:40 PM UTC
**Owner:** Anders Bjorners
- **status**: assigned --> unassigned
- **Milestone**: 4.4.FC --> future
---
** [tickets:#40] IMM: Protect OI-handles against rapid switching of OI role.**
**Status:** unassigned
**Created:** Tue May 07, 2013 11:31 AM UTC by Anders Bjornerstedt
**Last Updated:** Tue Sep 17, 2013 10:34 AM UTC
*
Comments inline:
> -Original Message-
> From: Anders Bjornerstedt [mailto:ander...@users.sf.net]
> Sent: Tuesday, October 29, 2013 1:29 PM
> To: [opensaf:tickets]
> Subject: [tickets] [opensaf:tickets] Re: #528 order of service not guaranteed
> during failover
>
> The cause of the problem
changeset: 4573:90aa577fb3ef
tag: tip
user:Nagendra Kumar
date:Tue Oct 29 16:23:58 2013 +0530
summary: amfd: Stop cluster startup timer, if all configured nodes have
joined [#76]
[staging:90aa57]
---
** [tickets:#76] AMF: if all nodes have joined the cluster, ca
- **status**: review --> fixed
---
** [tickets:#76] AMF: if all nodes have joined the cluster, cancel the
assignment timer and assign anyway**
**Status:** fixed
**Created:** Mon May 13, 2013 04:25 AM UTC by Nagendra Kumar
**Last Updated:** Wed Sep 25, 2013 09:24 AM UTC
**Owner:** Nagendra Kum
changeset: 4573:90aa577fb3ef
tag: tip
user:Nagendra Kumar
date:Tue Oct 29 16:23:58 2013 +0530
summary: amfd: Stop cluster startup timer, if all configured nodes have
joined [#76]
[staging:90aa57]
---
** [tickets:#76] AMF: if all nodes have joined the cluster, ca
This issue is reproducible on changeset: 4565:e8ae1895d8e3.
Attached 182.tgz contains Traces and 182.xml (reproducible configuration).
Steps to reproduce and observation:
1)immcfg -f 182.xml
2)amf-adm unlock-in and unlock safSu=SU1,safSg=AmfDemo,safApp=AmfDemo_NPI
error - saImmOmAdminOperatio
The cause of the problem is that the "discard_node" message from the active
IMMD to all IMMNDs over FEVS (MDS broadcast)
has not reached the IMMND at new-active where the CLMD is trying to set
implementer.
This is a timing issue due to the non homogenous communication mechanism in
OpenSAF.
This
- **status**: unassigned --> accepted
- **Milestone**: future --> 4.4.FC
---
** [tickets:#152] LOG: remove dependency to shared file system**
**Status:** accepted
**Created:** Mon May 13, 2013 11:51 AM UTC by elunlen
**Last Updated:** Mon May 13, 2013 11:51 AM UTC
**Owner:** elunlen
Purpose:
Attached traces and configuration.
Attachment: 203.tgz (628.1 kB; application/x-compressed)
---
** [tickets:#203] avsv: SG went to unstable state when active SU is locked
after adding new SI in NWay RM**
**Status:** assigned
**Created:** Wed May 15, 2013 04:32 AM UTC by Praveen
**Last Updat
Attached 203.tgz contains configuration:
-203.xml configuration to reproduce the issue.
-script new_si_csi_add.sh to add new SI
-Traces.
Steps to reproduce:
1) immcfg -f 203.xml
2) Unlock and Unlock-in of SU1 and SU2.
3) ./new_si_csi_add.sh
4) Lock SU1
5) OpenSAF stop of payload hosting SU2.
18 matches
Mail list logo