Summary:amfnd: avoid sending multiple node-switchover recovery request for same fault[#1935] Review request for Trac Ticket(s): #1935 Peer Reviewer(s): AMF devs 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 y OpenSAF services n Core libraries n Samples n Tests n Other n Comments (indicate scope for each "y" above): --------------------------------------------- changeset e333d735aa1d19ac11428d1f0937df2c3c9a5822 Author: [email protected] Date: Fri, 02 Sep 2016 11:02:31 +0530 amfnd: avoid sending multiple node-switchover recovery request for same fault[#1935] In the reported problem, AMFND sends multiple mode-switchover recovery request for same fault when nodeautorepair is disabled. Sometimes, amfnd is successful in sending the request but it may crash also. In the reported problem, AMFND reports node-switchover recovery to AMFD. AMFD removes assignments gracefully and does not reboot the node as nodeautorepair is disabled. After this user deletes the faulty SU after perofrming lock and lock-in admin operations. Same SU is added again and instantiated. AMFND while instantiating the SU, sends recovery request to AMFD again for the same fault. Patch resets failed_su in avnd_cb so that recovery request is not sent for same fault again. Complete diffstat: ------------------ osaf/services/saf/amf/amfnd/susm.cc | 3 ++- 1 files changed, 2 insertions(+), 1 deletions(-) Testing Commands: ----------------- Tested as per ticket description. Testing, Expected Results: -------------------------- Not observed AMFND crash and not observed muitlple node-switchover requests. Conditions of Submission: ------------------------- Ack from anyone 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
