Summary: smf: Fix handling of MDS events in smfnd [#2723] Review request for Ticket(s): 2723 Peer Reviewer(s): rafael.odza...@ericsson.com Pull request to: Affected branch(es): develop Development branch: ticket-2723 Base revision: d54303925f86813c5c2fa1103f3c8ed841488145 Personal repository: git://git.code.sf.net/u/elunlen/review
-------------------------------- 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 *** revision 924aa6e5046621c2c299f22d1943b8f1b0148b4a Author: Lennart Lund <lennart.l...@ericsson.com> Date: Tue, 5 Dec 2017 12:16:50 +0100 smf: Fix handling of MDS events in smfnd [#2723] The global smfd_dest (in cd struct) shall be restored with MDS event NCSMDS_UP and NCSMDS_NEW_ACTIVE (is set to 0 with event NCSMDS_DOWN) Complete diffstat: ------------------ src/smf/smfnd/smfnd_mds.c | 7 +++++-- 1 file changed, 5 insertions(+), 2 deletions(-) Testing Commands: ----------------- Configure system for absence allowed Check result for each step 1. Start a cluster 2. Do a si swap 3. Reboot both SC nodes at the same time 4. Stop both SC nodes and then start at least one of them Testing, Expected Results: -------------------------- Check result using the following grep on the syslog. $ grep 'MDS ' <path to syslog>/messages The printout shall show that the smfd destination is restored Conditions of Submission: ------------------------- Ack by reviwers or one week Arch Built Started Linux distro ------------------------------------------- mips n n mips64 n n x86 n n x86_64 n n 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 ~/.gitconfig file (i.e. user.name, user.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. ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot _______________________________________________ Opensaf-devel mailing list Opensaf-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/opensaf-devel