[tickets] [opensaf:tickets] #1198 immtools: IMM version for the tools must be changed to A.2.14

- **status**: assigned --> accepted --- ** [tickets:#1198] immtools: IMM version for the tools must be changed to A.2.14** **Status:** accepted **Milestone:** 4.6.FC **Created:** Fri Oct 31, 2014 03:30 PM UTC by Neelakanta Reddy **Last Updated:** Tue Nov 11, 2014 07:02 AM UTC **Owner:** Neela

[tickets] [opensaf:tickets] #1198 immtools: IMM version for the tools must be changed to A.2.14

- **summary**: immtools: IMM cersion for the tools must be changed to A.2.14 --> immtools: IMM version for the tools must be changed to A.2.14 - Description has changed: Diff: --- old +++ new @@ -1,3 +1,2 @@ - A new features like "Allow admin-operations directly targeting an implementer

[tickets] [opensaf:tickets] #1206 imm: long DNs values are not handled well if client does not support long DNs

--- ** [tickets:#1206] imm: long DNs values are not handled well if client does not support long DNs** **Status:** accepted **Milestone:** 4.5.1 **Created:** Mon Nov 10, 2014 03:40 PM UTC by Zoran Milinkovic **Last Updated:** Mon Nov 10, 2014 03:40 PM UTC **Owner:** Zoran Milinkovic Long DNs

[tickets] [opensaf:tickets] #1178 “logtest 4 1” could only be executed once

- **status**: unassigned --> accepted - **assigned_to**: Per Rodenvall --> elunlen --- ** [tickets:#1178] “logtest 4 1” could only be executed once** **Status:** accepted **Milestone:** 4.6.FC **Created:** Mon Oct 20, 2014 08:58 AM UTC by Per Rodenvall **Last Updated:** Mon Oct 20, 2014 08:58

[tickets] [opensaf:tickets] #1183 imm: CCB timer is not reset after CCB is augmented

- **status**: accepted --> review --- ** [tickets:#1183] imm: CCB timer is not reset after CCB is augmented** **Status:** review **Milestone:** 4.4.2 **Created:** Tue Oct 21, 2014 11:18 AM UTC by Zoran Milinkovic **Last Updated:** Thu Nov 06, 2014 01:43 PM UTC **Owner:** Zoran Milinkovic Afte

Re: [tickets] [opensaf:tickets] #1179 LOG: Log service shall be able to recover if both SC nodes goes down

Hi Lennart, When you say "INVALID HANDLE" I assume you mean SA_AIS_ERR_BAD_HANDLE, right ? /AndersBj From: elunlen [mailto:elun...@users.sf.net] Sent: den 10 november 2014 12:54 To: opensaf-tickets@lists.sourceforge.net Subject: [tickets] [opensaf:tickets] #1179

[tickets] [opensaf:tickets] Re: #1179 LOG: Log service shall be able to recover if both SC nodes goes down

Hi Lennart, When you say "INVALID HANDLE" I assume you mean SA_AIS_ERR_BAD_HANDLE, right ? /AndersBj From: elunlen [mailto:elun...@users.sf.net] Sent: den 10 november 2014 12:54 To: opensaf-tickets@lists.sourceforge.net Subject: [tickets] [opensaf:tickets] #1179

[tickets] [opensaf:tickets] #1179 LOG: Log service shall be able to recover if both SC nodes goes down

I now have two patches for handling this situation. The idea is that the agent detects when the server goes down (both active and standby). When this happen the agent will invalidate all handles to all clients and free all resources. The clients will now get "INVALID HANDLE" as a reply in all API

[tickets] [opensaf:tickets] #1179 LOG: Log service shall be able to recover if both SC nodes goes down

- **status**: unassigned --> accepted --- ** [tickets:#1179] LOG: Log service shall be able to recover if both SC nodes goes down** **Status:** accepted **Milestone:** 4.6.FC **Created:** Mon Oct 20, 2014 01:25 PM UTC by elunlen **Last Updated:** Mon Oct 20, 2014 01:42 PM UTC **Owner:** elunl

[tickets] [opensaf:tickets] #1203 smfd: waits 5sec too long after node is up

- **status**: review --> fixed - **Comment**: changeset: 6128:b6f10f709b64 tag: tip parent: 6125:fd4bc9ded37d user:Ingvar Bergstrom date:Fri Nov 07 08:04:12 2014 +0100 summary: smfd: no unneccessary delay at node reboot [#1203] changeset: 6127:0b6d2927a627 br