Attached configuration and AMF traces after successful operation in 311.tgz.
Attachment: 311.tgz (214.0 kB; application/x-compressed)
---
** [tickets:#311] standby su has no assignments after unlock of sg.**
**Status:** unassigned
**Created:** Fri May 24, 2013 08:29 AM UTC by Nagendra Kumar
This issue is no longer reproducible on changeset: 4546:902b3c7ea830.
Attached 311.tgz contains the configuration and AMF traces of successful
operation as per bug description.
---
** [tickets:#311] standby su has no assignments after unlock of sg.**
**Status:** unassigned
**Created:** Fri
- **status**: unassigned --> accepted
---
** [tickets:#448] LOG: Incorrect validity check for saLogStreamFileName**
**Status:** accepted
**Created:** Mon Jun 10, 2013 12:01 PM UTC by elunlen
**Last Updated:** Thu Aug 15, 2013 01:24 PM UTC
**Owner:** elunlen
Validity check when changing saLogS
- **status**: accepted --> fixed
---
** [tickets:#595] IMM: saImmOmAccessorGet_2 locks IMM handle if
SA_IMM_SEARCH_GET_CONFIG_ATTR is used for IMM version less than A.02.11**
**Status:** fixed
**Created:** Mon Oct 14, 2013 01:58 PM UTC by Zoran Milinkovic
**Last Updated:** Tue Oct 15, 2013 01
default(4.4):
changeset: 4547:8b83ef6716d4
tag: tip
user:Zoran Milinkovic
date:Mon Oct 14 16:23:14 2013 +0200
summary: IMM: fix IMM handle lock when SA_IMM_SEARCH_GET_CONFIG_ATTR is
used in attribute names [#595]
---
** [tickets:#595] IMM: saImmOmAccessorGet_2 l
http://www.mail-archive.com/opensaf-devel@lists.sourceforge.net/msg00701.html
---
** [tickets:#595] IMM: saImmOmAccessorGet_2 locks IMM handle if
SA_IMM_SEARCH_GET_CONFIG_ATTR is used for IMM version less than A.02.11**
**Status:** accepted
**Created:** Mon Oct 14, 2013 01:58 PM UTC by Zoran M
- **status**: unassigned --> review
- **Milestone**: future --> 4.4.FC
---
** [tickets:#536] LOG: Incorrect handling of "partial write" when writing log
record to file**
**Status:** review
**Created:** Thu Aug 08, 2013 10:59 AM UTC by elunlen
**Last Updated:** Thu Aug 15, 2013 01:54 PM UTC
**
- **status**: assigned --> worksforme
---
** [tickets:#313] Wrong HA state reported after node-failover**
**Status:** worksforme
**Created:** Fri May 24, 2013 08:33 AM UTC by Nagendra Kumar
**Last Updated:** Tue Oct 15, 2013 12:37 PM UTC
**Owner:** Praveen
Migrated from http://devel.opensaf.o
Not observing this issue on changeset: 4546:902b3c7ea830.
Steps performed to reproduce it (configuration is in 313.tgz):
1)amf-adm lock safSu=SU2,safSg=AmfDemo,safApp=AmfDemo1
2)immcfg -a saAmfNodeSuFailoverMax=0 safAmfNode=SC-2,safAmfCluster=myAmfCluster
3)immcfg -a saAmfNodeSuFailoverMax=0 sa
- **assigned_to**: Praveen
---
** [tickets:#313] Wrong HA state reported after node-failover**
**Status:** unassigned
**Created:** Fri May 24, 2013 08:33 AM UTC by Nagendra Kumar
**Last Updated:** Fri May 24, 2013 08:33 AM UTC
**Owner:** Praveen
Migrated from http://devel.opensaf.org/ticket/3
- **status**: unassigned --> assigned
---
** [tickets:#313] Wrong HA state reported after node-failover**
**Status:** assigned
**Created:** Fri May 24, 2013 08:33 AM UTC by Nagendra Kumar
**Last Updated:** Tue Oct 15, 2013 12:37 PM UTC
**Owner:** Praveen
Migrated from http://devel.opensaf.org
This issue is observed on changeset: 4546:902b3c7ea830 default branch.
Attached 330.tgz contains configuration and AMF traces after reproducing the
issue.
Attachment: 330.tgz (532.2 kB; application/x-compressed)
---
** [tickets:#330] amf: SUSI assignments show only standy assignments for
12 matches
Mail list logo