[tickets] [opensaf:tickets] #2273 imm: imm_common is not specified as additional library for SaImmOi
--- ** [tickets:#2273] imm: imm_common is not specified as additional library for SaImmOi** **Status:** accepted **Milestone:** 5.2.FC **Created:** Thu Jan 19, 2017 04:07 AM UTC by Hung Nguyen **Last Updated:** Thu Jan 19, 2017 04:07 AM UTC **Owner:** Hung Nguyen ~~~ [lib] $ readelf -d libSaImmOi.so Dynamic section at offset 0x22d90 contains 29 entries: TagType Name/Value 0x0001 (NEEDED) Shared library: [libopensaf_core.so.0] 0x0001 (NEEDED) Shared library: [libc.so.6] 0x000e (SONAME) Library soname: [libSaImmOi.so.0] 0x000f (RPATH) Library rpath: [/usr/local/lib/opensaf] ~~~ When linking against libSaImmOi, the compiler complains: ~~~ libSaImmOi.so: undefined reference to `immsv_evt_dec_flat' libSaImmOi.so: undefined reference to `immsv_evt_free_att_val' libSaImmOi.so: undefined reference to `immsv_evt_free_attrNames' libSaImmOi.so: undefined reference to `immsv_free_attrvalues_list' libSaImmOi.so: undefined reference to `immsv_free_attrmods' libSaImmOi.so: undefined reference to `immsv_evt_dec' libSaImmOi.so: undefined reference to `immsv_evt_enc_flat' libSaImmOi.so: undefined reference to `immsv_evt_enc' collect2: error: ld returned 1 exit status ~~~ --- 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] #2272 imm: Mismatch between continuation ids when resetting sLastContinuationId
---
** [tickets:#2272] imm: Mismatch between continuation ids when resetting
sLastContinuationId**
**Status:** accepted
**Milestone:** 5.0.2
**Created:** Thu Jan 19, 2017 03:48 AM UTC by Hung Nguyen
**Last Updated:** Thu Jan 19, 2017 03:48 AM UTC
**Owner:** Hung Nguyen
Example from ImmModel::ccbObjectCreate()
~~~
//Increment even if we dont invoke locally
oMut->mContinuationId = (++sLastContinuationId);
if(sLastContinuationId >= 0xfffe)
{sLastContinuationId = 1;}
if(*implConn) {
if(object->mImplementer->mDying) {
LOG_WA("Lost connection with implementer %s in "
"CcbObjectCreate.",
object->mImplementer->mImplementerName.c_str());
*continuationId = 0;
*implConn = 0;
//err = SA_AIS_ERR_FAILED_OPERATION;
//Let the timeout handling take care of it.
//This really needs to be tested! But how ?
} else {
*continuationId = sLastContinuationId;
}
}
~~~
There's mismatch between **oMut->mContinuationId** and **\*continuationId**
when** sLastContinuationId** is reset to 1
---
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] #2133 AMF: Rollback admin shutdown/lock SI operation if node failover
Hi Nagu, The section 3.6.2 in Compliance Table in AMF PR says: In 2N model, deviations related to shutdown operation on SI: 1) During shutdown operation on SI if component faults and it leads to component-failover, sufailover or nodefailover, then shutdown operation will not be completed and SI will remain in assigned state. 2) There is, however, one deviation when SI dependency is configured and component's fault leads to component-failover. In this case SI will go to locked state with no assignments. It looks only one case, which SI dependency is configured and component-failover is escalated, then the SI will go to LOCKED. All other cases, the SI remains ASSIGNED state, I assume the SI should be UNLOCKED to have ASSIGNED state Comparing to your findings, is there something we have to do with "single SI assignment, the admin state is locked." for su f/o and node f/o? I think it's good idea that we return other codes (TIMEOUT,...?) in case error escalation that rollback the shutdown command. Another question, do you know use case's motivation or technical problem behind that we had this deviation/inconsistency? It's good to document in README at least for code maintainance purpose (or to know what to do in similar cases for other SGs) thanks, Minh --- ** [tickets:#2133] AMF: Rollback admin shutdown/lock SI operation if node failover** **Status:** unassigned **Milestone:** future **Created:** Thu Oct 20, 2016 06:49 PM UTC by Minh Hon Chau **Last Updated:** Wed Jan 18, 2017 11:05 AM UTC **Owner:** nobody In scenario of shut down SI, delay QUIESCING csi callback, then reboot the node that hosting SU having pending this csi callback. The result of this operation looks differently between SGs - For 2N: the SI Admin state is rollbacked to UNLOCK - For Nway: the SI Admin state moves to LOCKED - In NpM: Haven't tested just browsing SG_NPM::node_fail_si_oper, looks SI Admin states rollbacks to UNLOCK My question is whether the result of these scenario should be consistent? And what's the expected outcome? Also, the handling of node_fail_si_oper for admin lock is not consistent. For 2N, Admin state remains LOCKED, NpM rollbacks to UNLOCK --- 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] #2271 imm: Unused variables in saImmOmClassCreate_2()
--- ** [tickets:#2271] imm: Unused variables in saImmOmClassCreate_2()** **Status:** accepted **Milestone:** 5.2.FC **Created:** Wed Jan 18, 2017 11:17 AM UTC by Hung Nguyen **Last Updated:** Wed Jan 18, 2017 11:17 AM UTC **Owner:** Hung Nguyen These variables always have value of 0. ~~~ int attrClNameExist = 0; int attrAdmNameExist = 0; int attrImplNameExist = 0; ~~~ --- 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] #2133 AMF: Rollback admin shutdown/lock SI operation if node failover
I will check the admin op return code and will try to fix them. --- ** [tickets:#2133] AMF: Rollback admin shutdown/lock SI operation if node failover** **Status:** unassigned **Milestone:** future **Created:** Thu Oct 20, 2016 06:49 PM UTC by Minh Hon Chau **Last Updated:** Wed Jan 18, 2017 11:04 AM UTC **Owner:** nobody In scenario of shut down SI, delay QUIESCING csi callback, then reboot the node that hosting SU having pending this csi callback. The result of this operation looks differently between SGs - For 2N: the SI Admin state is rollbacked to UNLOCK - For Nway: the SI Admin state moves to LOCKED - In NpM: Haven't tested just browsing SG_NPM::node_fail_si_oper, looks SI Admin states rollbacks to UNLOCK My question is whether the result of these scenario should be consistent? And what's the expected outcome? Also, the handling of node_fail_si_oper for admin lock is not consistent. For 2N, Admin state remains LOCKED, NpM rollbacks to UNLOCK --- 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
