Summary: amf : disable oper state of faulty comp if SU is disabled [#1035]
Review request for Trac Ticket(s): #1035
Peer Reviewer(s): AMF contributors
Pull request to: <<LIST THE PERSON WITH PUSH ACCESS HERE>>
Affected branch(es): ALL
Development branch: <<IF ANY GIVE THE REPO URL>>
--------------------------------
Impacted area Impact y/n
--------------------------------
Docs n
Build system n
RPM/packaging n
Configuration files n
Startup scripts n
SAF services n
OpenSAF services y
Core libraries n
Samples n
Tests n
Other n
Comments (indicate scope for each "y" above):
---------------------------------------------
changeset 686ee80a6cea723a9ae76702221b1442eb536238
Author: praveen.malv...@oracle.com
Date: Fri, 05 Sep 2014 10:26:00 +0530
amf : disable oper state of faulty comp if SU is disabled [#1035]
Operational state of faulty component is not disabled when SU gets
disabled
after termination failure.
AMFND is not disabling the oper state of component when its
instantiation
and clean up fails. AMFND marks both compoent and its SU TERM_FAILED but
disables only SU.
Patch updates the component oper state at AMFND and same update is sent
to
AMFD. Also it replies for the pending operation
Complete diffstat:
------------------
osaf/services/saf/amf/amfd/ndproc.cc | 10 ++++++++++
osaf/services/saf/amf/amfnd/clc.cc | 12 ++++++++----
osaf/services/saf/amf/amfnd/susm.cc | 14 ++++++++++++++
3 files changed, 32 insertions(+), 4 deletions(-)
Testing Commands:
-----------------
Tested case given in ticket with
PI SU configuration and
NPI SU configuration
Testing, Expected Results:
--------------------------
component should be marked disabled.
Conditions of Submission:
-------------------------
Ack from any reviewer
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.
------------------------------------------------------------------------------
Slashdot TV.
Video for Nerds. Stuff that matters.
http://tv.slashdot.org/
_______________________________________________
Opensaf-devel mailing list
Opensaf-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensaf-devel
