Summary: amfd: respond to IMM for admin op status when SG becomes stable [#1740] Review request for Trac Ticket(s): #1740 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 d22a9caa140f4e1bb16c0347ddfb937964f9ec57 Author: [email protected] Date: Tue, 12 Apr 2016 10:43:38 +0530 amfd: respond to IMM for admin op status when SG becomes stable [#1740] If unlock admin operation on SU1 is timed just after cluster timer expiry, AMFD will start assignment for SU1. During this phase, some other SUs in same SG may be in INSTANTIATING state. These SUs may move to INSTANTIATION state before the assignment due to unlock operation is over in SU1 and becomes eligible for assignments. Now when AMFD gets assignment response from AMFND, it will start assignment for other SUs in SG_FSM. Although assignment in SU1 is over, SG remains in UNSTABLE state as assignmnets in other SUs started. Because of this AMFD loses the context of admin operation and when SG becomes stable it never responds to IMM for the completed operation. Patch fixes the problem by checking each SU for any pending admin operation when SG becomes stable. Complete diffstat: ------------------ osaf/services/saf/amf/amfd/sgproc.cc | 3 +-- 1 files changed, 1 insertions(+), 2 deletions(-) Testing Commands: ----------------- As per ticket description tested for 2N and Nored models. Testing, Expected Results: -------------------------- AMFD responded for admin operation. 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. ------------------------------------------------------------------------------ Find and fix application performance issues faster with Applications Manager Applications Manager provides deep performance insights into multiple tiers of your business applications. It resolves application problems quickly and reduces your MTTR. Get your free trial! https://ad.doubleclick.net/ddm/clk/302982198;130105516;z _______________________________________________ Opensaf-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/opensaf-devel
