[tickets] [opensaf:tickets] #2088 CLM : saClmClusterNodeGetAsync returns OK on a non member node

[Ravi Sekhar Reddy via Opensaf-tickets]

- **status**: review --> fixed



---

** [tickets:#2088] CLM : saClmClusterNodeGetAsync returns OK on a non member 
node**

**Status:** fixed
**Milestone:** future
**Created:** Mon Oct 03, 2016 07:34 AM UTC by Srikanth R
**Last Updated:** Fri Sep 01, 2017 07:01 AM UTC
**Owner:** Ravi Sekhar Reddy


Changeset : 7997 5.1.FC

The saClmClusterNodeGetAsync api returns SA_AIS_OK on a non member node.  The 
expected behavior is saClmClusterNodeGetAsync, should return ERR_AVAILABLE like 
the api saClmClusterNodeGet_4. Currently the saClmClusterNodeGet_4 api returns 
ERR_AVAILABLE on a nonmember node. 


 Below is the snippet from CLM agent trace.
 
 Oct  3 12:40:34.532320 clma [7881:clma_api.c:1235] >> saClmClusterNodeGet_4
Oct  3 12:40:34.532330 clma [7881:clma_api.c:1278] >> clmaclusternodeget
Oct  3 12:40:34.532338 clma [7881:clma_util.c:0036] >> clma_validate_version
Oct  3 12:40:34.532345 clma [7881:clma_util.c:0042] << clma_validate_version
Oct  3 12:40:34.532363 clma [7881:clma_mds.c:1227] >> clma_mds_msg_sync_send
Oct  3 12:40:34.532383 clma [7881:clma_mds.c:0317] >> clma_mds_enc
Oct  3 12:40:34.532392 clma [7881:clma_mds.c:0352] T2 msgtype: 0
Oct  3 12:40:34.532399 clma [7881:clma_mds.c:0366] T2 api_info.type: 4
Oct  3 12:40:34.532406 clma [7881:clma_mds.c:0192] >> clma_enc_node_get_msg
Oct  3 12:40:34.532412 clma [7881:clma_mds.c:0207] << clma_enc_node_get_msg
Oct  3 12:40:34.532418 clma [7881:clma_mds.c:0407] << clma_mds_enc
Oct  3 12:40:34.533347 clma [7881:clma_mds.c:0697] >> clma_mds_dec
Oct  3 12:40:34.533377 clma [7881:clma_mds.c:0729] T2 CLMSV_CLMA_API_RESP_MSG 
rc = 31
Oct  3 12:40:34.533388 clma [7881:clma_mds.c:0809] << clma_mds_dec
Oct  3 12:40:34.533448 clma [7881:clma_mds.c:1253] << clma_mds_msg_sync_send
Oct  3 12:40:34.533474 clma [7881:clma_util.c:0656] >> clma_msg_destroy
Oct  3 12:40:34.533486 clma [7881:clma_util.c:0694] << clma_msg_destroy
Oct  3 12:40:34.533496 clma [7881:clma_api.c:1395] << clmaclusternodeget
Oct  3 12:40:34.533502 clma [7881:clma_api.c:1245] << saClmClusterNodeGet_4
Oct  3 12:40:34.533657 clma [7881:clma_api.c:1422] >> saClmClusterNodeGetAsync
Oct  3 12:40:34.533668 clma [7881:clma_util.c:0036] >> clma_validate_version
Oct  3 12:40:34.533674 clma [7881:clma_util.c:0042] << clma_validate_version
Oct  3 12:40:34.533681 clma [7881:clma_mds.c:1274] >> clma_mds_msg_async_send
Oct  3 12:40:34.533692 clma [7881:clma_mds.c:0317] >> clma_mds_enc
Oct  3 12:40:34.533700 clma [7881:clma_mds.c:0352] T2 msgtype: 0
Oct  3 12:40:34.533707 clma [7881:clma_mds.c:0366] T2 api_info.type: 5
Oct  3 12:40:34.533713 clma [7881:clma_mds.c:0229] >> 
clma_enc_node_get_async_msg
Oct  3 12:40:34.533720 clma [7881:clma_mds.c:0245] << 
clma_enc_node_get_async_msg
Oct  3 12:40:34.533726 clma [7881:clma_mds.c:0407] << clma_mds_enc
Oct  3 12:40:34.533744 clma [7881:clma_mds.c:1296] << clma_mds_msg_async_send
Oct  3 12:40:34.533753 clma [7881:clma_api.c:1497] << saClmClusterNodeGetAsync


---

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] #2638 dtm: Use multiple backup files when rotating log files

[Anders Widell via Opensaf-tickets]

- **status**: assigned --> review



---

** [tickets:#2638] dtm: Use multiple backup files when rotating log files**

**Status:** review
**Milestone:** 5.17.10
**Created:** Thu Oct 19, 2017 10:15 AM UTC by Anders Widell
**Last Updated:** Thu Oct 19, 2017 10:15 AM UTC
**Owner:** Anders Widell


Currently, only one backup file is used when rotating log files. This may be 
insufficient when the internal log server is used for trace, and the suggestion 
is to use multiple backup files (.1, .2, .3 ... .9)


---

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] #2653 nid: Derive Node ID from TIPC address when not managing TIPC

[Anders Widell via Opensaf-tickets]

- **status**: review --> fixed
- **Type**: defect --> enhancement
- **Comment**:

commit 0da15c4702eaed9a39f4697eee38dbd2f99f17bd (HEAD -> develop, ticket-2653)
Author: Anders Widell 
Date:   Thu Oct 26 12:15:31 2017 +0200

dtm: Always call the configure_tipc script [#2653]

Call the configure_tipc script regardless of whether OpenSAF is configured 
to
manage TIPC or not. This is needed since the script may need to set up the 
Node
ID when OpenSAF is not managing TIPC.

commit f58a2e542f6ef93114073820031e313bf0d57a6a
Author: Anders Widell 
Date:   Thu Oct 26 12:15:31 2017 +0200

nid: Derive node ID from TIPC address when not managing TIPC [#2653]

If OpenSAF is not configured to manage TIPC, we don't need to require the
presence of /etc/opensaf/slot_id or /var/lib/opensaf/node_id. Instead, we 
create
the file /var/lib/opensaf/node_id ourselves based on the TIPC address of the
node we are running on. The same translation formula is used (in the 
opposite
direction) as when OpenSAF is managing TIPC.




---

** [tickets:#2653] nid: Derive Node ID from TIPC address when not managing 
TIPC**

**Status:** fixed
**Milestone:** 5.17.10
**Created:** Wed Oct 25, 2017 11:42 AM UTC by Anders Widell
**Last Updated:** Wed Oct 25, 2017 12:38 PM UTC
**Owner:** Anders Widell


Related to [#2598]. If OpenSAF is not configured to manage TIPC, we don't need 
to require the presence of /etc/opensaf/slot_id or /var/lib/opensaf/node_id. 
Instead, we can create the file /var/lib/opensaf/node_id ourselves based on the 
TIPC address of the node we are running on.



---

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] #2601 #AMF: MessageID Missmatch during Headless between AMFD and AMFND

[Ravi Sekhar Reddy via Opensaf-tickets]

- **status**: review --> fixed
- **Comment**:

Also, agreed to handle D2N_PRESENCE_SU and PG_TRACK Messages in a separate 
Ticket

Gary suggested to do some refactoring as well ..

Eg. write a function that returns a state (eg SC_ABSENT, SC_SYNCING, 
SC_SYNCED), instead of directly checking these variables:

cb->is_avd_down == true || cb->amfd_sync_required == true

cb->is_avd_down == true && cb->amfd_sync_required == true




---

** [tickets:#2601] #AMF: MessageID Missmatch during Headless between AMFD and 
AMFND**

**Status:** fixed
**Milestone:** 5.17.10
**Created:** Thu Sep 28, 2017 11:51 AM UTC by Ravi Sekhar Reddy
**Last Updated:** Tue Oct 17, 2017 11:57 AM UTC
**Owner:** Ravi Sekhar Reddy


During Headless if any component on the payload fails, Message ID miss match is 
hapeening when buffered messages are sent from AMFND to AMFD

Steps to reproduce :
1. 3 node setup with 2 controllers and one payload (SC-1, SC-2 & PL-4) 
2. Headless enabled 
3. 2n application deployed where SU1 is hosted on the SC-1 and SU2 is hosted on 
the PL-4.
   Configure Delay in AmfCSISetCallbackT callback
   Configure CLC-CLI script of demo cmp to exit with -1 on cleanup invocation  
4. Set ACTIVE assignment on ACTIVE SC-1, STANDBY on PL-4. 
5. Stop opensafd on SC-1
6. Stop opensafd on SC-2 when ACTIVE assignment is given to Application 
Component on PL-4
7. Start opensafd on SC-1, before AMFD comeup up Kill App component on PL-4 
   As we configured to return -1 on Cleanup, termination will fail and SU will 
move to "Termination Failed" State
8. At AMFD observed messages with invalid Message ID and Messages are being 
dropped 



---

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] #2657 log: valgrind reports invalid write in logtest

[Vu Minh Nguyen via Opensaf-tickets]

- **status**: assigned --> review



---

** [tickets:#2657] log: valgrind reports invalid write in logtest**

**Status:** review
**Milestone:** 5.17.10
**Created:** Thu Oct 26, 2017 07:26 AM UTC by Vu Minh Nguyen
**Last Updated:** Thu Oct 26, 2017 07:26 AM UTC
**Owner:** Vu Minh Nguyen


Here is valgrind report:

> ==1586== Invalid write of size 8
> ==1586==at 0x11623B: strcpy (string3.h:104)
> ==1586==by 0x11623B: saLogWriteLogCallbackT_02 
> (tet_saLogWriteLogCallbackT.c:155)
> ==1586==by 0x1299E8: run_test_case (utest.c:178)
> ==1586==by 0x129EF3: test_run (utest.c:202)
> ==1586==by 0x10FD27: main (logtest.c:558)
> ==1586==  Address 0xffeff0450 is on thread 1's stack
> ==1586==  65408 bytes below stack pointer
> ==1586==
> ==1586== Invalid write of size 8
> ==1586==at 0x116248: strcpy (string3.h:104)
> ==1586==by 0x116248: saLogWriteLogCallbackT_02 
> (tet_saLogWriteLogCallbackT.c:155)
> ==1586==by 0x1299E8: run_test_case (utest.c:178)
> ==1586==by 0x129EF3: test_run (utest.c:202)
> ==1586==by 0x10FD27: main (logtest.c:558)
> ==1586==  Address 0xffeff0458 is on thread 1's stack
> ==1586==  65400 bytes below stack pointer




---

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] #2657 log: valgrind reports invalid write in logtest

[Vu Minh Nguyen via Opensaf-tickets]

---

** [tickets:#2657] log: valgrind reports invalid write in logtest**

**Status:** assigned
**Milestone:** 5.17.10
**Created:** Thu Oct 26, 2017 07:26 AM UTC by Vu Minh Nguyen
**Last Updated:** Thu Oct 26, 2017 07:26 AM UTC
**Owner:** Vu Minh Nguyen


Here is valgrind report:

> ==1586== Invalid write of size 8
> ==1586==at 0x11623B: strcpy (string3.h:104)
> ==1586==by 0x11623B: saLogWriteLogCallbackT_02 
> (tet_saLogWriteLogCallbackT.c:155)
> ==1586==by 0x1299E8: run_test_case (utest.c:178)
> ==1586==by 0x129EF3: test_run (utest.c:202)
> ==1586==by 0x10FD27: main (logtest.c:558)
> ==1586==  Address 0xffeff0450 is on thread 1's stack
> ==1586==  65408 bytes below stack pointer
> ==1586==
> ==1586== Invalid write of size 8
> ==1586==at 0x116248: strcpy (string3.h:104)
> ==1586==by 0x116248: saLogWriteLogCallbackT_02 
> (tet_saLogWriteLogCallbackT.c:155)
> ==1586==by 0x1299E8: run_test_case (utest.c:178)
> ==1586==by 0x129EF3: test_run (utest.c:202)
> ==1586==by 0x10FD27: main (logtest.c:558)
> ==1586==  Address 0xffeff0458 is on thread 1's stack
> ==1586==  65400 bytes below stack pointer




---

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