[tickets] [opensaf:tickets] #1869 AMF: SG in unstable for SI lock operation, after HEADLESS
- **status**: accepted --> duplicate - **Comment**: #1725 fixed. --- ** [tickets:#1869] AMF: SG in unstable for SI lock operation, after HEADLESS ** **Status:** duplicate **Milestone:** future **Created:** Thu Jun 09, 2016 07:24 AM UTC by Srikanth R **Last Updated:** Mon Oct 30, 2017 08:31 AM UTC **Owner:** nobody Opensaf version : 5.0. GA. Setup : 5 nodes with 3 controllers. PL-5, PL-4 hosted active, standby assignments for application 2n SU. where as SC-3 hosted spare SU. Steps performed: -> Brought down all the controllers and headless scenario is created. ->Now stopped opensafd on PL-5, where SU2 is hosting active assignment -> SU1 on PL-4 did not get active assignment. It remained in standby assignment. -> After the controllers joined back the cluster, following is the error message printed on the PL-4. Aug 26 17:21:34 SCALE_SLOT-94 osafamfnd[19347]: CR SU-SI record addition failed, SU= safSu=SU1,safSg=AmfDemo,safApp=AmfDemo : SI=safSi=AmfDemo,safApp=AmfDemo SCALE_SLOT-94:~ # immlist safSi=AmfDemo,safApp=AmfDemo Name Type Value(s) saAmfSIPrefStandbyAssignments SA_UINT32_T 1 (0x1) saAmfSIPrefActiveAssignments SA_UINT32_T 1 (0x1) saAmfSINumCurrStandbyAssignments SA_UINT32_T 2 (0x2) saAmfSINumCurrActiveAssignmentsSA_UINT32_T 0 (0x0) saAmfSIAssignmentState SA_UINT32_T 3 (0x3) -> Lock operation on SI resulted in SG unstable operation. 46 04:30:46 07/23/2016 NO safApp=safAmfService "Cluster startup timeout, assigning SIs to SUs" 47 04:30:46 07/23/2016 NO safApp=safAmfService "safSi=AmfDemo,safApp=AmfDemo assigned to safSu=SU1,safSg=AmfDemo,safApp=AmfDemo HA State 'STANDBY'" 48 04:30:46 07/23/2016 NO safApp=safAmfService "Autorepair not done for 'safSu=SC-3,safSg=2N,safApp=OpenSAF'" 49 04:30:46 07/23/2016 NO safApp=safAmfService "Autorepair not done for 'safSu=SU3_Spare,safSg=AmfDemo,safApp=AmfDemo'" 50 07:49:21 07/23/2016 NO safApp=safAmfService "Admin op "LOCK" initiated for 'safSi=AmfDemo,safApp=AmfDemo', invocation: 219043332097" 51 07:49:21 07/23/2016 NO safApp=safAmfService "Admin op invocation: 219043332097, err: 'SI lock of 'safSi=AmfDemo,safApp=AmfDemo' failed, SG not stable'" 52 07:49:21 07/23/2016 NO safApp=safAmfService "Admin op done for invocation: 219043332097, result 6" 53 07:49:22 07/23/2016 NO safApp=safAmfService "Admin op "LOCK" initiated for 'safSi=AmfDemo,safApp=AmfDemo', invocation: 2190 --- 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.___ Opensaf-tickets mailing list Opensaf-tickets@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
[tickets] [opensaf:tickets] #1869 AMF: SG in unstable for SI lock operation, after HEADLESS
- **status**: unassigned --> accepted - **Blocker**: --> False --- ** [tickets:#1869] AMF: SG in unstable for SI lock operation, after HEADLESS ** **Status:** accepted **Milestone:** future **Created:** Thu Jun 09, 2016 07:24 AM UTC by Srikanth R **Last Updated:** Tue Sep 20, 2016 05:43 PM UTC **Owner:** nobody Opensaf version : 5.0. GA. Setup : 5 nodes with 3 controllers. PL-5, PL-4 hosted active, standby assignments for application 2n SU. where as SC-3 hosted spare SU. Steps performed: -> Brought down all the controllers and headless scenario is created. ->Now stopped opensafd on PL-5, where SU2 is hosting active assignment -> SU1 on PL-4 did not get active assignment. It remained in standby assignment. -> After the controllers joined back the cluster, following is the error message printed on the PL-4. Aug 26 17:21:34 SCALE_SLOT-94 osafamfnd[19347]: CR SU-SI record addition failed, SU= safSu=SU1,safSg=AmfDemo,safApp=AmfDemo : SI=safSi=AmfDemo,safApp=AmfDemo SCALE_SLOT-94:~ # immlist safSi=AmfDemo,safApp=AmfDemo Name Type Value(s) saAmfSIPrefStandbyAssignments SA_UINT32_T 1 (0x1) saAmfSIPrefActiveAssignments SA_UINT32_T 1 (0x1) saAmfSINumCurrStandbyAssignments SA_UINT32_T 2 (0x2) saAmfSINumCurrActiveAssignmentsSA_UINT32_T 0 (0x0) saAmfSIAssignmentState SA_UINT32_T 3 (0x3) -> Lock operation on SI resulted in SG unstable operation. 46 04:30:46 07/23/2016 NO safApp=safAmfService "Cluster startup timeout, assigning SIs to SUs" 47 04:30:46 07/23/2016 NO safApp=safAmfService "safSi=AmfDemo,safApp=AmfDemo assigned to safSu=SU1,safSg=AmfDemo,safApp=AmfDemo HA State 'STANDBY'" 48 04:30:46 07/23/2016 NO safApp=safAmfService "Autorepair not done for 'safSu=SC-3,safSg=2N,safApp=OpenSAF'" 49 04:30:46 07/23/2016 NO safApp=safAmfService "Autorepair not done for 'safSu=SU3_Spare,safSg=AmfDemo,safApp=AmfDemo'" 50 07:49:21 07/23/2016 NO safApp=safAmfService "Admin op "LOCK" initiated for 'safSi=AmfDemo,safApp=AmfDemo', invocation: 219043332097" 51 07:49:21 07/23/2016 NO safApp=safAmfService "Admin op invocation: 219043332097, err: 'SI lock of 'safSi=AmfDemo,safApp=AmfDemo' failed, SG not stable'" 52 07:49:21 07/23/2016 NO safApp=safAmfService "Admin op done for invocation: 219043332097, result 6" 53 07:49:22 07/23/2016 NO safApp=safAmfService "Admin op "LOCK" initiated for 'safSi=AmfDemo,safApp=AmfDemo', invocation: 2190 --- 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] #1869 AMF: SG in unstable for SI lock operation, after HEADLESS
- **Milestone**: 5.0.1 --> 5.0.2 --- ** [tickets:#1869] AMF: SG in unstable for SI lock operation, after HEADLESS ** **Status:** unassigned **Milestone:** 5.0.2 **Created:** Thu Jun 09, 2016 07:24 AM UTC by Srikanth R **Last Updated:** Thu Jun 09, 2016 08:01 AM UTC **Owner:** nobody Opensaf version : 5.0. GA. Setup : 5 nodes with 3 controllers. PL-5, PL-4 hosted active, standby assignments for application 2n SU. where as SC-3 hosted spare SU. Steps performed: -> Brought down all the controllers and headless scenario is created. ->Now stopped opensafd on PL-5, where SU2 is hosting active assignment -> SU1 on PL-4 did not get active assignment. It remained in standby assignment. -> After the controllers joined back the cluster, following is the error message printed on the PL-4. Aug 26 17:21:34 SCALE_SLOT-94 osafamfnd[19347]: CR SU-SI record addition failed, SU= safSu=SU1,safSg=AmfDemo,safApp=AmfDemo : SI=safSi=AmfDemo,safApp=AmfDemo SCALE_SLOT-94:~ # immlist safSi=AmfDemo,safApp=AmfDemo Name Type Value(s) saAmfSIPrefStandbyAssignments SA_UINT32_T 1 (0x1) saAmfSIPrefActiveAssignments SA_UINT32_T 1 (0x1) saAmfSINumCurrStandbyAssignments SA_UINT32_T 2 (0x2) saAmfSINumCurrActiveAssignmentsSA_UINT32_T 0 (0x0) saAmfSIAssignmentState SA_UINT32_T 3 (0x3) -> Lock operation on SI resulted in SG unstable operation. 46 04:30:46 07/23/2016 NO safApp=safAmfService "Cluster startup timeout, assigning SIs to SUs" 47 04:30:46 07/23/2016 NO safApp=safAmfService "safSi=AmfDemo,safApp=AmfDemo assigned to safSu=SU1,safSg=AmfDemo,safApp=AmfDemo HA State 'STANDBY'" 48 04:30:46 07/23/2016 NO safApp=safAmfService "Autorepair not done for 'safSu=SC-3,safSg=2N,safApp=OpenSAF'" 49 04:30:46 07/23/2016 NO safApp=safAmfService "Autorepair not done for 'safSu=SU3_Spare,safSg=AmfDemo,safApp=AmfDemo'" 50 07:49:21 07/23/2016 NO safApp=safAmfService "Admin op "LOCK" initiated for 'safSi=AmfDemo,safApp=AmfDemo', invocation: 219043332097" 51 07:49:21 07/23/2016 NO safApp=safAmfService "Admin op invocation: 219043332097, err: 'SI lock of 'safSi=AmfDemo,safApp=AmfDemo' failed, SG not stable'" 52 07:49:21 07/23/2016 NO safApp=safAmfService "Admin op done for invocation: 219043332097, result 6" 53 07:49:22 07/23/2016 NO safApp=safAmfService "Admin op "LOCK" initiated for 'safSi=AmfDemo,safApp=AmfDemo', invocation: 2190 --- 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.-- ___ Opensaf-tickets mailing list Opensaf-tickets@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
[tickets] [opensaf:tickets] #1869 AMF: SG in unstable for SI lock operation, after HEADLESS
This issue is stated in #1725, will be fixed in #1725 --- ** [tickets:#1869] AMF: SG in unstable for SI lock operation, after HEADLESS ** **Status:** unassigned **Milestone:** 5.0.1 **Created:** Thu Jun 09, 2016 07:24 AM UTC by Srikanth R **Last Updated:** Thu Jun 09, 2016 07:24 AM UTC **Owner:** nobody Opensaf version : 5.0. GA. Setup : 5 nodes with 3 controllers. PL-5, PL-4 hosted active, standby assignments for application 2n SU. where as SC-3 hosted spare SU. Steps performed: -> Brought down all the controllers and headless scenario is created. ->Now stopped opensafd on PL-5, where SU2 is hosting active assignment -> SU1 on PL-4 did not get active assignment. It remained in standby assignment. -> After the controllers joined back the cluster, following is the error message printed on the PL-4. Aug 26 17:21:34 SCALE_SLOT-94 osafamfnd[19347]: CR SU-SI record addition failed, SU= safSu=SU1,safSg=AmfDemo,safApp=AmfDemo : SI=safSi=AmfDemo,safApp=AmfDemo SCALE_SLOT-94:~ # immlist safSi=AmfDemo,safApp=AmfDemo Name Type Value(s) saAmfSIPrefStandbyAssignments SA_UINT32_T 1 (0x1) saAmfSIPrefActiveAssignments SA_UINT32_T 1 (0x1) saAmfSINumCurrStandbyAssignments SA_UINT32_T 2 (0x2) saAmfSINumCurrActiveAssignmentsSA_UINT32_T 0 (0x0) saAmfSIAssignmentState SA_UINT32_T 3 (0x3) -> Lock operation on SI resulted in SG unstable operation. 46 04:30:46 07/23/2016 NO safApp=safAmfService "Cluster startup timeout, assigning SIs to SUs" 47 04:30:46 07/23/2016 NO safApp=safAmfService "safSi=AmfDemo,safApp=AmfDemo assigned to safSu=SU1,safSg=AmfDemo,safApp=AmfDemo HA State 'STANDBY'" 48 04:30:46 07/23/2016 NO safApp=safAmfService "Autorepair not done for 'safSu=SC-3,safSg=2N,safApp=OpenSAF'" 49 04:30:46 07/23/2016 NO safApp=safAmfService "Autorepair not done for 'safSu=SU3_Spare,safSg=AmfDemo,safApp=AmfDemo'" 50 07:49:21 07/23/2016 NO safApp=safAmfService "Admin op "LOCK" initiated for 'safSi=AmfDemo,safApp=AmfDemo', invocation: 219043332097" 51 07:49:21 07/23/2016 NO safApp=safAmfService "Admin op invocation: 219043332097, err: 'SI lock of 'safSi=AmfDemo,safApp=AmfDemo' failed, SG not stable'" 52 07:49:21 07/23/2016 NO safApp=safAmfService "Admin op done for invocation: 219043332097, result 6" 53 07:49:22 07/23/2016 NO safApp=safAmfService "Admin op "LOCK" initiated for 'safSi=AmfDemo,safApp=AmfDemo', invocation: 2190 --- 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.-- What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic patterns at an interface-level. Reveals which users, apps, and protocols are consuming the most bandwidth. Provides multi-vendor support for NetFlow, J-Flow, sFlow and other flows. Make informed decisions using capacity planning reports. https://ad.doubleclick.net/ddm/clk/305295220;132659582;e___ Opensaf-tickets mailing list Opensaf-tickets@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
[tickets] [opensaf:tickets] #1869 AMF: SG in unstable for SI lock operation, after HEADLESS
--- ** [tickets:#1869] AMF: SG in unstable for SI lock operation, after HEADLESS ** **Status:** unassigned **Milestone:** 5.0.1 **Created:** Thu Jun 09, 2016 07:24 AM UTC by Srikanth R **Last Updated:** Thu Jun 09, 2016 07:24 AM UTC **Owner:** nobody Opensaf version : 5.0. GA. Setup : 5 nodes with 3 controllers. PL-5, PL-4 hosted active, standby assignments for application 2n SU. where as SC-3 hosted spare SU. Steps performed: -> Brought down all the controllers and headless scenario is created. ->Now stopped opensafd on PL-5, where SU2 is hosting active assignment -> SU1 on PL-4 did not get active assignment. It remained in standby assignment. -> After the controllers joined back the cluster, following is the error message printed on the PL-4. Aug 26 17:21:34 SCALE_SLOT-94 osafamfnd[19347]: CR SU-SI record addition failed, SU= safSu=SU1,safSg=AmfDemo,safApp=AmfDemo : SI=safSi=AmfDemo,safApp=AmfDemo SCALE_SLOT-94:~ # immlist safSi=AmfDemo,safApp=AmfDemo Name Type Value(s) saAmfSIPrefStandbyAssignments SA_UINT32_T 1 (0x1) saAmfSIPrefActiveAssignments SA_UINT32_T 1 (0x1) saAmfSINumCurrStandbyAssignments SA_UINT32_T 2 (0x2) saAmfSINumCurrActiveAssignmentsSA_UINT32_T 0 (0x0) saAmfSIAssignmentState SA_UINT32_T 3 (0x3) -> Lock operation on SI resulted in SG unstable operation. 46 04:30:46 07/23/2016 NO safApp=safAmfService "Cluster startup timeout, assigning SIs to SUs" 47 04:30:46 07/23/2016 NO safApp=safAmfService "safSi=AmfDemo,safApp=AmfDemo assigned to safSu=SU1,safSg=AmfDemo,safApp=AmfDemo HA State 'STANDBY'" 48 04:30:46 07/23/2016 NO safApp=safAmfService "Autorepair not done for 'safSu=SC-3,safSg=2N,safApp=OpenSAF'" 49 04:30:46 07/23/2016 NO safApp=safAmfService "Autorepair not done for 'safSu=SU3_Spare,safSg=AmfDemo,safApp=AmfDemo'" 50 07:49:21 07/23/2016 NO safApp=safAmfService "Admin op "LOCK" initiated for 'safSi=AmfDemo,safApp=AmfDemo', invocation: 219043332097" 51 07:49:21 07/23/2016 NO safApp=safAmfService "Admin op invocation: 219043332097, err: 'SI lock of 'safSi=AmfDemo,safApp=AmfDemo' failed, SG not stable'" 52 07:49:21 07/23/2016 NO safApp=safAmfService "Admin op done for invocation: 219043332097, result 6" 53 07:49:22 07/23/2016 NO safApp=safAmfService "Admin op "LOCK" initiated for 'safSi=AmfDemo,safApp=AmfDemo', invocation: 2190 --- 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.-- What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic patterns at an interface-level. Reveals which users, apps, and protocols are consuming the most bandwidth. Provides multi-vendor support for NetFlow, J-Flow, sFlow and other flows. Make informed decisions using capacity planning reports. https://ad.doubleclick.net/ddm/clk/305295220;132659582;e___ Opensaf-tickets mailing list Opensaf-tickets@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
