Summary: amfd: Return SA_AIS_ERR_BAD_OPERATION if error occurs during si-swap
[#214]
Review request for Trac Ticket(s): #214
Peer Reviewer(s): Hans F, Hans N
Pull request to: <<LIST THE PERSON WITH PUSH ACCESS HERE>>
Affected branch(es): All
Development branch: Default
--------------------------------
Impacted area Impact y/n
--------------------------------
Docs n
Build system n
RPM/packaging n
Configuration files n
Startup scripts n
SAF services y
OpenSAF services n
Core libraries n
Samples n
Tests n
Other n
Comments (indicate scope for each "y" above):
---------------------------------------------
<<EXPLAIN/COMMENT THE PATCH SERIES HERE>>
changeset e4673201df894f6e8052031c82f19720ab157196
Author: Nagendra Kumar<nagendr...@oracle.com>
Date: Wed, 27 Nov 2013 14:51:22 +0530
amfd: Return SA_AIS_ERR_BAD_OPERATION if error occurs during si-swap
[#214]
During si-swap, when su goes into terminating state, amf need to respond
back to imm with error as SA_AIS_ERR_BAD_OPERATION. As of now, Amf is
not
even responding to imm in case of error during si-swap. This causes Amf
to
respond back to previous si operation result when another si-swap
operation
is successfully executed as invocation is not reset for previous si-swap
operation.
Complete diffstat:
------------------
osaf/services/saf/amf/amfd/sg_2n_fsm.cc | 10 ++++++++++
1 files changed, 10 insertions(+), 0 deletions(-)
Testing Commands:
-----------------
In amf demo application, configure two SI (with two csi) with si dep.
SU with two components.
1. Unlock both the SUs, SU1 Act, SU2 Standby.
2. Keep gdb in component in SU1 at saAmfResponse and Run 'amf-adm si-swap
safSi=AmfDemo,safApp=AmfDemo1'
3. Return 21 in saAmfResponse from component in SU1 in gdb.
4. Run 'amf-adm si-swap safSi=AmfDemo1,safApp=AmfDemo1'
Testing, Expected Results:
--------------------------
After 3, si-swap command will return with SA_AIS_ERR_BAD_OPERATION.
After 4, si-swap command will be successful and swap result will be sent for
safSi=AmfDemo1,safApp=AmfDemo1
and not for safSi=AmfDemo,safApp=AmfDemo1(as it use to do it before this fix).
Conditions of Submission:
-------------------------
Ack from peer reviewers
Arch Built Started Linux distro
-------------------------------------------
mips n n
mips64 n n
x86 n n
x86_64 y y
powerpc n n
powerpc64 n n
Reviewer Checklist:
-------------------
[Submitters: make sure that your review doesn't trigger any checkmarks!]
Your checkin has not passed review because (see checked entries):
___ Your RR template is generally incomplete; it has too many blank entries
that need proper data filled in.
___ You have failed to nominate the proper persons for review and push.
___ Your patches do not have proper short+long header
___ You have grammar/spelling in your header that is unacceptable.
___ You have exceeded a sensible line length in your headers/comments/text.
___ You have failed to put in a proper Trac Ticket # into your commits.
___ You have incorrectly put/left internal data in your comments/files
(i.e. internal bug tracking tool IDs, product names etc)
___ You have not given any evidence of testing beyond basic build tests.
Demonstrate some level of runtime or other sanity testing.
___ You have ^M present in some of your files. These have to be removed.
___ You have needlessly changed whitespace or added whitespace crimes
like trailing spaces, or spaces before tabs.
___ You have mixed real technical changes with whitespace and other
cosmetic code cleanup changes. These have to be separate commits.
___ You need to refactor your submission into logical chunks; there is
too much content into a single commit.
___ You have extraneous garbage in your review (merge commits etc)
___ You have giant attachments which should never have been sent;
Instead you should place your content in a public tree to be pulled.
___ You have too many commits attached to an e-mail; resend as threaded
commits, or place in a public tree for a pull.
___ You have resent this content multiple times without a clear indication
of what has changed between each re-send.
___ You have failed to adequately and individually address all of the
comments and change requests that were proposed in the initial review.
___ You have a misconfigured ~/.hgrc file (i.e. username, email etc)
___ Your computer have a badly configured date and time; confusing the
the threaded patch review.
___ Your changes affect IPC mechanism, and you don't present any results
for in-service upgradability test.
___ Your changes affect user manual and documentation, your patch series
do not contain the patch that updates the Doxygen manual.
------------------------------------------------------------------------------
Rapidly troubleshoot problems before they affect your business. Most IT
organizations don't have a clear picture of how application performance
affects their revenue. With AppDynamics, you get 100% visibility into your
Java,.NET, & PHP application. Start your 15-day FREE TRIAL of AppDynamics Pro!
http://pubads.g.doubleclick.net/gampad/clk?id=84349351&iu=/4140/ostg.clktrk
_______________________________________________
Opensaf-devel mailing list
Opensaf-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensaf-devel
