osaf/services/saf/amf/amfd/sgproc.cc |  6 ++++++
 1 files changed, 6 insertions(+), 0 deletions(-)


Problem: Run time objects and attributes are not updated when node-failover
gots escalated for active controller and standby controller took
the active role.

Reason: Activities related to update of runtime objects and certain
attribute to IMM are given low priotiy and are pushed in Job queue by AMF.
These jobs are completed when AMF is not busy in any other high priority
activity. When node-failover is escalated, AMFD sends reboot message to
AMFND to reboot the node. In case node-failover is escalated for active
controller, it will send reboot message to AMFND which will reboot the
controller. In such a case, some IMM related activites in JOB queue will
remian uncompleted. All such activites should be compleleted before
rebooting the active controller when node-failover is escalated for it.

Fix: Fix will finish all IMM related jobs before sending reboot message
to AMFND when node-failover is escalated for active controller.

diff --git a/osaf/services/saf/amf/amfd/sgproc.cc 
b/osaf/services/saf/amf/amfd/sgproc.cc
--- a/osaf/services/saf/amf/amfd/sgproc.cc
+++ b/osaf/services/saf/amf/amfd/sgproc.cc
@@ -528,6 +528,12 @@ void avd_su_oper_state_evh(AVD_CL_CB *cb
                                                                "Ordering 
reboot of '%s' as node fail/switch-over"
                                                                " repair 
action",
                                                                
node->name.value);
+                                               AvdJobDequeueResultT job_res = 
JOB_EXECUTED;
+                                               /* Finish as many IMM jobs as 
possible because active 
+                                                  controller is rebooting.
+                                                */
+                                               while (job_res == JOB_EXECUTED)
+                                                       job_res = 
Fifo::execute(cb->immOiHandle);
                                                avd_d2n_reboot_snd(node);
                                                goto done;
                                        } else {

------------------------------------------------------------------------------
Is your legacy SCM system holding you back? Join Perforce May 7 to find out:
• 3 signs your SCM is hindering your productivity
• Requirements for releasing software faster
• Expert tips and advice for migrating your SCM now
http://p.sf.net/sfu/perforce
_______________________________________________
Opensaf-devel mailing list
Opensaf-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensaf-devel

Reply via email to