[tickets] [opensaf:tickets] #2421 amfd: is_swbdl_delete_ok_for_node should also check for SG and Node admin state
changeset: 8776:6ec908703ae1 tag: tip user:Praveen Malviya date:Mon Apr 24 11:57:48 2017 +0530 summary: amfd: allow nodeswbundle deletion if anyone of Node, SU or SG is locked_in [#2421] --- ** [tickets:#2421] amfd: is_swbdl_delete_ok_for_node should also check for SG and Node admin state** **Status:** fixed **Milestone:** 5.17.06 **Created:** Tue Apr 11, 2017 09:33 AM UTC by Tai Dinh **Last Updated:** Mon Apr 24, 2017 06:18 AM UTC **Owner:** Praveen During deleting of NodeSwBundle object, AMF only check if the SUs admin state is at LOCKED_INSTANTIATION or not. Which means that the deletion of that object is not allowed even in the case where the SG or Node is at LOCKED_INSTANTIATION state, which implicitetly means that the SU is UNINSTANTIATED. This currently blocks the SMF campagin to be rolled back in some situation. The SU's node admin state and SU's SG admin state should also be checked and the deletetion should be allowed if one of above state is LOCKED_INSTANTIATION. /Tai --- 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] #2421 amfd: is_swbdl_delete_ok_for_node should also check for SG and Node admin state
- **status**: review --> fixed - **Blocker**: --> True - **Comment**: develop: commit 20970cf5e21496bfef532f62cdb860388660ef62 Author: Praveen Date: Mon Apr 24 11:24:18 2017 +0530 amfd: allow nodeswbundle deletion if anyone of Node, SU or SG is locked_in [#2421] 5.17.06: commit 6c613964e1ce56ef5798b3d426d40aae1c5068ef Author: Praveen Date: Mon Apr 24 11:24:18 2017 +0530 amfd: allow nodeswbundle deletion if anyone of Node, SU or SG is locked_in [#2421] --- ** [tickets:#2421] amfd: is_swbdl_delete_ok_for_node should also check for SG and Node admin state** **Status:** fixed **Milestone:** 5.17.06 **Created:** Tue Apr 11, 2017 09:33 AM UTC by Tai Dinh **Last Updated:** Fri Apr 21, 2017 08:50 AM UTC **Owner:** Praveen During deleting of NodeSwBundle object, AMF only check if the SUs admin state is at LOCKED_INSTANTIATION or not. Which means that the deletion of that object is not allowed even in the case where the SG or Node is at LOCKED_INSTANTIATION state, which implicitetly means that the SU is UNINSTANTIATED. This currently blocks the SMF campagin to be rolled back in some situation. The SU's node admin state and SU's SG admin state should also be checked and the deletetion should be allowed if one of above state is LOCKED_INSTANTIATION. /Tai --- 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] #2381 clmd: clm admin operation returns BAD_OP after rebooting node
- **Blocker**: --> False - **Milestone**: 5.17.08 --> 5.17.06 - **Comment**: Pushed in released branch with revision: commit a79f101873dffd145aa70d9cb4eb3c99b8ffd4ca Author: Praveen Date: Fri Apr 21 14:31:19 2017 +0530 clms: return TIME_OUT for unlock op if CLMS update to CLM agent fails [#2381] --- ** [tickets:#2381] clmd: clm admin operation returns BAD_OP after rebooting node** **Status:** fixed **Milestone:** 5.17.06 **Created:** Thu Mar 16, 2017 07:30 AM UTC by Ritu Raj **Last Updated:** Fri Apr 21, 2017 11:21 AM UTC **Owner:** Praveen **Attachments:** - [active_clmd.tgz](https://sourceforge.net/p/opensaf/tickets/2381/attachment/active_clmd.tgz) (1.3 MB; application/x-compressed-tar) - [messages](https://sourceforge.net/p/opensaf/tickets/2381/attachment/messages) (1.9 MB; application/octet-stream) ###Environment details OS : Suse 64bit Changeset : 8701 ( 5.2.RC1) 4 nodes setup(2 controller and 2 payload) ###Summary clm admin operation returns SA_AIS_ERR_BAD_OPERATION after rebooting node ###Steps followed & Observed behaviour 1. Initially performed clm_lock operation on Payload (PL-3) and immediately restarted the same payload(PL-3) > init 6; exit 2. Later, performed clm_unlock operation on PL-3, and got message unlock operation got timed out but still node joined the cluster > SLES-SLOT1:~ # amf-adm unlock safNode=PL-3,safCluster=myClmCluster > Mar 15 14:35:20 SLES-SLOT1 osafclmd[2763]: ER clms_imm_node_unlock failed > Mar 15 14:35:20 SLES-SLOT1 osafamfd[2773]: NO Received node_up from 2030f: > msg_id 1 > Mar 15 14:35:20 SLES-SLOT1 osafamfd[2773]: NO Node 'PL-3' joined the cluster > Mar 15 14:35:20 SLES-SLOT1 osafimmnd[2733]: NO Implementer connected: 197 > (MsgQueueService131855) <0, 2030f> > error - command timed out (alarm) 3. After, that if clm_lock or unlock opeartion performed it returns 'SA_AIS_ERR_BAD_OPERATION' SLES-SLOT1:~ # amf-adm lock safNode=PL-3,safCluster=myClmCluster error - saImmOmAdminOperationInvoke_2 admin-op RETURNED: SA_AIS_ERR_BAD_OPERATION (20) > > SLES-SLOT1:~ # amf-adm unlock safNode=PL-3,safCluster=myClmCluster > error - saImmOmAdminOperationInvoke_2 admin-op RETURNED: > SA_AIS_ERR_BAD_OPERATION (20) Traces: >From the traces: Node PL-3 joined the cluster ~~~ Mar 15 14:35:20.373997 osafclmd [2763:src/clm/clmd/clms_imm.c:0939] >> clms_imm_admin_op_callback: Admin callback for nodename:safNode=PL-3,safCluster=myClmCluster, opId:1 Mar 15 14:35:20.374002 osafclmd [2763:src/clm/clmd/clms_util.c:0038] >> clms_node_get_by_name: name input safNode=PL-3,safCluster=myClmCluster length 36 Mar 15 14:35:20.374006 osafclmd [2763:src/clm/clmd/clms_util.c:0046] TR nodename after patricia tree get safNode=PL-3,safCluster=myClmCluster Mar 15 14:35:20.374009 osafclmd [2763:src/clm/clmd/clms_util.c:0049] << clms_node_get_by_name Mar 15 14:35:20.374012 osafclmd [2763:src/clm/clmd/clms_imm.c:2223] >> clms_imm_node_unlock: Node name safNode=PL-3,safCluster=myClmCluster to unlock Mar 15 14:35:20.374015 osafclmd [2763:src/clm/clmd/clms_imm.c:0579] >> clms_admin_state_update_rattr: Admin state 1 update for node safNode=PL-3,safCluster=myClmCluster Mar 15 14:35:20.374018 osafclmd [2763:src/clm/clmd/clms_util.c:0038] >> clms_node_get_by_name: name input safNode=PL-3,safCluster=myClmCluster length 36 Mar 15 14:35:20.374021 osafclmd [2763:src/clm/clmd/clms_util.c:0046] TR nodename after patricia tree get safNode=PL-3,safCluster=myClmCluster ~~~ .. .. *but Sending track callback failed for SA_CLM_CHANGE_COMPLETED* ~~~ Mar 15 14:35:20.380860 osafclmd [2763:src/clm/clmd/clms_imm.c:1439] TR callback msg send to clma failed Mar 15 14:35:20.380869 osafclmd [2763:src/clm/clmd/clms_imm.c:1447] << clms_prep_and_send_track Mar 15 14:35:20.380872 osafclmd [2763:src/clm/clmd/clms_imm.c:1220] TR Sending track callback failed for SA_CLM_CHANGE_COMPLETED Mar 15 14:35:20.380875 osafclmd [2763:src/clm/clmd/clms_imm.c:1380] >> clms_prep_and_send_track ~~~ -- and later performed admin operation got failed as 'Another Admin operation already in progress' ~~~ Mar 15 14:51:21.878688 osafclmd [2763:src/clm/clmd/clms_imm.c:0939] >> clms_imm_admin_op_callback: Admin callback for nodename:safNode=PL-3,safCluster=myClmCluster, opId:2 Mar 15 14:51:21.878700 osafclmd [2763:src/clm/clmd/clms_util.c:0038] >> clms_node_get_by_name: name input safNode=PL-3,safCluster=myClmCluster length 36 Mar 15 14:51:21.878712 osafclmd [2763:src/clm/clmd/clms_util.c:0046] TR nodename after patricia tree get safNode=PL-3,safCluster=myClmCluster Mar 15 14:51:21.878720 osafclmd [2763:src/clm/clmd/clms_util.c:0049] << clms_node_get_by_name Mar 15 14:51:21.878726 osafclmd [2763:src/clm/clmd/clms_imm.c:0982] TR Another Admin operation already in progress: 4 ~~~ Notes: 1. Syslog of Active controller attached 2. osafclmd of Active controller attached --- Sent from sourceforge.net because opensaf-tickets@lists.sourceforge.net is subscribed to https://sourceforge.net/p/
[tickets] [opensaf:tickets] #2367 imm: Improve ccb error string handling
- **status**: assigned --> review - **Blocker**: --> False --- ** [tickets:#2367] imm: Improve ccb error string handling** **Status:** review **Milestone:** 5.17.08 **Created:** Mon Mar 13, 2017 03:34 AM UTC by Hung Nguyen **Last Updated:** Wed Apr 12, 2017 10:12 AM UTC **Owner:** Hieu Nguyen * Use ::setCcbErrorString in ::ccbObjDelContinuation and::ccbCompletedContinuation instead of working directly with ccb->mErrorStrings * Only store error strings on originating node where OM client resides. --- 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
