Since SI Swap is over, the admin operation returned. Since controller s/w
started because of SI Swap was done, so controller switchover can proceed
independently. Both shouldn't be linked with each other. The same kind of
situation occur when SU lock succeeds but just after that because of some
fault, sg goes into unstable state. SO, further admin operation can't continue.
I guess, we can close this ticket. What are other opinions?
---
** [tickets:#375] Middleware switch-over is responded before completely done**
**Status:** unassigned
**Created:** Fri May 31, 2013 03:58 AM UTC by Nagendra Kumar
**Last Updated:** Fri May 31, 2013 03:58 AM UTC
**Owner:** nobody
Migrated from http://devel.opensaf.org/ticket/2364
AMF makes no distinction between SIs for swap. This means that the response to
the admin operation is sent too early in the case the swap actually means
controller switch. This needs to be fixed.
---
Sent from sourceforge.net because [email protected] 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.
------------------------------------------------------------------------------
Learn the latest--Visual Studio 2012, SharePoint 2013, SQL 2012, more!
Discover the easy way to master current and previous Microsoft technologies
and advance your career. Get an incredible 1,500+ hours of step-by-step
tutorial videos with LearnDevNow. Subscribe today and save!
http://pubads.g.doubleclick.net/gampad/clk?id=58040911&iu=/4140/ostg.clktrk
_______________________________________________
Opensaf-tickets mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
