Summary: amfd: fix bad standby assignment in N+M [#1414] Review request for Trac Ticket(s): #1414 Peer Reviewer(s): Nagu, Praveen Pull request to: Nagu Affected branch(es): default, 4.6, 4.5 Development branch:
-------------------------------- 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 2c5d542674cb3ba85d2cbd7192b71ba5fd35c514 Author: Alex Jones <[email protected]> Date: Mon, 13 Jul 2015 14:22:52 -0400 amfd: fix N+M identification of standby SU at controller failover [#1414] An N+M SU, with an active assignment, can also get a standby assignment at the same time. Details for reproducing this are in the ticket. The SUSI returned from avd_sg_npm_su_othr() is not being checked to make sure that its HA state is standby (among other things). The SUSI returned from avd_sg_npm_su_othr() needs to check that its HA state is standby, that its readiness state is in-service, and that its fsm state is not unassigned. This is done in many parts of sg_npm_fsm.cc, but it is missing in some parts. Complete diffstat: ------------------ osaf/services/saf/amf/amfd/sg_npm_fsm.cc | 5 ++++- 1 files changed, 4 insertions(+), 1 deletions(-) Testing Commands: ----------------- See ticket for explanation of how to reproduce the problem. Testing, Expected Results: -------------------------- No standby should be assigned to an SU which already has an active assignment. Conditions of Submission: ------------------------- <<HOW MANY DAYS BEFORE PUSHING, CONSENSUS ETC>> 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. ------------------------------------------------------------------------------ Don't Limit Your Business. Reach for the Cloud. GigeNET's Cloud Solutions provide you with the tools and support that you need to offload your IT needs and focus on growing your business. Configured For All Businesses. Start Your Cloud Today. https://www.gigenetcloud.com/ _______________________________________________ Opensaf-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/opensaf-devel
