Summary: plm: don't instantiate child EEs twice when unlocking parent EE [#2846]
Review request for Ticket(s): 2846
Peer Reviewer(s): Mathi, Ravi
Pull request to:
Affected branch(es): develop
Development branch: ticket-2846
Base revision: 46181161a4b4afbf1f269d601914951da97265ef
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 y
OpenSAF services n
Core libraries n
Samples n
Tests n
Other n
Comments (indicate scope for each "y" above):
---------------------------------------------
revision 4efaccbcde991cd3ff848e43af6c6d007912af14
Author: Alex Jones <ajo...@rbbn.com>
Date: Thu, 3 May 2018 10:53:15 -0400
plm: don't instantiate child EEs twice when unlocking parent EE [#2846]
Child EEs (VMs) can fail to boot up when unlocking the parent EE.
The current code resets the VM when unlocking the parent EE. This is done in
plms_move_chld_ent_to_insvc(). Later in the unlock function, the child EEs
are reset again. libvirt does not like these resets being done in less than 1
second, and often will not boot the VM.
Don't reset the child EEs twice when unlocking the parent EE.
Complete diffstat:
------------------
src/plm/plmd/plms_adm_fsm.c | 5 ++++-
1 file changed, 4 insertions(+), 1 deletion(-)
Testing Commands:
-----------------
1) Setup a parent EE with at least 17 child EEs
2) Lock the parent EE
3) Unlock the parent EE
Testing, Expected Results:
--------------------------
1) child EEs should not get instantiated (reset) twice
Conditions of Submission:
-------------------------
May 9, 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
