Summary: amfnd: add cleanup command for proxy and proxied [#2186]
Review request for Trac Ticket(s): #2186
Peer Reviewer(s): Amf Dev
Pull request to: <<LIST THE PERSON WITH PUSH ACCESS HERE>>
Affected branch(es): Default
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 337c6dde5dfca14c8af4299a2a2598958bd1ea37
Author: Nagendra Kumar<nagendr...@oracle.com>
Date: Thu, 17 Nov 2016 13:41:09 +0530
amfnd: add cleanup command for proxy and proxied [#2186] When proxy and
proxied are in the same SU and if proxy fails and SU restart is
escalated,
then proxied are not being cleaned up. Added cleanup commands for
proxied
component if their proxy are not in healthy state. Also, during opensafd
stop, opensafd is not able to terminate the proxy. Added fix for this
also.
Complete diffstat:
------------------
osaf/services/saf/amf/amfnd/clc.cc | 38
++++++++++++++++++++++++++++++--------
osaf/services/saf/amf/amfnd/susm.cc | 24 +++++++++++++++++++++++-
2 files changed, 53 insertions(+), 9 deletions(-)
Testing Commands:
-----------------
Please use proxy.c and proxy.xml for testing attached in the ticket.
Proxy.xml is having Su with 1 proxy component and two proxied components.
Configured saAmfSgtDefCompRestartMax as 1.
1. immcfg -f proxy.xml
2. amf-adm unlock-in safSu=1,safSg=2N,safApp=Proxy; amf-adm unlock
safSu=1,safSg=2N,safApp=Proxy
3. pkill -9 proxy and again pkill -9 proxy to restart SU.
4. amf-adm unlock-in safSu=1,safSg=2N,safApp=Proxy; amf-adm unlock
safSu=1,safSg=2N,safApp=Proxy
5. amf-adm lock safSu=1,safSg=2N,safApp=Proxy
6. amf-adm unlock safSu=1,safSg=2N,safApp=Proxy
7. amf-adm restart safSu=1,safSg=2N,safApp=Proxy
Testing, Expected Results:
--------------------------
All steps #4 to #7 worked fine.
Conditions of Submission:
-------------------------
Ack from Amf Dev
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.
------------------------------------------------------------------------------
_______________________________________________
Opensaf-devel mailing list
Opensaf-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensaf-devel
