Summary: rde: save a role for active and standby nodes in peer info request
[#2423]
Review request for Ticket(s): 2423
Peer Reviewer(s): Anders W., Ramesh
Pull request to: Zoran
Affected branch(es): develop
Development branch: ticket-2423
Private repository: git://git.code.sf.net/u/zmilinkovic/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 0ba8847949ad2ea3517e782c5c277bf37b14af24
Author: Zoran Milinkovic <zoran.milinko...@ericsson.com>
Date: Tue, 11 Apr 2017 14:49:09 +0200
rde: save a role for active and standby nodes in peer info request [#2423]
When a node with active or standby role sends peer info request, the node role
will be saved.
This will avoid setting the active role to the new starting node.
Complete diffstat:
------------------
src/rde/rded/rde_main.cc | 3 +++
1 file changed, 3 insertions(+)
Testing Commands:
-----------------
Testing, Expected Results:
--------------------------
The problem is very hard to reproduce. That's because it's a timing issue in
very small time gap.
When a new joined node receives peer info request from a active or standby
node, and before the joined node received response from active or standby node,
the joined node should not set active or standby role.
Conditions of Submission:
-------------------------
Ack from Anders W. and Ramesh
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
