[tickets] [opensaf:tickets] #2373 IMM: Object Implementer APIs giving BAD_ANDLE on a locked node
- **status**: accepted --> review --- ** [tickets:#2373] IMM: Object Implementer APIs giving BAD_ANDLE on a locked node** **Status:** review **Milestone:** 5.2.RC2 **Created:** Tue Mar 14, 2017 11:15 AM UTC by Chani Srivastava **Last Updated:** Mon Mar 20, 2017 10:03 AM UTC **Owner:** Neelakanta Reddy **Environment details** OS : Suse 64bit Changeset : 8634 ( 5.2.FC) Setup : 4 nodes **Steps to Reproduce:** 1. Initialize OI a on a payload 2. Perform lock operation on that payload 3. Call saImmOiObjectImplementerSet()/saImmOiObjectImplementerRelease() with the handle obtained in step1 Step 3 returned with BAD_HANDLE Expected: Step 3 should return ERR_UNAVAILABLE like saImmOiClassImplementerSet() and others --- 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] #2380 log: change LOG_ER incase rename file failed
- **assigned_to**: Canh Truong --> nobody
---
** [tickets:#2380] log: change LOG_ER incase rename file failed**
**Status:** duplicate
**Milestone:** 5.2.RC2
**Created:** Wed Mar 15, 2017 01:44 PM UTC by Canh Truong
**Last Updated:** Mon Mar 20, 2017 10:05 AM UTC
**Owner:** nobody
LOG_ER("Could not rename log file: %s", strerror(errno));
After main thread send request to file handle thread to rename log file, the
main thread may get some failed result. Maybe it's not error case. e.g. file is
not exist incase deleting manually,
Convert ER to WA.
---
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] #2380 log: change LOG_ER incase rename file failed
- **status**: accepted --> duplicate
- **Comment**:
it is fixed in #2383
---
** [tickets:#2380] log: change LOG_ER incase rename file failed**
**Status:** duplicate
**Milestone:** 5.2.RC2
**Created:** Wed Mar 15, 2017 01:44 PM UTC by Canh Truong
**Last Updated:** Wed Mar 15, 2017 01:51 PM UTC
**Owner:** Canh Truong
LOG_ER("Could not rename log file: %s", strerror(errno));
After main thread send request to file handle thread to rename log file, the
main thread may get some failed result. Maybe it's not error case. e.g. file is
not exist incase deleting manually,
Convert ER to WA.
---
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] #2373 IMM: Object Implementer APIs giving BAD_ANDLE on a locked node
- **status**: unassigned --> accepted - **assigned_to**: Neelakanta Reddy - **Part**: - --> lib - **Version**: --> 5.2 - **Comment**: when the OI was initalized with version A.02.18 and CLM node is locked. saImmOiObjectImplementerSet()/saImmOiObjectImplementerRelease() must return ERR_UNAVAILABLE --- ** [tickets:#2373] IMM: Object Implementer APIs giving BAD_ANDLE on a locked node** **Status:** accepted **Milestone:** 5.2.RC2 **Created:** Tue Mar 14, 2017 11:15 AM UTC by Chani Srivastava **Last Updated:** Tue Mar 14, 2017 11:15 AM UTC **Owner:** Neelakanta Reddy **Environment details** OS : Suse 64bit Changeset : 8634 ( 5.2.FC) Setup : 4 nodes **Steps to Reproduce:** 1. Initialize OI a on a payload 2. Perform lock operation on that payload 3. Call saImmOiObjectImplementerSet()/saImmOiObjectImplementerRelease() with the handle obtained in step1 Step 3 returned with BAD_HANDLE Expected: Step 3 should return ERR_UNAVAILABLE like saImmOiClassImplementerSet() and others --- 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] #2379 smf:PR documentation for 5.2 release
- **status**: accepted --> review --- ** [tickets:#2379] smf:PR documentation for 5.2 release** **Status:** review **Milestone:** 5.2.RC2 **Created:** Wed Mar 15, 2017 10:03 AM UTC by Neelakanta Reddy **Last Updated:** Wed Mar 15, 2017 10:03 AM UTC **Owner:** Neelakanta Reddy update the PR document wit 5.2 Enancements smf: add support for asynchronous detection of failed AMF entities [#2145] --- 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] #2212 smf: avoid unpredictable timeout for adminoperations
- **Milestone**: 5.2.RC2 --> future --- ** [tickets:#2212] smf: avoid unpredictable timeout for adminoperations** **Status:** accepted **Milestone:** future **Created:** Thu Dec 01, 2016 05:06 AM UTC by Neelakanta Reddy **Last Updated:** Thu Dec 01, 2016 05:06 AM UTC **Owner:** Neelakanta Reddy SmfImmUtils AdminOperation can be changed to avoid unpredictable timeout similar to adminoperation in nodegroup. call the nodegroup adminoperation using SmfImmUtils --- 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] #2387 amf: choose CLM unlocked spare controller for standby role in failover situation
- **summary**: clm_locked spare controller got standby role after failover --> amf: choose CLM unlocked spare controller for standby role in failover situation - Description has changed: Diff: --- old +++ new @@ -4,7 +4,7 @@ 6 nodes setup(3 controller and 3 payload, with SC_ABSENCE enabled) ###Summary -clm_locked spare controller got standby role after failover +choose CLM unlocked spare controller for standby role in failover situation ###Steps followed & Observed behaviour 1. Initially SC-1 (ACTIVE), SC-2 (QUIESCED) , SC-3 (STANDBY) role --- ** [tickets:#2387] amf: choose CLM unlocked spare controller for standby role in failover situation** **Status:** assigned **Milestone:** 5.0.2 **Created:** Fri Mar 17, 2017 12:13 PM UTC by Ritu Raj **Last Updated:** Mon Mar 20, 2017 07:09 AM UTC **Owner:** Praveen **Attachments:** - [SC-1.tar.bz2](https://sourceforge.net/p/opensaf/tickets/2387/attachment/SC-1.tar.bz2) (873.4 kB; application/x-bzip) - [SC-2.tar.bz2](https://sourceforge.net/p/opensaf/tickets/2387/attachment/SC-2.tar.bz2) (762.0 kB; application/x-bzip) - [SC-3.tar.bz2](https://sourceforge.net/p/opensaf/tickets/2387/attachment/SC-3.tar.bz2) (724.5 kB; application/x-bzip) ###Environment details OS : Suse 64bit Changeset : 8701 ( 5.2.RC1) 6 nodes setup(3 controller and 3 payload, with SC_ABSENCE enabled) ###Summary choose CLM unlocked spare controller for standby role in failover situation ###Steps followed & Observed behaviour 1. Initially SC-1 (ACTIVE), SC-2 (QUIESCED) , SC-3 (STANDBY) role 2. Performed clm_lock operation on SC-2(QUIESCED) controller 3. after, that perfomed on failover on Active controller (SC-1), by killing one director 4. Observed that SC-3 got Active role while SC-2 got Standby role, which is not expcted as node SC-2 is in clm_locked state 5. Later, SC-1 joined as QUIESCED controller (after recovery from failover) **Expected**: clm_lock node should not get standby role as it is in locked state and SC-1 should join as a Standby after recovery from failover. Syslog: Mar 17 17:56:59 suseR2-S2 osafimmnd[21809]: NO Implementer (applier) connected: 28 (@safSmf_applier1) <0, 2030f> Mar 17 17:56:59 suseR2-S2 osafamfnd[21859]: NO Assigning 'safSi=SC-2N,safApp=OpenSAF' STANDBY to 'safSu=SC-2,safSg=2N,safApp=OpenSAF' Mar 17 17:56:59 suseR2-S2 osafrded[21779]: NO RDE role set to STANDBY Mar 17 17:56:59 suseR2-S2 osafrded[21779]: NO Peer up on node 0x2030f Mar 17 17:56:59 suseR2-S2 osafrded[21779]: NO Got peer info request from node 0x2030f with role ACTIVE Mar 17 17:56:59 suseR2-S2 osafrded[21779]: NO Got peer info response from node 0x2030f with role ACTIVE Mar 17 17:56:59 suseR2-S2 osafimmd[21798]: NO MDS event from svc_id 24 (change:3, dest:13) Mar 17 17:56:59 suseR2-S2 osafimmd[21798]: NO MDS event from svc_id 24 (change:5, dest:13) Mar 17 17:56:59 suseR2-S2 osafimmd[21798]: NO MDS event from svc_id 24 (change:5, dest:13) Mar 17 17:56:59 suseR2-S2 osafimmd[21798]: NO MDS event from svc_id 25 (change:3, dest:566317113647120) Mar 17 17:56:59 suseR2-S2 osafimmd[21798]: NO MDS event from svc_id 25 (change:3, dest:565213543063568) Mar 17 17:56:59 suseR2-S2 osafimmd[21798]: IN AMF HA STANDBY request Mar 17 17:56:59 suseR2-S2 osafimmd[21798]: IN Added IMMND node with dest 566317113647120 Mar 17 17:56:59 suseR2-S2 osafimmd[21798]: IN Added IMMND node with dest 565213543063568 Mar 17 17:56:59 suseR2-S2 osafsmfd[21878]: WA saClmClusterNodeGet failed, rc=SA_AIS_ERR_UNAVAILABLE (31) Mar 17 17:56:59 suseR2-S2 osafsmfd[21878]: WA proc_mds_info: SMFND UP failed Mar 17 17:56:59 suseR2-S2 osafsmfd[21878]: WA saClmClusterNodeGet failed, rc=SA_AIS_ERR_UNAVAILABLE (31) Mar 17 17:56:59 suseR2-S2 osafsmfd[21878]: WA proc_mds_info: SMFND UP failed From Traces: SC-2 left the cluster as clm lock operation performed and later SC-1 left the cluster as one failover performed: ~~~ SC-2::: Mar 17 17:54:24.123134 osafamfnd [6773:src/amf/amfnd/clm.cc:0196] >> clm_track_cb: '0' '4' '1' Mar 17 17:54:24.123142 osafamfnd [6773:src/amf/amfnd/clm.cc:0217] TR Node has left the cluster 'safNode=SC-2,safCluster=myClmCluster', avnd_cb->first_time_up 0,notifItem->clusterNode.nodeId 131599, avnd_cb->node_info.nodeId 131343 - - SC-1::: Mar 17 17:57:03.514477 osafamfnd [9266:src/amf/amfnd/clm.cc:0196] >> clm_track_cb: '0' '4' '1' Mar 17 17:57:03.514484 osafamfnd [9266:src/amf/amfnd/clm.cc:0217] TR Node has left the cluster 'safNode=SC-1,safCluster=myClmCluster', avnd_cb->first_time_up 0,notifItem->clusterNode.nodeId 131343, avnd_cb->node_info.nodeId 131855 ~~~ after failover SC-2 got standby role and SC-3 Active : ~~~ SC::2 Mar 17 17:56:59.941081 osafamfnd [21859:src/amf/amfnd/susm.cc:1043] NO Assigned 'safSi=SC-2N,safApp=OpenSAF' STANDBY to 'safSu=SC-2,safSg=2N,safApp=OpenSAF' Mar 17 17:56:59.941089 osafamfnd [21859:src/amf/amfnd/err.cc:1639] >> is_no_assignment_due_to_escalations Mar 17 17:56:59.941097 osafamfnd
