[tickets] [opensaf:tickets] #2605 amfnd: change log level to notice for events during node failover/shutdown

- **status**: accepted --> review - **Component**: unknown --> amf --- ** [tickets:#2605] amfnd: change log level to notice for events during node failover/shutdown** **Status:** review **Milestone:** 5.17.10 **Created:** Wed Oct 04, 2017 03:43 AM UTC by Gary Lee **Last Updated:** Wed Oct 04,

[tickets] [opensaf:tickets] #2533 pyosaf: Make pyosaf:::immom::initialize() consistent with other modules

- **status**: review --> fixed - **Comment**: commit dfb0d550adb44e148001beb5237559b3e472fd9c Author: Hieu Nguyen Date: Wed Oct 4 11:12:43 2017 +0700 pyosaf: Make pyosaf:::immom::initialize() consistent with other modules [#2533] + Remove a preceding underscore character of the initi

[tickets] [opensaf:tickets] #2605 amfnd: change log level to notice for events during node failover/shutdown

- **summary**: amfnd: change log level to warning for events during node failover/shutdown --> amfnd: change log level to notice for events during node failover/shutdown - Description has changed: Diff: --- old +++ new @@ -1,4 +1,4 @@ -Messages such as these can be made warnings instead.

[tickets] [opensaf:tickets] #2230 pyosaf: imm om and oi utils bindings don't handle BAD HANDLE

- **status**: accepted --> wontfix - **Comment**: I set this ticket to "wontfix". If you have any comments, let me know ? --- ** [tickets:#2230] pyosaf: imm om and oi utils bindings don't handle BAD HANDLE ** **Status:** wontfix **Milestone:** 5.17.10 **Created:** Sun Dec 18, 2016 01:21 PM U

[tickets] [opensaf:tickets] #2230 pyosaf: imm om and oi utils bindings don't handle BAD HANDLE

Hi, According to Johan's idea: "This should be done automatically in the retry loop". I want make clearly about this: In BAD\_HANDLE case difference with TRY\_AGAIN case + TRY\_AGAIN is a simple case that's mean try to call current function agian. + BAD\_HANDLE have many complex cases. Example fo

[tickets] [opensaf:tickets] #2605 amfnd: change log level to warning for events during node failover/shutdown

--- ** [tickets:#2605] amfnd: change log level to warning for events during node failover/shutdown** **Status:** accepted **Milestone:** 5.17.10 **Created:** Wed Oct 04, 2017 03:43 AM UTC by Gary Lee **Last Updated:** Wed Oct 04, 2017 03:43 AM UTC **Owner:** Gary Lee Messages such as these

[tickets] [opensaf:tickets] #2587 amf: Incorrect handling of version when initializing OpenSAF APIs

- **status**: review --> fixed --- ** [tickets:#2587] amf: Incorrect handling of version when initializing OpenSAF APIs** **Status:** fixed **Milestone:** 5.17.10 **Created:** Thu Sep 21, 2017 06:38 AM UTC by Gary Lee **Last Updated:** Wed Oct 04, 2017 12:06 AM UTC **Owner:** Gary Lee AMF s

[tickets] [opensaf:tickets] #2587 amf: Incorrect handling of version when initializing OpenSAF APIs

develop: commit c9daf4dae064f10c27fa82d15db7b7cdc3bd90ea Author: Gary Lee Date: Wed Oct 4 11:04:55 2017 +1100 amf: ensure we do not reuse version when calling OpenSAF init functions [#2587] release: commit 4957f89607c79c41dc147b5ce3c87343b34ee105 Author: Gary Lee Date: Wed Oct 4

[tickets] [opensaf:tickets] #2517 ntf: Incorrect handling of version when initializing OpenSAF APIs

- **status**: review --> fixed - **assigned_to**: Canh Truong --> nobody - **Comment**: release: commit c342d1ef320226ee0b2ddf9f85bd28f07143c083 Author: Canh Van Truong Date: Wed Oct 4 10:51:56 2017 +1100 ntf: fix incorrect handling of version when initializing OpenSAF APIs in ntf servi

[tickets] [opensaf:tickets] #2516 log: Incorrect handling of version when initializing OpenSAF APIs

- **status**: review --> fixed - **assigned_to**: Canh Truong --> nobody - **Comment**: commit 9638ef3c50fa94036203c97fb382c3dba758e39b (HEAD, origin/develop, develop) Author: Canh Van Truong Date: Mon Sep 18 15:49:03 2017 +0700 log: fix incorrect handling of version when initializing Op

[tickets] [opensaf:tickets] #2230 pyosaf: imm om and oi utils bindings don't handle BAD HANDLE

- **status**: unassigned --> accepted - **assigned_to**: Hieu Nguyen - **Blocker**: --> False - **Milestone**: future --> 5.17.10 - **Comment**: In progress --- ** [tickets:#2230] pyosaf: imm om and oi utils bindings don't handle BAD HANDLE ** **Status:** accepted **Milestone:** 5.17.10 **C

[tickets] [opensaf:tickets] #2603 pyosaf: run pylint for pyosaf utils and try to fix the reported issues

- Description has changed: Diff: --- old +++ new @@ -1 +1 @@ -Run pylint for all Python code files in OpenSAF and try to fix all reported issues. +Run pylint for pyosaf utils and try to fix the reported issues. --- ** [tickets:#2603] pyosaf: run pylint for pyosaf utils and try t

[tickets] [opensaf:tickets] #2523 pyosaf: IMM OM module initialized with ERR_BAD_HANDLE

Hi Zoran ! All functions in pyosaf utils decorate by decorate() function in pyosaf/utils/__init__.py. You can see in __init__.py of clm/immoi/immom/log/ntf same as below: saImmOmInitialize = decorate(saImmOm.saImmOmInitialize) saImmOmSelectionObjectGet = decorate(saImmOm.saImmOmSelection

[tickets] [opensaf:tickets] #2603 pyosaf: run pylint for pyosaf utils and try to fix the reported issues

- **summary**: pyosaf: run pylint for Python code files and try to fix all reported issues --> pyosaf: run pylint for pyosaf utils and try to fix the reported issues --- ** [tickets:#2603] pyosaf: run pylint for pyosaf utils and try to fix the reported issues** **Status:** accepted **Milest