[tickets] [opensaf:tickets] #1906 clm: add support for long DN
Hi Ritu, Can you check your test case that executionEnvironment is using value longer than 255 characters ? I'm asking you this because before the patch, CLM allowed to use SaNameT value up to 256 characters. But in this case CLM removed the last 256th character and set \0. So SaNameT value is not the same before and after sending to CLM. After applying the patch, it's allowed to use SaNameT values up to 255 characters like in IMM. Frankly, I have no idea how CLM stored this values in IMM earlier. --- ** [tickets:#1906] clm: add support for long DN** **Status:** review **Milestone:** 5.1.FC **Created:** Mon Jul 04, 2016 01:10 PM UTC by Zoran Milinkovic **Last Updated:** Fri Aug 26, 2016 09:33 AM UTC **Owner:** Zoran Milinkovic Ticket [#191] introduces support for long DN. This ticket adds the support for long RDN to CLM. Today, there is no any reason for the support for long DN in CLM. The main reason for adding support for long DN is to support long RDN. In SaClmNode class, safNode attribute may have a hostname which can be up to 63 bytes. Together with prefix "safNode=", RDN exceedes RDN limitation of 64 bytes. Limit of 255 bytes for DN will still remain after applying the patch. Only long RDN will be supported. The same limitation applies to PLM entities in CLM. --- 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] #1934 amf: amfd fail-overs su to failed node during node-switchover recovery.
- **status**: accepted --> review --- ** [tickets:#1934] amf: amfd fail-overs su to failed node during node-switchover recovery. ** **Status:** review **Milestone:** 4.7.2 **Created:** Thu Aug 04, 2016 11:46 AM UTC by Praveen **Last Updated:** Thu Aug 04, 2016 11:54 AM UTC **Owner:** Praveen **Attachments:** - [nodeswitch.xml](https://sourceforge.net/p/opensaf/tickets/1934/attachment/nodeswitch.xml) (11.1 kB; text/xml) Conf: Two SUs hosted on standby controller with 2N model. Recovery is node-switchover with su-failover flag enabled for SU1. Steps to reproduce: 1)Bring attached configuration up. 2) kill comp in SU1(active SU). When AMFD gets recovery request for standby SC, it failovers SU1 and gives active to SU2 as a part of SU1 recovery. For SU2 recovery, it then sends quiesced assignment. This is a wrong sequence. Since SU2 is hosted on failed node, AMFD should not failover SU1 to SU2, >From code perpective: AMFD marks all SUs of failed node OOS only in INIT_DONE >state. In APP_STATE this needs to be done by respective reocovery funtion. In >case of node-failvoer recovery avd_node_down_appl_susi_failover() is marking >SUs OOS before performing failover. But perform_nodeswitchover_recovery() is >not marking all the SUs OOS before performing failover/switchover of any SU. --- 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] #1725 AMF: Recover transient SUSIs left over from headless
Attach all patches support to phase #0 #1 #2, apply with below orders 1725_01_V5_intro_new_rta_states_longDn.diff 1725_02_V2_resend_su_si_assign_msg_longDn.diff 1725_02_bugfix_all.diff 1725_03_V4_failover_absent_susi_longDn.diff 1725_04_V2_headless_validation.diff 1725_05_V2_resend_oper_state.diff (from #1902) 1725_06a_fullscope_escalation_headless.diff (from #1902) Note: . Not support for nodegroup operation . Test case component failover is still under testing . Test case SC failover while headless sync is under testing Attachments: - [1725_p2.tgz](https://sourceforge.net/p/opensaf/tickets/_discuss/thread/7b203666/fa79/attachment/1725_p2.tgz) (25.6 kB; application/x-compressed) - [test_report_1725_p2.ods](https://sourceforge.net/p/opensaf/tickets/_discuss/thread/7b203666/fa79/attachment/test_report_1725_p2.ods) (16.0 kB; application/vnd.oasis.opendocument.spreadsheet) --- ** [tickets:#1725] AMF: Recover transient SUSIs left over from headless** **Status:** review **Milestone:** 5.1.FC **Created:** Wed Apr 06, 2016 07:16 AM UTC by Minh Hon Chau **Last Updated:** Thu Aug 25, 2016 03:08 PM UTC **Owner:** Minh Hon Chau This ticket is more likely an enhancement that targets on how AMFD detect and recover the transients SUSI left over from headless. There are three major situations: (1) - Cluster goes headless, su/node failover on any payloads can happen, or any payloads can be hard rebooted/powered off by operator, then cluster recover (2) - issue admin op on any AMF entities, cluster goes headless. During headless, the middle HA assignments of whole admin op sequence between AMFND and components could be: (2.1) The assignment completes, component returns OK with csi callback, then cluster recover (2.2) The assignment is under going, then cluster recover. The assignment afterward could complete, or csi callback returns FAILED_OPERATION or error can also happen At the time cluster recover, amfd has collected all assignments from all amfnd(s). These assignments can be in assigned or assigning states whilst its HA states do not conform its SG redundancy. Any of (1) (2.1) (2.2) can happen in a combination, which means while issuing admin op (2), cluster go headless and any kinds of failover (1) can happen during headless. --- 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] #1906 clm: add support for long DN
Hi Zoran, We did't added any clm node or changes any configuration, the default one is used. Also, the test case are not related to longDn. --- ** [tickets:#1906] clm: add support for long DN** **Status:** review **Milestone:** 5.1.FC **Created:** Mon Jul 04, 2016 01:10 PM UTC by Zoran Milinkovic **Last Updated:** Wed Aug 24, 2016 01:36 PM UTC **Owner:** Zoran Milinkovic Ticket [#191] introduces support for long DN. This ticket adds the support for long RDN to CLM. Today, there is no any reason for the support for long DN in CLM. The main reason for adding support for long DN is to support long RDN. In SaClmNode class, safNode attribute may have a hostname which can be up to 63 bytes. Together with prefix "safNode=", RDN exceedes RDN limitation of 64 bytes. Limit of 255 bytes for DN will still remain after applying the patch. Only long RDN will be supported. The same limitation applies to PLM entities in CLM. --- 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] #1973 imm: IMM test returns zero even when it fails
---
** [tickets:#1973] imm: IMM test returns zero even when it fails**
**Status:** accepted
**Milestone:** 4.7.2
**Created:** Fri Aug 26, 2016 08:15 AM UTC by Hung Nguyen
**Last Updated:** Fri Aug 26, 2016 08:15 AM UTC
**Owner:** Hung Nguyen
Snippet from main() in immtest.c
~~~
int main(int argc, char **argv)
{
...
/* Added pthread_exit() to remove dlopen@@GLIBC leak from valgrind */
pthread_exit(NULL);
return rc;
}
~~~
pthread_exit() should be removed because it makes the test exit before 'return
rc'.
I tried to run valgrind without pthread_exit(), it didn't complain anything
about dlopen.
---
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
