[tickets] [opensaf:tickets] #1842 rde: standby amfd notifies to NID early.

2016-05-20 Thread Anders Widell
- **status**: unassigned --> invalid - **Milestone**: 5.0.1 --> never - **Comment**: I don't see why it would be a problem that MW components get assigned while AMFD cold sync is in progress. If AMFD detects a fail-over before the cold sync is complete, it shall initiate a node reboot since it

[tickets] [opensaf:tickets] #1842 rde: standby amfd notifies to NID early.

2016-05-20 Thread Anders Widell
We must move away from using NID for synchronizing. NID currently only plays a role when OpenSAF is initially started, but not after OpenSAF is up and running (as in this case when assigning the STANDBY role to a spare controller node, or for example when unlocking/instantiating the middleware

[tickets] [opensaf:tickets] #1842 rde: standby amfd notifies to NID early.

2016-05-20 Thread Praveen
--- ** [tickets:#1842] rde: standby amfd notifies to NID early.** **Status:** unassigned **Milestone:** 5.0.1 **Created:** Fri May 20, 2016 09:25 AM UTC by Praveen **Last Updated:** Fri May 20, 2016 09:25 AM UTC **Owner:** nobody Rde API rda_get_role() gives quiesced role on other than

[tickets] [opensaf:tickets] #1841 amfd: Out of sync at si-swap when coldsync is late

2016-05-20 Thread Hans Nordebäck
--- ** [tickets:#1841] amfd: Out of sync at si-swap when coldsync is late** **Status:** review **Milestone:** 5.1.FC **Created:** Fri May 20, 2016 06:09 AM UTC by Hans Nordebäck **Last Updated:** Fri May 20, 2016 06:09 AM UTC **Owner:** Hans Nordebäck At start of a new amfd standby in a