[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, 2017 04:12 AM UTC
**Owner:** Gary Lee
Messages such as these can be made notice instead.
LOG_ER("Ignoring event '%s' for '%s' during node failover",
pres_state_evt[ev], comp->name.c_str());
---
Sent from sourceforge.net because opensaf-tickets@lists.sourceforge.net is
subscribed to https://sourceforge.net/p/opensaf/tickets/
To unsubscribe from further messages, a project admin can change settings at
https://sourceforge.net/p/opensaf/admin/tickets/options. Or, if this is a
mailing list, you can unsubscribe from the mailing list.--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
Opensaf-tickets mailing list
Opensaf-tickets@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
[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 initialize method in immom + Does not automatically called initialize() when the module is implemented --- ** [tickets:#2533] pyosaf: Make pyosaf:::immom::initialize() consistent with other modules** **Status:** fixed **Milestone:** 5.17.10 **Created:** Fri Jul 21, 2017 01:09 PM UTC by Anders Widell **Last Updated:** Mon Oct 02, 2017 09:12 AM UTC **Owner:** Hieu Nguyen The module pyosaf/utils/immom has a method with the name initialize(), which is called automatically when the module is implemented. This is inconsistent with other pyosaf modules under utils, which don't call the initialize method automatically when the module is imported. Also, the initialize method in immom has a preceding underscore character, which should be removed to make the method name consistent with the other modules. --- Sent from sourceforge.net because opensaf-tickets@lists.sourceforge.net is subscribed to https://sourceforge.net/p/opensaf/tickets/ To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/opensaf/admin/tickets/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.-- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot___ Opensaf-tickets mailing list Opensaf-tickets@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
[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.
+Messages such as these can be made notice instead.
LOG_ER("Ignoring event '%s' for '%s' during node failover",
pres_state_evt[ev], comp->name.c_str());
---
** [tickets:#2605] amfnd: change log level to notice 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 can be made notice instead.
LOG_ER("Ignoring event '%s' for '%s' during node failover",
pres_state_evt[ev], comp->name.c_str());
---
Sent from sourceforge.net because opensaf-tickets@lists.sourceforge.net is
subscribed to https://sourceforge.net/p/opensaf/tickets/
To unsubscribe from further messages, a project admin can change settings at
https://sourceforge.net/p/opensaf/admin/tickets/options. Or, if this is a
mailing list, you can unsubscribe from the mailing list.--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
Opensaf-tickets mailing list
Opensaf-tickets@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
[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 UTC by Johan Mårtensson **Last Updated:** Wed Oct 04, 2017 03:51 AM UTC **Owner:** Hieu Nguyen The utils functions for imm om and oi add retry loops that shield the user from writing repetitive retries for each call to handle TRY AGAIN. The retry loop doesn't handle BAD HANDLE which means that the user will still need to wrap each call to check for BAD HANDLE and re-initialize the handle if required. This should be done automatically in the retry loop. --- Sent from sourceforge.net because opensaf-tickets@lists.sourceforge.net is subscribed to https://sourceforge.net/p/opensaf/tickets/ To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/opensaf/admin/tickets/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.-- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot___ Opensaf-tickets mailing list Opensaf-tickets@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
[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 for a CCB: * Init OM handle => OK * Init Admin Owner handle => OK * Init CCB handle => OK * Create a object => OK * Modify this object => OK * Apply CCB => BAD_HANDLE If we handle BAD\_HANDLE case use Johan's idea, we need keep track all data and all steps of CBB in above case, NOT only re-intialize. That takes many effort to store data and process complex. I think user who know clear their steps. When TRY\_AGAIN error occurred, they can easy rollback their steps. Regards, --- ** [tickets:#2230] pyosaf: imm om and oi utils bindings don't handle BAD HANDLE ** **Status:** accepted **Milestone:** 5.17.10 **Created:** Sun Dec 18, 2016 01:21 PM UTC by Johan Mårtensson **Last Updated:** Tue Oct 03, 2017 09:11 AM UTC **Owner:** Hieu Nguyen The utils functions for imm om and oi add retry loops that shield the user from writing repetitive retries for each call to handle TRY AGAIN. The retry loop doesn't handle BAD HANDLE which means that the user will still need to wrap each call to check for BAD HANDLE and re-initialize the handle if required. This should be done automatically in the retry loop. --- Sent from sourceforge.net because opensaf-tickets@lists.sourceforge.net is subscribed to https://sourceforge.net/p/opensaf/tickets/ To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/opensaf/admin/tickets/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.-- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot___ Opensaf-tickets mailing list Opensaf-tickets@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
[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 can be made warnings instead.
LOG_ER("Ignoring event '%s' for '%s' during node failover",
pres_state_evt[ev], comp->name.c_str());
---
Sent from sourceforge.net because opensaf-tickets@lists.sourceforge.net is
subscribed to https://sourceforge.net/p/opensaf/tickets/
To unsubscribe from further messages, a project admin can change settings at
https://sourceforge.net/p/opensaf/admin/tickets/options. Or, if this is a
mailing list, you can unsubscribe from the mailing list.--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
Opensaf-tickets mailing list
Opensaf-tickets@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
[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 sometimes reuses a version variable when initializing OpenSAF APIs. This means that the next time the API is initialized it may be initialized with a higher version. See #2517 for details. --- Sent from sourceforge.net because opensaf-tickets@lists.sourceforge.net is subscribed to https://sourceforge.net/p/opensaf/tickets/ To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/opensaf/admin/tickets/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.-- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot___ Opensaf-tickets mailing list Opensaf-tickets@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
[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 11:04:55 2017 +1100 amf: ensure we do not reuse version when calling OpenSAF init functions [#2587] --- ** [tickets:#2587] amf: Incorrect handling of version when initializing OpenSAF APIs** **Status:** review **Milestone:** 5.17.10 **Created:** Thu Sep 21, 2017 06:38 AM UTC by Gary Lee **Last Updated:** Fri Sep 22, 2017 01:24 AM UTC **Owner:** Gary Lee AMF sometimes reuses a version variable when initializing OpenSAF APIs. This means that the next time the API is initialized it may be initialized with a higher version. See #2517 for details. --- Sent from sourceforge.net because opensaf-tickets@lists.sourceforge.net is subscribed to https://sourceforge.net/p/opensaf/tickets/ To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/opensaf/admin/tickets/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.-- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot___ Opensaf-tickets mailing list Opensaf-tickets@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
[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 service [#2517] develop: commit 5ef5306958a5796dc836910c7067394d706056cc Author: Canh Van Truong Date: Wed Oct 4 10:38:00 2017 +1100 ntf: fix incorrect handling of version when initializing OpenSAF APIs in ntf service [#2517] --- ** [tickets:#2517] ntf: Incorrect handling of version when initializing OpenSAF APIs** **Status:** fixed **Milestone:** 5.17.10 **Created:** Fri Jun 30, 2017 12:51 PM UTC by elunlen **Last Updated:** Thu Sep 21, 2017 09:36 AM UTC **Owner:** nobody A general problem when initializing OpenSAF APIs is found. This problem applies to all OpenSAF services. The version used when initializing the API is in many cases stored in a global variable and this global variable is used every time the API is initialized. The version is given as a pointer to this variable. The problem is that this variable is defined as an [in/out] parameter that gives the version to use when initializing [in] but the value shall be changed by the agent to the highest version supported by the initialized service [out]. This means that the next time the API is initialized it may be initialized with a higher version. A higher version may not be backwards compatible with the intended version. Even if this is not causing any problems now it may in the future when new features are added. An example is IMM that has a highest version A, 2, 18. If this version is used IMM will handle CLM nodes in a different way than if initialized with a lower version. For example, new return codes has to be handled. --- Sent from sourceforge.net because opensaf-tickets@lists.sourceforge.net is subscribed to https://sourceforge.net/p/opensaf/tickets/ To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/opensaf/admin/tickets/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.-- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot___ Opensaf-tickets mailing list Opensaf-tickets@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
[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 OpenSAF APIs [#2516] The version used when initializing the API is in many cases stored in a global variable and this global variable is used every time the API is initialized. The version is given as a pointer to this variable. The problem is that this variable is defined as an [in/out] parameter that gives the version to use when initializing [in] but the value shall be changed by the agent to the highest version supported by the initialized service [out]. This means that the next time the API is initialized it may be initialized with a higher version. This patch help to fix that always initialize OpenSaf API with correct version in log service. --- ** [tickets:#2516] log: Incorrect handling of version when initializing OpenSAF APIs** **Status:** fixed **Milestone:** 5.17.10 **Created:** Fri Jun 30, 2017 12:49 PM UTC by elunlen **Last Updated:** Mon Sep 18, 2017 11:28 AM UTC **Owner:** nobody A general problem when initializing OpenSAF APIs is found. This problem applies to all OpenSAF services. The version used when initializing the API is in many cases stored in a global variable and this global variable is used every time the API is initialized. The version is given as a pointer to this variable. The problem is that this variable is defined as an [in/out] parameter that gives the version to use when initializing [in] but the value shall be changed by the agent to the highest version supported by the initialized service [out]. This means that the next time the API is initialized it may be initialized with a higher version. A higher version may not be backwards compatible with the intended version. Even if this is not causing any problems now it may in the future when new features are added. An example is IMM that has a highest version A, 2, 18. If this version is used IMM will handle CLM nodes in a different way than if initialized with a lower version. For example, new return codes has to be handled. --- Sent from sourceforge.net because opensaf-tickets@lists.sourceforge.net is subscribed to https://sourceforge.net/p/opensaf/tickets/ To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/opensaf/admin/tickets/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.-- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot___ Opensaf-tickets mailing list Opensaf-tickets@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
[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 **Created:** Sun Dec 18, 2016 01:21 PM UTC by Johan Mårtensson **Last Updated:** Sun Dec 18, 2016 01:21 PM UTC **Owner:** Hieu Nguyen The utils functions for imm om and oi add retry loops that shield the user from writing repetitive retries for each call to handle TRY AGAIN. The retry loop doesn't handle BAD HANDLE which means that the user will still need to wrap each call to check for BAD HANDLE and re-initialize the handle if required. This should be done automatically in the retry loop. --- Sent from sourceforge.net because opensaf-tickets@lists.sourceforge.net is subscribed to https://sourceforge.net/p/opensaf/tickets/ To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/opensaf/admin/tickets/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.-- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot___ Opensaf-tickets mailing list Opensaf-tickets@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
[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 to fix the reported issues** **Status:** accepted **Milestone:** 5.17.10 **Created:** Fri Sep 29, 2017 06:54 AM UTC by Nguyen TK Luu **Last Updated:** Tue Oct 03, 2017 08:23 AM UTC **Owner:** Nguyen TK Luu Run pylint for pyosaf utils and try to fix the reported issues. --- Sent from sourceforge.net because opensaf-tickets@lists.sourceforge.net is subscribed to https://sourceforge.net/p/opensaf/tickets/ To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/opensaf/admin/tickets/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.-- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot___ Opensaf-tickets mailing list Opensaf-tickets@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
[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.saImmOmSelectionObjectGet) saImmOmDispatch = decorate(saImmOm.saImmOmDispatch) saImmOmFinalize = decorate(saImmOm.saImmOmFinalize) All error codes returned handle by decorate() function (decorator of Python). We have been handle ERR_BAD_HANDLE in this function with stop app and raise exception. if error != eSaAisErrorT.SA_AIS_OK: raise_saf_exception(function, error) Do you have any ideas about this? --- ** [tickets:#2523] pyosaf: IMM OM module initialized with ERR_BAD_HANDLE** **Status:** accepted **Milestone:** 5.17.10 **Created:** Thu Jul 06, 2017 01:40 PM UTC by Zoran Milinkovic **Last Updated:** Tue Oct 03, 2017 06:24 AM UTC **Owner:** Hieu Nguyen pyosaf does not handle well intialization of IMM OM module. Regardless of error code returned from saImmOmInitialize, in _initialize() function, saImmOmAccessorInitialize is called(). --- Sent from sourceforge.net because opensaf-tickets@lists.sourceforge.net is subscribed to https://sourceforge.net/p/opensaf/tickets/ To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/opensaf/admin/tickets/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.-- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot___ Opensaf-tickets mailing list Opensaf-tickets@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
[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 **Milestone:** 5.17.10 **Created:** Fri Sep 29, 2017 06:54 AM UTC by Nguyen TK Luu **Last Updated:** Mon Oct 02, 2017 06:37 AM UTC **Owner:** Nguyen TK Luu Run pylint for all Python code files in OpenSAF and try to fix all reported issues. --- Sent from sourceforge.net because opensaf-tickets@lists.sourceforge.net is subscribed to https://sourceforge.net/p/opensaf/tickets/ To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/opensaf/admin/tickets/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.-- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot___ Opensaf-tickets mailing list Opensaf-tickets@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
