Summary: amfnd: Delete comp_curr_info if comp fails into TERMINATION_FAILED [#1500] Review request for Trac Ticket(s): 1500 Peer Reviewer(s): AMF devs Pull request to: AMF maintainers Affected branch(es): 4.6, 4.7, 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 d7df94a697aa1258c1ed38f2bc59c4bb95c0d055 Author: Minh Hon Chau <[email protected]> Date: Tue, 15 Dec 2015 15:16:50 +1100 amfnd: Delete comp_curr_info if comp fails into TERMINATION_FAILED [#1500] Escalation is configured in the way that just one component restart can lead to su failover. If the clc cleanup script returns error, the component fails into TERMINATION_FAILED state. The AMF repair command also fails afterward, because component can not register healthcheck callback with error code 14 (SA_AIS_ERR_EXIST) returned from amfnd. If clc cleanup succeeds, amfnd will delete component info. But if cleanup fails, amfnd currently does not delete component info. At the other escalation configuration, which more component restart leads to su failover, amfnd does delete component info at the first component restart recovery. Therefore, if component fails into TERMINAITON_FAILED later on, the healthcheck won't get error in repair. Complete diffstat: ------------------ osaf/services/saf/amf/amfnd/clc.cc | 2 +- 1 files changed, 1 insertions(+), 1 deletions(-) Testing Commands: ----------------- Repeat the steps to reproduce this problem Testing, Expected Results: -------------------------- Repair SU successfully Conditions of Submission: ------------------------- ack from 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. ------------------------------------------------------------------------------ _______________________________________________ Opensaf-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/opensaf-devel
