changeset: 5232:8913c7dd8fe6
user:Hans Feldt
date:Wed May 07 14:53:20 2014 +0200
summary: V2 (4/7) amfd: add SU constr/destr [#713]
changeset: 5233:c19cba564bb6
user:Hans Feldt
date:Wed May 07 14:54:15 2014 +0200
summary: amfd: add and use set_su_switc
---
** [tickets:#893] smfd: node destination not found in cluster reboot step**
**Status:** assigned
**Milestone:** 4.5.FC
**Created:** Fri May 09, 2014 04:51 AM UTC by Ingvar Bergström
**Last Updated:** Fri May 09, 2014 04:51 AM UTC
**Owner:** Ingvar Bergström
In a cluster reboot step, direc
- **status**: assigned --> fixed
- **Comment**:
SMF allows objects to be created and deleted regardless of DN.
This is how it is today. It is in the hands of the user to specify these DNs.
---
** [tickets:#752] Incorrect safSmfBundle objects should not be allowed to
create/delete during camp
- **status**: accepted --> review
---
** [tickets:#883] osaf: Build fails with GCC 4.9.0**
**Status:** review
**Milestone:** 4.3.3
**Created:** Mon May 05, 2014 08:01 AM UTC by Anders Widell
**Last Updated:** Mon May 05, 2014 08:01 AM UTC
**Owner:** Anders Widell
OpenSAF fails to build with G
Following is the analysis of the logs:
imma trace(Application is started from PL-3):
Adminoperation sync is called(here the timeout is specified is 1 second):
May 7 19:51:13.918324 imma [16924:imma_om_api.c:3332] >> admin_op_invoke_common
May 7 19:51:14.927406 imma [16924:imma_om_api.c:3536]
- **assigned_to**: Zoran Milinkovic
- **Comment**:
default(4.5):
http://sourceforge.net/p/opensaf/mailman/message/32315376/
---
** [tickets:#16] IMM: Configigurable OI callback server-side timeout per
OI-handle.**
**Status:** review
**Milestone:** 4.5.FC
**Created:** Tue May 07, 2013 08:28 A
---
** [tickets:#16] IMM: Configigurable OI callback server-side timeout per
OI-handle.**
**Status:** review
**Milestone:** 4.5.FC
**Created:** Tue May 07, 2013 08:28 AM UTC by Anders Bjornerstedt
**Last Updated:** Thu May 08, 2014 11:55 AM UTC
**Owner:** nobody
There is a need for configura
- **status**: accepted --> review
- **assigned_to**: Zoran Milinkovic --> nobody
---
** [tickets:#16] IMM: Configigurable OI callback server-side timeout per
OI-handle.**
**Status:** review
**Milestone:** 4.5.FC
**Created:** Tue May 07, 2013 08:28 AM UTC by Anders Bjornerstedt
**Last Update
- **status**: review --> fixed
- **assigned_to**: Anders Bjornerstedt --> nobody
- **Comment**:
changeset: 5231:02371e62cd45
tag: tip
user:Anders Bjornerstedt
date:Thu May 08 13:38:04 2014 +0200
summary: imm: Allow admin-operations directly targeting an
implemente
---
** [tickets:#892] ntf: Incorrect handling of length in SaNameT**
**Status:** accepted
**Milestone:** 4.5.FC
**Created:** Thu May 08, 2014 11:37 AM UTC by elunlen
**Last Updated:** Thu May 08, 2014 11:37 AM UTC
**Owner:** elunlen
The length variable in a SaNameT can in OpenSAF have a max 2
- **status**: accepted --> fixed
- **Comment**:
There is no new fix for this one. The reason for reopen is not valid. A new
ticket [#891] is written
---
** [tickets:#771] logd crashed when logsv application is running **
**Status:** fixed
**Milestone:** 4.5.FC
**Created:** Fri Feb 07, 2014 0
---
** [tickets:#891] LOG: Log server crash if length in SaNameT is 256**
**Status:** accepted
**Milestone:** 4.5.FC
**Created:** Thu May 08, 2014 11:06 AM UTC by elunlen
**Last Updated:** Thu May 08, 2014 11:06 AM UTC
**Owner:** elunlen
When writing a log record with a Ntf header e.g. an ala
- **Comment**:
The same issue is observed on the ChangeSet: 5142, with same scenario.
1. SC-2 Active
SC-1 Standby hosting imm coord.
2. Kill immnd on SC-1(new active) during controller switchover.
csiSetcallbackTimeout observed for LOG service and nodefail fast was triggered.
Attaching the l
Not using immadm client. using om apis(). For TIMEOUT/TRY_AGAIN of adminop(),
doing trying again. trying for 10times in total.
agent traces are enabled and attached as part of logs
---
** [tickets:#889] unknown: oi poll timeout differs during switchover and
failover scenarios**
**Status:**
- Description has changed:
Diff:
--- old
+++ new
@@ -9,5 +9,5 @@
MessageSendReceive initially timesout and later returns ERR_NOT_EXIST which
shows that the queue group may not be existing at that point of time. Journals
and trace are attached.
-On cs5143 (6.3.2)
+On cs5143 (4.3.2)
s
- Description has changed:
Diff:
--- old
+++ new
@@ -7,3 +7,7 @@
3) MessageSendReceive is invoked from another node.
MessageSendReceive initially timesout and later returns ERR_NOT_EXIST which
shows that the queue group may not be existing at that point of time. Journals
and trace are
I have a theory about why you see the long delay.
Are you using the tool immadm to generate the admin-operation ?
If so, then I think you are spending all those seconds in a
TRY_AGAIN lopp inside the immadm client.
Thus it is not actually any successfully invoked admin-operation
that is taking s
Does it take more than 40 seconds for the failover to produce a
new active IMMD ? That would explain the observed behavior.
But the question is then why it takes 40+ seconds to failover the IMMD.
---
** [tickets:#889] unknown: oi poll timeout differs during switchover and
failover scenarios*
- **summary**: oi poll timeout differs during switchover and failover scenarios
--> unknown: oi poll timeout differs during switchover and failover scenarios
- **Component**: imm --> unknown
- **Comment**:
Please remember to prefix ticket slogan with intended component.
Description indicates tha
---
** [tickets:#890] multiple times clc cleanup invoked for comps during opensaf
shutdown**
**Status:** unassigned
**Milestone:** future
**Created:** Thu May 08, 2014 07:24 AM UTC by surender khetavath
**Last Updated:** Thu May 08, 2014 07:24 AM UTC
**Owner:** nobody
changeset : 5143
model
20 matches
Mail list logo
