[tickets] [opensaf:tickets] #2499 SMF: 20 seconds timeout in getting node destination is not enough

This issue is as far as I could see a bug. In other campaign sequences SMF will wait with rebootTimeout before doing any operation after reboot. In this campaign sequence the first operation type after a reboot was to to a CLI command on a payload node. This timed out because the CLI command is

[tickets] [opensaf:tickets] #2513 rde: allow to early change peer role only when active or standby nodes exist

- **status**: review --> fixed - **Comment**: release(5.17.06): commit aba7bc5460136cca39b6b067d934973b3099fe0f Author: Zoran Milinkovic Date: Wed Jun 28 13:25:29 2017 +0200 rde: allow early role change when active or standby nodes are introduced [#2513]

[tickets] [opensaf:tickets] #2513 rde: allow to early change peer role only when active or standby nodes exist

- **status**: accepted --> review - **Comment**: https://sourceforge.net/p/opensaf/mailman/message/35916824/ --- ** [tickets:#2513] rde: allow to early change peer role only when active or standby nodes exist** **Status:** review **Milestone:** 5.17.06 **Created:** Wed Jun 28, 2017 09:14 AM

[tickets] [opensaf:tickets] #2459 try-again for opensafd stop

- **status**: review --> fixed - **Comment**: commit a051496719a3c862594af17d88b082031dd53b33 (ticket-2459) base: Try again for opensafd stop [#2459] Internally opensafd creates a mutex during start/stop to avoid parallel execution. Makes mutex more robust and add a short retry if

[tickets] [opensaf:tickets] #2513 rde: allow to early change peer role only when active or standby nodes exist

--- ** [tickets:#2513] rde: allow to early change peer role only when active or standby nodes exist** **Status:** accepted **Milestone:** 5.17.06 **Created:** Wed Jun 28, 2017 09:14 AM UTC by Zoran Milinkovic **Last Updated:** Wed Jun 28, 2017 09:14 AM UTC **Owner:** Zoran Milinkovic The

[tickets] [opensaf:tickets] #2512 clmtest: test case 7 7 return failed when new node is added to test environment

- **status**: review --> fixed - **Comment**: 5.17.08 (develop) [code:7193ab] ~~~ commit 7193ab9d6261f13efe5ce173f3b9bee248401ef3 Author: Hoang Vo Date: Wed Jun 28 13:43:48 2017 +0700 clmtest: update non-member node_id for new test environment [#2512]

[tickets] [opensaf:tickets] #2490 amfnd: handle ERR_NOT_EXIST

- **status**: review --> fixed --- ** [tickets:#2490] amfnd: handle ERR_NOT_EXIST** **Status:** fixed **Milestone:** 5.17.08 **Created:** Fri Jun 09, 2017 02:07 AM UTC by Gary Lee **Last Updated:** Wed Jun 28, 2017 06:35 AM UTC **Owner:** Gary Lee Sometimes this can be seen on AMFND:

[tickets] [opensaf:tickets] #2490 amfnd: handle ERR_NOT_EXIST

commit a2ad04ecd1dba0ba033fd028322c24d6842ac347 Author: Gary Lee Date: Thu Jun 15 17:35:58 2017 +1000 amfnd: retry on ERR_NOT_EXIST [#2490] On a congested network, sometimes a newly created IMM object can take some time to be available on other nodes.

[tickets] [opensaf:tickets] #2469 amf: Stop tracking api returns NOT_EXIST

- **status**: review --> fixed - **assigned_to**: Minh Hon Chau --> nobody - **Comment**: commits: release: [10bc897c58b915960021b5dd63378f23b40e2f15] develop: [f3b59d740b303f6eaba4584160ce9c0281adcde9] --- ** [tickets:#2469] amf: Stop tracking api returns NOT_EXIST** **Status:** fixed