Summary: fmd: fix regression interacting with PLM [#2844]
Review request for Ticket(s): 2844
Peer Reviewer(s): Gary, Mathi, Ravi
Pull request to:
Affected branch(es): develop
Development branch: ticket-2844
Base revision: fd827200ddd0336d8301fefed62d4afc40e5f10b
Personal repository: git://git.code.sf.net/u/trguitar/review
--------------------------------
Impacted area Impact y/n
--------------------------------
Docs n
Build system n
RPM/packaging n
Configuration files n
Startup scripts n
SAF services n
OpenSAF services y
Core libraries n
Samples n
Tests n
Other n
Comments (indicate scope for each "y" above):
---------------------------------------------
revision 9ab40a006c71a27c140cea5a32ab71b33facdb25
Author: Alex Jones <ajo...@rbbn.com>
Date: Mon, 30 Apr 2018 10:52:41 -0400
fmd: fix regression interacting with PLM [#2844]
fmd does not pass the EE to opensaf_reboot when attempting to reset the peer.
The legacy code passed 0 to fm_mds_async_send. The new code passes
NCSMDS_SCOPE_NONE, but doesn't update how bcast_scope is used.
Change fm_mds_async_send to check bcast_scope. If it is not NCSMDS_SCOPE_NONE,
then use it. Otherwise, use the MDS dest.
Complete diffstat:
------------------
src/fm/fmd/fm_mds.cc | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
Testing Commands:
-----------------
1) bring down a controller in a PLM environment
Testing, Expected Results:
--------------------------
1) The remaining controller should attempt to use PLM to reset the controller
which went down
Conditions of Submission:
-------------------------
May 6, or ack from developer
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 ~/.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
